Hi guys, it’s been quite the development week for the Connector. This update will make future updates easier to deploy and, most importantly, easier to install for you. Gone are the ZIP files in comes the installer.
When I started this project, I was always proud of the ease of installation. Download the ZIP file, extract, and press run. Sounds great, right! The downside is that when you’ve been a loyal user of the software, you’d probably have a collection of ZIP files. Even I sometimes can’t figure out the latest version on my pc. It also meant that your handcrafted event file would get overwritten if you weren’t careful.
Say hello to my new friend, the installer!
The installer lets you install and even update every component individually. If a new update is available, the Connector will prompt you with a button. If you click the button, the ConnectorMaintenanceTool will open, where you’re able to update without having to juggle ZIP files. This change makes it easier for me to push more minor updates. Win-win all around.
By default, the connector checks if an update is available once it launches. You could also check for updates manually from either the Connector or the ConnectorMaintenanceTool.
By default, users can’t write data to the Program files folder. It’s meant to store the application’s core functionality while the changeable data get stored elsewhere. Utilizing this principle, we can make our event files persist spread over several updates. Currently, your event file is stored in the same folder as the Connector. From 1.2.0-0 out, the events file is stored next to the settings file (” %appdata%/Bits and Droids/BitsAndDroidsConnector/events.txt”). When you start the Connector, it checks if an event file is present. If that is not the case, it stores the default version in your appdata folder. Installing the WASM module through the Connector will retrieve the events file from the appdata folder.
TLDR: Your event file isn’t stored in the BitsAndDroidsModule folder anymore. If you want to install the WASM module manually, fetch the events.txt from the new location.
Simplicity without angering power users
The previous UI could lead to confusion and from confusion to bugs. Especially if you recently joined the club and haven’t followed the development since day 1 (welcome if it feels I’m talking to you). By default, the Connector will now open in a more straightforward overview where you’re able to add and remove inputs, outputs, or both.
More of a power user that wants the best performance possible for their advanced setup? You can revert via the advanced mode toggle in the view menu.
The Connector will remember your last used view, so you don’t have to toggle the button each session.
If your setup changes, the Connector forgot your old setup when it started. These resets would be frustrating for those who refreshed the com ports or opened the Connector before plugging in their USB cables. I’ve added an extra settings group that splits the saved last used connections from the running connections. If your saved USB isn’t connected, the dropdown will default to “Not connected” when refreshing the com list or starting the Connector. When you reconnect your device and hit refresh, the Connector will load your last setup.
Close to tray / run on startup
This will speak for itself. You’ll find checkboxes for both options giving you control over the application behavior. “Run on startup” doesn’t start the connections by default. I will add this later down the road.
In-game WASM logs
Previously all logs were triggered as errors. A thought inside my head convinced me this was the only option in the SDK. I’d have to confess I was wrong. From this version, logs are placed in the proper channel.