crispd / issues

issues for Eric to work on ... all projects that don't have a home
2 stars 0 forks source link

Enable/Disable ALL checkbox #13

Closed crispd closed 9 years ago

crispd commented 9 years ago

The screen now comes up disabled, as it should. And an initial click on the enable all checkbox will enable all devices as expected. The Issue is this checkboxe's ability to be toggled back and fourth in intervals of at least 2 seconds. I notice when removing focus from the screen, then trying the checkbox again that it will work but I have to do that each time I want to check or uncheck the box.

crispd commented 9 years ago

Upon re-creating this issue, this checkbox toggled as expected, I'm unsure why it didn't seem to work well at first.

crispd commented 9 years ago

This is a reacurring issue, I'm unsure what triggers it. But there are times when the checkbox can not be correctly toggled. The issue is not related to the time one must allow for all devices to be enabled or disabled.

dxmaxwell commented 9 years ago

I have not been able to reproduce this behavior on my own Win7 VM. I would not be entirely surprised it there was an issue because I'm doing something unusual with the focus on checkboxes to try and work around the "spacebar problem".

On Tue, Dec 2, 2014 at 12:40 PM, DanC notifications@github.com wrote:

This is a reacurring issue, I'm unsure what triggers it. But there are times when the checkbox can not be correctly toggled. The issue is not related to the time one must allow for all devices to be enabled or disabled.

— Reply to this email directly or view it on GitHub https://github.com/crispd/issues/issues/13#issuecomment-65271314.

crispd commented 9 years ago

Well the issue is somewhat intermittent.. possibly indicating that it won't be easily reproduceable. Is there any way that unfocusing the checkbox disallows a successive refocus? Something that is more properly done when focusing on an exterior window that isn't happening after you 'defocus' the checkbox for the space bar?

crispd commented 9 years ago

This seems to have been solved with the update that was tested ~30 April.