google-code-export / zscreen

Automatically exported from code.google.com/p/zscreen
1 stars 0 forks source link

ZScreen is not saving configuration of actions #512

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Select two actions
2. Deselect one action
3. Close and Open ZScreen, both actions will be checked

What is the expected output? What do you see instead?
Save configuration is expected.

What version of the product are you using? On what operating system?
Copy text from Debug tab

Please provide any additional information below.

Original issue reported on code.google.com by jjnil...@gmail.com on 26 Jul 2011 at 11:33

GoogleCodeExporter commented 9 years ago
I'm having this issue as well. Zscreen keeps deselecting clipboard, even if I 
minimize it to tray first, which is supposed to help.

Original comment by mopqu...@gmail.com on 30 Jul 2011 at 3:02

GoogleCodeExporter commented 9 years ago
Regarding "Zscreen keeps deselecting clipboard" where is Clipboard listed under 
Actions?

Original comment by mcored on 11 Aug 2011 at 12:37

GoogleCodeExporter commented 9 years ago
Sorry there is no "Clipboard" in actions

http://mcored.zscreen.net/2011-08/2011-08-21_09.18.08-ZScreen_4.2.4_rev_2419.png

Original comment by mcored on 21 Aug 2011 at 1:19

GoogleCodeExporter commented 9 years ago
I believe he means under output. That is what I mean, at least.

http://www.emulysianfields.com/images/personal/screenshots/screen_2011-08-20_071
7.png

It seemed to save on a previous version if you set it, closed the window, 
exited the program, and re-opened it. I'm currently on the latest dev version, 
which is not the build I was experiencing this on, but I haven't touched the 
setting since I tricked it into saving, and I'm not eager to find out if it's 
still there.

Original comment by mopqu...@gmail.com on 21 Aug 2011 at 1:22

GoogleCodeExporter commented 9 years ago
if you set it, closed the window, exited the program, and re-opened it - thanks 
for clarifying that :)

I did all those steps and cannot reproduce the bug so I believe this is fixed. 

Original comment by mcored on 24 Aug 2011 at 11:09