qumarr / macosx-nosleep-extension

Automatically exported from code.google.com/p/macosx-nosleep-extension
0 stars 0 forks source link

Settings are not preserved between disable and renable #78

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Nosleep is configured to work only on Battery (verified via preferences)
2. Currently on battery - icon is black
3. Click to disable - icon is gray
4. Click to enable. Open preferences. Expect to see only Battery checked. I see 
also AC checked

What is the expected output? What do you see instead?
After disable and enable I expect to see the same settings as before disable. 
In this case only battery should be checked.

What version of the product are you using? On what operating system?
NoSleep 1.3.3
MBA Mountain Lion 10.8.3

Original issue reported on code.google.com by beeryhol...@gmail.com on 11 Apr 2013 at 7:48

GoogleCodeExporter commented 8 years ago
Hi,
Thanks for asking. This is a designed behaviour - since 1.3.3 the menu bar icon 
enables/disables both options at once.

You can still use PrefPane to setup NoSleep for different modes.

--Pavel.

Original comment by integral...@gmail.com on 11 Apr 2013 at 7:56

GoogleCodeExporter commented 8 years ago
Hi,

Thanks for the quick reply.

hmmm that's a surprise. Was it mentioned somewhere that I've missed?
I would expect that Disable->Enable would bring me exactly to the same place - 
what was the motivation for this non-standard behavior?

If continue with this behavior, would it be possible to provide it with some UI 
visibility? For example one of the z would be for Battery and one for AC. So if 
only on Battery then the "front" Z is black and "back" Z is gray?

--Beery

Btw, I have many heat issue with strange "Wake Reason" and my current suspect 
is NoSleep. So I'm experimenting a bit with OnSleep on/off and Enable/Disable 
and current new behavior only creates more confusion.

Wake reason: EC.SleepTimer (SleepTimer)
Kernel[0] <Debug>: Wake reason: EC.ACAttach (Maintenance)

Original comment by beeryhol...@gmail.com on 12 Apr 2013 at 3:58

GoogleCodeExporter commented 8 years ago
Issue 82 has been merged into this issue.

Original comment by integral...@gmail.com on 25 Apr 2013 at 10:14

GoogleCodeExporter commented 8 years ago
I agree. Preference selections should be persistent through disable/enable 
cycle. 

Your comment that you can still use PrefPane to setup different modes is 
confusing to me. The preferences set there are the same as those accessed from 
the icon in the menu bar. Since this is the same PrefPane, unsurprisingly the 
behavior is the same. I must be misunderstanding what you are describing. 
Please clarify.

Original comment by zacharyk...@gmail.com on 15 Jun 2013 at 8:10