BindControl v0.21.0.1

v0.21.0.1 - More robust generation of binds directory candidates

This release does a more thorough job of trying to generate a unique profile-specific binds directory. It also checks better for existing profiles' binds directories and will try not to pick those.

The actual upshot is that it's slightly more likely just to throw its hands up and pop up the dialog box asking you for a profile binds dir.

BindControl v0.21

Version 0.21 -- Control over binds directory

This release requires a little explanation. We'll start with a warning:

This release will save profiles in a non-backwards-compatible way. Backing out to a previous version may cause some confusing results. Stick with v0.20.1 if you aren't comfortable moving forward.

With this release, the name of the profile-specific directory where bindfiles are written has been separated from the profile's name. This is to allow Profiles to be named longer and more descriptively, with spaces in the names and so forth, which previously had been disallowed.

One new consequence of this is that the profile name -is- the filename. That is to say, your profile "RadioactivePixie.bcp" is named "RadioactivePixie" going forward. Changing the filename is the same thing as changing the Profile name. There is no longer a separately-editable "Name" field in the UI.

The profile-specific binds directory of existing profiles will not be automatically changed. New profiles will be given a short binds directory name based on the profile name.

The profile-specific binds directory can be changed at any time via the new "Set Binds Location" button at the lower left of the window. Setting a new binds directory will save the profile and offer to delete the previous binds directory.

Profiles will attempt to detect if you assign multiple profiles to the same binds directory, and will warn about this case. You might want to do that for some reason, so if you ignore the warnings, you'll still be able to blast multiple profiles' binds into the same directory. You do you.

This is a bit of an esoteric change, but it created a much more robust Profile loading scheme, as well as a much better initial launch experience for first-time users. Additionally, binds directories will be short by default, which is a good thing in terms of game limitations on keybind lengths.

As always, if you find any bugs (and there will likely be bugs), please open Github issues for them.

Try it out! Thanks, all.

BindControl v0.20.1

Fixes to the Mastermind Release

This release fixes a couple of the known misbehaviors with v0.20, the
"Mastermind Release":

• Multi-word pet names are now fully supported and checked in their
  entirety for uniqueness.
• The warning dialog that some pet names have errors, which is shows at
  write-binds time, will only appear if binds are configured that
  require pet names to exist and be unique. If by-name binds and
  bodyguard mode bind keys are left blank, that dialog will be skipped.

TODO: still might update the red error display on pet names also only
to appear if unique names are required.

BindControl v0.20

The Mastermind Release

This release finally gives some long-overdue love to the Mastermind tab
and binds set.

Changes

• reorganizes the tab to be a bit more intuitive and cleaner
• integrates the classic Sandolphan binds with the by-name selection
  binds and the next/prev pet binds.
• removes the broken parts of "Bodyguard Mode" that CityBinder had added
  long ago that never worked completely.

What works

• Select-by-name now works correctly assuming pet names can be
  uniquely determined. That means that the default pet names for most
  powersets are not going to work, and some pets will need to be renamed
  in-game.
• Any number and combination of pets can be specified for "Bodyguard
  Mode" which is a one-key bind to put the selected pets into Defensive /
  Follow mode.
• The Sandolphan stance and action binds can be applied to all pets,
  pets by power level (minion, lieutenants, boss), or to the selected pet.
  Pets selected by-name and with the next/previous pet binds count for
  this.

What needs work

• The algorithm to determine unique pet names only uses the longest
  word of multi-word pet names. This causes problems distinguishing, for
  instance, between "Howler Wolf" and "Alpha Howler Wolf". This can
  probably be improved.
• Not having unique pet names will cause a warning dialog when you try
  to write binds. This will occur if your archetype is Mastermind,
  regardless of whether the by-name binds or the Sandolphan binds are
  filled out. This will be improved.
• Using the next/previous selection binds will put pets into "chatty"
  mode if they had been toggled into quiet mode. This will hopefully be
  fixed eventually.

Please dust off your Masterminds and give it a spin. As always, please
open issues with anything you find.

BindControl v0.19.5

New logging system

This release incorporates a new scheme for logging errors, warnings,
informational messages, and so forth.

Visually, the Log Window remains and will act as it always has. Serious
errors and warnings will surface in a small informational bar at the
bottom of the app.

The existing messages have been reviewed and categorized to keep
non-critical informational messages from appearing in the infobar.

Going forward, the Log Window is likely to start to see more traffic, as
the new infrastructure gets used more for debugging and troubleshooting
messages.

BindControl v0.19.4.1

Strip executable when building on MacOS and Linux

BindControl v0.19.4

Add "Fill Tray" buttons to Gameplay page

v0.20 Prerelease 6 - select binds directory

This merges all the various changes that have been made to the main branch recently, including the new logging scheme and the "Fill" buttons for the tray binds on the Gameplay tab.

It also incorporates a big handful of tweaks to behavior around "owned" profile binds directories, and loading profiles from file.

This is starting to angle towards being ready for a release to get it in the larger world's hands.

v0.20 Prerelease 5.0.1 - select binds directory

This is a quickfix for select_binds_dir_prerelease5, which on Windows was never dismissing the new "Startup Panel" and instantiating the profile behind it where it couldn't be seen.

v0.20 Prerelease 5 - select binds directory

This prerelease offers a new flow for the initial launch of the app, as well as anyone who had their preference for "Start With" set to "New Profile" -- the app will start with two large buttons offering to start a new profile or load an existing one.

This required some nontrivial plumbing work in the supporting code to set up an app window at all that didn't contain a profile, and as such, it might still contain bugs, some of them even crashes. I've tested many paths through this but if you find anything weird and/or unexpected, please start an issue or weigh in on #51.

The "Start With" preference has changed to a simple checkbox for "Start With Last Profile" which is checked by default. If you had a previous setting of "Start With" it will be honored by the new code.

There are some other smaller updates including slightly smarter detection of existing profiles when making a new profile and slightly smarter detection of existing binds directories when setting the binds location. Both of these areas could still improve, and will.