fix disabled hardware variable save button bug#122
fix disabled hardware variable save button bug#122ThomasAkam merged 1 commit intopyControl:masterfrom
Conversation
If the hardware variables for multiple setups are being edited, the save button will only become enabled if the last variable in the table has changed. This fixes the bug so that the save button becomes enabled if any of the variables is changed.
alustig3
changed the title
|
Hi @alustig3, I somehow missed this and just saw it when looking at the repo for something else. Apologies for the very long delay! |
|
@ThomasAkam, I wanted to mention, for the next time you make a release on GitHub, it might be best to make a fresh release instead of editing the current v2 release. The only reason I say this is because this website can track downloads of the releases, which can be useful. But if you edit a release, the download count gets reset and only shows downloads of the latest version of that release (for instance when v2.0.2 was released as an edit to v2.0.1, all of the v.2.0.1 downloads that were counted were lost and the count was set back to 0). |
|
Hi @alustig3, good to know abou that website, I will make sure I only do new releases rather than editing old ones in future. |
If the hardware variables for multiple setups are being edited, the save button will only become enabled if the last variable in the table has changed. This fixes the bug so that the save button becomes enabled if any of the variables is changed.
2 participants
hw_save_button_disabled.mp4
If the hardware variables for multiple setups are being edited, the save button will only become enabled if the last variable in the table has changed. This fixes the bug so that the save button becomes enabled if any of the variables is changed.