Skip to content

Releases: emersonrp/bindcontrol

BindControl v0.21.6.1

07 Jan 17:42
Compare
Choose a tag to compare

Change autobuild for Mac to macos-14, since macos-12 deprecated. No other changes.

BindControl v0.21.6

07 Jan 17:30
Compare
Choose a tag to compare

Two little bugfixes:

-- Double-click was not working correctly in the Key Select dialog, and
therefore wasn't making it into binds correctly. Fixed.

(Use KeySelectDialog self.Keymap correctly in OnMouseEvent.)

-- After loading an existing profile (except during initial startup), or
creating a new one, keybind conflict checking would silently stop
working.

(Always use wx.App.Get().Main.Profile, instead of wx.App.Get().Profile,
if getting the profile that way.)

BindControl v0.21.5

04 Aug 20:09
Compare
Choose a tag to compare

Add Next / Prev Tray buttons to Gameplay tab

BindControl v0.21.4

24 Jul 16:08
Compare
Choose a tag to compare

Add new powerset and accolade powers from Issue 28; icons to match

BindControl v0.21.3

23 Jul 21:56
Compare
Choose a tag to compare

Add "Chatty is default" preference to Mastermind Page

This release adds a "chatty is default" checkbox to the Mastermind page,
which will select whether pets reset to chatty or non-chatty mode when
the Binds Reset key is pressed.

It also fixes a misbehavior bug when "Load Last Profile" is selected as
a preference and the last profile can't be found, ie, has been deleted
or moved.

BindControl v0.21.2.1

15 Jul 15:42
Compare
Choose a tag to compare

Do a little dance with Show() and Raise() on the write-binds results dialog

BindControl v0.21.2

08 Jul 04:58
Compare
Choose a tag to compare

Updates to Binds Directory window; better handling of "profile modified" dialog

v0.21 release notes:

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.21.1

07 Jul 22:17
Compare
Choose a tag to compare

Addition of new Help > Binds Directories window.

v0.21 release notes:

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.21.0.3

06 Jul 15:45
Compare
Choose a tag to compare

Fix bug with one-word existing profile names without ProfileBindsDir

v0.21 release notes:

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.21.0.2

04 Jul 19:06
Compare
Choose a tag to compare

Bugfixes: Make sure InfoBar stays at the bottom; rename a variable

v0.21 release notes:

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.