blacktree-nocturne - Project Hosting on Google Code

Last 7 days Jan 02, 2010 issue 9 (Automatic switching with light sensors does not work with ne...) commented on by Olli86 - Can someone please upload a compiled version with the included patch? Thanks in advance. Can someone please upload a compiled version with the included patch? Thanks in advance. Last 30 days Dec 22, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by dzturbd - Using version 2.0.0 For those who (like me) lack the programming skills needed to try the above fixes, quitting Nocturn restores normal colors. If you quit Nocturn while in night mode then restarting it will restore night mode. If you quit while in the screwed up version of day mode, then restarting Nocturn will alter the menu bar and may do some other odd things, but putting it into night mode works fine. Using version 2.0.0 For those who (like me) lack the programming skills needed to try the above fixes, quitting Nocturn restores normal colors. If you quit Nocturn while in night mode then restarting it will restore night mode. If you quit while in the screwed up version of day mode, then restarting Nocturn will alter the menu bar and may do some other odd things, but putting it into night mode works fine. Dec 15, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by milligil - The patch in comment #6 works for me (version 2.0.0 svn r17). To build on OSX 10.6.2 I needed to change the SDKROOT as well, since the macosx10.4 sdk root was not available. The patch in comment #6 works for me (version 2.0.0 svn r17). To build on OSX 10.6.2 I needed to change the SDKROOT as well, since the macosx10.4 sdk root was not available. Older Nov 25, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by t...@tulpe-media.de - The fix is still not included (version 2.0.0). Can there anything be done about this? (Except compiling the app on my own) The fix is still not included (version 2.0.0). Can there anything be done about this? (Except compiling the app on my own) Nov 24, 2009 issue 20 (Light sensor transition does not trigger if the sensor itsel...) reported by mrouthier - What steps will reproduce the problem? 1. Put something opaque on top of the light sensor 2. See the light sensor value drop to -1 3. See that it's not switching, even though the checkbox is checked What is the expected output? What do you see instead? Night mode should switch What version of the product are you using? On what operating system? Ncturne 1.0.4 on SnowLeopard (10.6.2) on a MacBook Pro 13". Please provide any additional information below. What steps will reproduce the problem? 1. Put something opaque on top of the light sensor 2. See the light sensor value drop to -1 3. See that it's not switching, even though the checkbox is checked What is the expected output? What do you see instead? Night mode should switch What version of the product are you using? On what operating system? Ncturne 1.0.4 on SnowLeopard (10.6.2) on a MacBook Pro 13". Please provide any additional information below. Nov 20, 2009 issue 19 (Invert Hue only works in one space) reported by axiixc - What steps will reproduce the problem? 1. Open Nocturne (1.0.4) 2. Enable night mode, disable monochrome, enable invert hue 3. Switch to new space What is the expected output? What do you see instead? The inverted colors only persist in the space where the setting was changed, all over spaces have normal hue. What version of the product are you using? On what operating system? Nocturne 1.0.4 Snow Leopard 10.6.2 Aluminum MacBook Pro What steps will reproduce the problem? 1. Open Nocturne (1.0.4) 2. Enable night mode, disable monochrome, enable invert hue 3. Switch to new space What is the expected output? What do you see instead? The inverted colors only persist in the space where the setting was changed, all over spaces have normal hue. What version of the product are you using? On what operating system? Nocturne 1.0.4 Snow Leopard 10.6.2 Aluminum MacBook Pro Oct 16, 2009 issue 18 (Nocturne does not retain night colors) reported by davidbjames1 - What steps will reproduce the problem? 1. Select Tint Colors 2. Switch to Night Mode 3. Activate Screen Saver (or put to sleep, or switch users) 4. Return to Desktop What is the expected output? What do you see instead? Expected: retain tint Instead: day colors What version of the product are you using? On what operating system? 1.0.4 Please provide any additional information below. Great product! What steps will reproduce the problem? 1. Select Tint Colors 2. Switch to Night Mode 3. Activate Screen Saver (or put to sleep, or switch users) 4. Return to Desktop What is the expected output? What do you see instead? Expected: retain tint Instead: day colors What version of the product are you using? On what operating system? 1.0.4 Please provide any additional information below. Great product! Oct 04, 2009 issue 17 (When dimming menu bar is on, it also inverts the menu bar.) reported by flintr94 - What steps will reproduce the problem? 1. Open preferences 2. Check "Dim when active" 3. Switch to "Day" 4. Click on ANY other application What is the expected output? What do you see instead? It's supposed to simply dim the menu bar, but it also inverts the color of the menu bar. What version of the product are you using? On what operating system? I'm using 2.0.0 on 10.5.8, on a Macbook Pro (Not unibody.) Please provide any additional information below. This does not happen while Nocturne is set to "Night" mode. What steps will reproduce the problem? 1. Open preferences 2. Check "Dim when active" 3. Switch to "Day" 4. Click on ANY other application What is the expected output? What do you see instead? It's supposed to simply dim the menu bar, but it also inverts the color of the menu bar. What version of the product are you using? On what operating system? I'm using 2.0.0 on 10.5.8, on a Macbook Pro (Not unibody.) Please provide any additional information below. This does not happen while Nocturne is set to "Night" mode. Oct 01, 2009 issue 16 (AXDescription missing) reported by macagp - I am trying to write an AppleScript to trigger Nocturne and the absence of AXDescription is making that impossible. The Accessibilty Inspector reports: <AXApplication: "Nocturne"> <AXButton> Attributes: AXRole: "AXButton" AXRoleDescription: "button" AXHelp: "(null)" AXEnabled: "true" AXFocused: "false" AXParent: "<AXApplication: "Nocturne">" AXWindow: "(null)" AXTopLevelUIElement: "(null)" AXPosition: "x=1261 y=0" AXSize: "w=22 h=22" AXTitle: "" Actions: AXPress - press Errors: AXTopLevelUIElement: Unable to get the value (kAXErrorNoValue) AXWindow: Unable to get the value (kAXErrorNoValue) AXParent: UIElement is not included as a child of the parent AXApplication. Warnings: AXDescription or AXTitleUIElement: Missing. Optional Attributes: AXValueDescription AXChildren AXDescription AXSubrole AXTitleUIElement AXLinkedUIElements AXValue AXEdited What version of the product are you using? On what operating system? 2.0 I am trying to write an AppleScript to trigger Nocturne and the absence of AXDescription is making that impossible. The Accessibilty Inspector reports: <AXApplication: "Nocturne"> <AXButton> Attributes: AXRole: "AXButton" AXRoleDescription: "button" AXHelp: "(null)" AXEnabled: "true" AXFocused: "false" AXParent: "<AXApplication: "Nocturne">" AXWindow: "(null)" AXTopLevelUIElement: "(null)" AXPosition: "x=1261 y=0" AXSize: "w=22 h=22" AXTitle: "" Actions: AXPress - press Errors: AXTopLevelUIElement: Unable to get the value (kAXErrorNoValue) AXWindow: Unable to get the value (kAXErrorNoValue) AXParent: UIElement is not included as a child of the parent AXApplication. Warnings: AXDescription or AXTitleUIElement: Missing. Optional Attributes: AXValueDescription AXChildren AXDescription AXSubrole AXTitleUIElement AXLinkedUIElements AXValue AXEdited What version of the product are you using? On what operating system? 2.0 Sep 28, 2009 Glow.png (Glow background) file uploaded by j...@gmail.com Sep 27, 2009 r17 (2.0.0) committed by j...@gmail.com - 2.0.0 2.0.0 Sep 27, 2009 Nocturne.2.0.0.zip (Nocturne 2.0.0 (10.5+)) file uploaded by j...@gmail.com - Labels: Featured Labels: Featured Sep 27, 2009 Nocturne.2.0.0.zip (Nocturne 2.0.0) file uploaded by j...@gmail.com - Labels: Featured Labels: Featured Sep 27, 2009 r16 (2.0.0) committed by j...@gmail.com - 2.0.0 2.0.0 Sep 27, 2009 r15 (remove old nib) committed by j...@gmail.com - remove old nib remove old nib Sep 27, 2009 r14 (2.0.0) committed by j...@gmail.com - 2.0.0 2.0.0 Sep 22, 2009 issue 12 (Request: Global keybinding) commented on by untoldwind - I tried a completely different approach: I've added a service method to Nocturne. Then you can assign a global hotkey using System Preferences->Keyboard->Shortcut (at least with Snow Leopard). This has the charm that the shortcut is really global (i.e. even if Nocturne is not running it will be automatically started). Here's what I did: Added to Info.plist: <key>NSServices</key> <array> <dict> <key>NSKeyEquivalent</key> <dict> <key>default</key> <string>T</string> </dict> <key>NSMenuItem</key> <dict> <key>default</key> <string>Nocturne Toggle</string> </dict> <key>NSMessage</key> <string>serviceToggle</string> <key>NSPartName</key> <string>Nocturne</string> </dict> </array> Added to QSNocturneController.m - (void)serviceToggle:(NSPasteboard )pboard userData:(NSString )userData error:(NSString *)error { [self toggle]; } and a [[NSApplication sharedApplication] setServicesProvider:self]; to - (void)awakeFromNib That's it. Once you have the Nocturne.app in you Applications folder the service will be automatically added to the System Preference's shortcut menu after login. Sorry, but I can't provide a patch for this feature alone. I've attached a diff with my acumulated patches so far: - Optional automatic disable/re-enable on power-safe - Fix for the Tint-Bug - Minor fix for some uggly CGSetDisplay... messages poluting the log - The service described above I tried a completely different approach: I've added a service method to Nocturne. Then you can assign a global hotkey using System Preferences->Keyboard->Shortcut (at least with Snow Leopard). This has the charm that the shortcut is really global (i.e. even if Nocturne is not running it will be automatically started). Here's what I did: Added to Info.plist: <key>NSServices</key> <array> <dict> <key>NSKeyEquivalent</key> <dict> <key>default</key> <string>T</string> </dict> <key>NSMenuItem</key> <dict> <key>default</key> <string>Nocturne Toggle</string> </dict> <key>NSMessage</key> <string>serviceToggle</string> <key>NSPartName</key> <string>Nocturne</string> </dict> </array> Added to QSNocturneController.m - (void)serviceToggle:(NSPasteboard )pboard userData:(NSString )userData error:(NSString )error { [self toggle]; } and a [[NSApplication sharedApplication] setServicesProvider:self]; to - (void)awakeFromNib That's it. Once you have the Nocturne.app in you Applications folder the service will be automatically added to the System Preference's shortcut menu after login. Sorry, but I can't provide a patch for this feature alone. I've attached a diff with my acumulated patches so far: - Optional automatic disable/re-enable on power-safe - Fix for the Tint-Bug - Minor fix for some uggly CGSetDisplay... messages poluting the log - The service described above Sep 22, 2009 issue 13 (After power save causes screen to disable, on restore tint i...) commented on by untoldwind - I've created a little hack for this feature: Nocturne disables right before the screen server or power saver and automatically enables after the re-login. Unluckily there is some ugly flickering involved, so I'm not sure if I can actually recommend this solution. Though it's still better than an eye-burning screen saver ;) I've created a little hack for this feature: Nocturne disables right before the screen server or power saver and automatically enables after the re-login. Unluckily there is some ugly flickering involved, so I'm not sure if I can actually recommend this solution. Though it's still better than an eye-burning screen saver ;) Sep 22, 2009 issue 13 (After power save causes screen to disable, on restore tint i...) commented on by untoldwind - Actually I'd like to see that nocturne switches back to day vision right before either the screen saver or power save is triggered. Simple reson: - Most screen saver already have a dark background and are simply too bright in night vision (... and of course look rather ugly too ;) ) - I've configured my system to re-login after power safe. The login screen is too bright in night vision as well (mostly black background) Would be nice to have an option like this configurable. Actually I'd like to see that nocturne switches back to day vision right before either the screen saver or power save is triggered. Simple reson: - Most screen saver already have a dark background and are simply too bright in night vision (... and of course look rather ugly too ;) ) - I've configured my system to re-login after power safe. The login screen is too bright in night vision as well (mostly black background) Would be nice to have an option like this configurable. Sep 22, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by n...@natesilva.com - That worked perfectly. I hope the project maintainer will incorporate this fix. That worked perfectly. I hope the project maintainer will incorporate this fix. Sep 22, 2009 issue 9 (Automatic switching with light sensors does not work with ne...) commented on by untoldwind - For some reson either the (new?) MacBook Pro or the new OS seems to have a total different scaling in concerning light sensors. On my system IOConnectMethodScalarIScalarO(...) get's values somewhere between 100000 and 1000000 (the preferences pane does not have enough digits to display this correctly). I've created a small hack: If the light sensor values are beyond 10000 they are divided by 1000. Not sure if this will work on every system, but it fixes the problem for me. For some reson either the (new?) MacBook Pro or the new OS seems to have a total different scaling in concerning light sensors. On my system IOConnectMethodScalarIScalarO(...) get's values somewhere between 100000 and 1000000 (the preferences pane does not have enough digits to display this correctly). I've created a small hack: If the light sensor values are beyond 10000 they are divided by 1000. Not sure if this will work on every system, but it fixes the problem for me. Sep 22, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by untoldwind - Quite simple to patch: For some reason the "updateGamma" is called again after everything switched back to day vision. I just added and additional check for the enabled flag. This fixes the problem for me. Quite simple to patch: For some reason the "updateGamma" is called again after everything switched back to day vision. I just added and additional check for the enabled flag. This fixes the problem for me. Aug 22, 2009 issue 15 (Progress bar "scrambled" visual glitch on CoverSutra Player ...) reported by ultravoila - What steps will reproduce the problem? 1. Switch to Night when Nocturne set to Monochrome 2. Bring up CoverSutra Player Controls window What is the expected output? What do you see instead? The track playing has a progress bar. Works fine with other settings until Monochrome is selected, then it scrambles the display of the progress bar. What version of the product are you using? On what operating system? OS X 10.5.8 MBP running Nocturne 1.0.6 (also experienced on 1.0.4) Please provide any additional information below. Attached screenshot of it proper and a camera shot of it jumbled. When taking a screen shot of the scrambled bar, it fixes itself, I guess it refreshes. Weird bug, really not a big deal. What steps will reproduce the problem? 1. Switch to Night when Nocturne set to Monochrome 2. Bring up CoverSutra Player Controls window What is the expected output? What do you see instead? The track playing has a progress bar. Works fine with other settings until Monochrome is selected, then it scrambles the display of the progress bar. What version of the product are you using? On what operating system? OS X 10.5.8 MBP running Nocturne 1.0.6 (also experienced on 1.0.4) Please provide any additional information below. Attached screenshot of it proper and a camera shot of it jumbled. When taking a screen shot of the scrambled bar, it fixes itself, I guess it refreshes. Weird bug, really not a big deal. Aug 05, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by sybersnake - I can confirm this on 10.5.7 I can confirm this on 10.5.7 May 28, 2009 issue 12 (Request: Global keybinding) commented on by mr.chesley - there is one small issue with this that i just noticed. when activated through the menu bar icon, the application that currently has focus keeps it. when i activate Nocturne using quicksilver or through a quicksilver trigger, the top application loses focus and must be re-focused. there is one small issue with this that i just noticed. when activated through the menu bar icon, the application that currently has focus keeps it. when i activate Nocturne using quicksilver or through a quicksilver trigger, the top application loses focus and must be re-focused. May 26, 2009 issue 12 (Request: Global keybinding) changed by papercrane - Status: Labels: Type-Enhancement −Type-Defect Status: Labels: Type-Enhancement −Type-Defect May 26, 2009 issue 12 (Request: Global keybinding) commented on by dreamcat4 - Thank you for responding on this - I never knew that. Please consider this support issue closed :) Thank you for responding on this - I never knew that. Please consider this support issue closed :) May 26, 2009 issue 14 (Autodetect and mask large light colored regions) commented on by mr.chesley - i was annoyed with Terminal windows being bright when nocturne is activated, so i wrote a ruby script that toggles the themes of each Terminal window before activating nocturne: http://john.cheslicious.com/projects/nocterm.html now i need to figure out how to do the same thing with my aquamacs windows, and i'll be golden. i was annoyed with Terminal windows being bright when nocturne is activated, so i wrote a ruby script that toggles the themes of each Terminal window before activating nocturne: http://john.cheslicious.com/projects/nocterm.html now i need to figure out how to do the same thing with my aquamacs windows, and i'll be golden. May 26, 2009 issue 12 (Request: Global keybinding) commented on by mr.chesley - you could use a quicksilver trigger that runs Nocturne. If it's already running, running it again toggles between night vision and normal mode. you could use a quicksilver trigger that runs Nocturne. If it's already running, running it again toggles between night vision and normal mode. Apr 16, 2009 issue 14 (Autodetect and mask large light colored regions) Labels changed by papercrane - Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium Apr 16, 2009 issue 14 (Autodetect and mask large light colored regions) reported by bsrini - The only issue with Nocturne is that some applications (such as Firefox) alternate light background content with dark background content. The dark content becomes a bright flash and can be very disturbing late at night. For example, if you close a full screen Terminal it will produce a bright flash. One way to get around this would be to detect and mask large regions that would be rendered as light colored. This would ensure that all* windows and displays were dark at all times. I'm not a GUI programmer, but I assume that you have access to each frame before it's displayed on screen as well as each window. Pseudocode would then be something like this: for each rendered frame for each window in that frame determine if the window is majority light or dark (simple heuristic would work) if it is majority light, then render as dark using standard nocturne if it is majority dark, then it would be rendered as light using standard nocturne. Instead, refrain from inverting the colors in this region so that the normal dark display applies. This is a per-frame computation but would be pretty fast -- basically just summing up the fluorescence in each window before it's rendered. An more sophisticated algorithm would actually look at UI elements within each window -- for example, some web sites may have dark borders that become disturbingly light under Nocturne. What you could do then is segment the region into clusters of local fluorescence intensity and invert or leave uninverted as necessary. This segmentation would be tricky to get fast and right, but it would ensure that Nocturne never rendered a large bright flash. The only issue with Nocturne is that some applications (such as Firefox) alternate light background content with dark background content. The dark content becomes a bright flash and can be very disturbing late at night. For example, if you close a full screen Terminal it will produce a bright flash. One way to get around this would be to detect and mask large regions that would be rendered as light colored. This would ensure that all windows and displays were dark at all times. I'm not a GUI programmer, but I assume that you have access to each frame before it's displayed on screen as well as each window. Pseudocode would then be something like this: for each rendered frame for each window in that frame determine if the window is majority light or dark (simple heuristic would work) if it is majority light, then render as dark using standard nocturne if it is majority dark, then it would be rendered as light using standard nocturne. Instead, refrain from inverting the colors in this region so that the normal dark display applies. This is a per-frame computation but would be pretty fast -- basically just summing up the fluorescence in each window before it's rendered. An more sophisticated algorithm would actually look at UI elements within each window -- for example, some web sites may have dark borders that become disturbingly light under Nocturne. What you could do then is segment the region into clusters of local fluorescence intensity and invert or leave uninverted as necessary. This segmentation would be tricky to get fast and right, but it would ensure that Nocturne never rendered a large bright flash. Mar 08, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by canburak - bug confirmed by me also. I tried to capture it via screenflow but it doesn't record the wizardry of nocturne. bug confirmed by me also. I tried to capture it via screenflow but it doesn't record the wizardry of nocturne. Feb 20, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by han.yuan - Same issue here with a gen 2 MBA Same issue here with a gen 2 MBA Feb 14, 2009 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by dkuntz - I can confirm this bug also with 10.5.6, on a Rev3 MPB with 4GB ram. 1.0.4 did not do this, but in a multi- monitor setup, the tint feature did not work properly (main screen/external monitor would tint, MBP screen would just invert, which was blinding as my default BG is black) I can confirm this bug also with 10.5.6, on a Rev3 MPB with 4GB ram. 1.0.4 did not do this, but in a multi- monitor setup, the tint feature did not work properly (main screen/external monitor would tint, MBP screen would just invert, which was blinding as my default BG is black) Feb 12, 2009 issue 9 (Automatic switching with light sensors does not work with ne...) commented on by han.yuan - When I put my thumb over the light sensor on my Gen 2 MBA, the lowest value I receive is 2263. On an overcast day with ambient light, I am seeing sensor values in the 4000s. Somehow the values for measuring ambient light for the newer Apple hardware is inconsistent on the newer hardware platforms. I'd really love this feature but I can imagine that if the API is not yielding consistent values for different hardware platforms this could be very difficult to fix. When I put my thumb over the light sensor on my Gen 2 MBA, the lowest value I receive is 2263. On an overcast day with ambient light, I am seeing sensor values in the 4000s. Somehow the values for measuring ambient light for the newer Apple hardware is inconsistent on the newer hardware platforms. I'd really love this feature but I can imagine that if the API is not yielding consistent values for different hardware platforms this could be very difficult to fix. Feb 12, 2009 issue 13 (After power save causes screen to disable, on restore tint i...) reported by han.yuan - What steps will reproduce the problem? 1. Configure nocturne to use a tint. 2. Trigger screen to turn off (either through power savings or through hot corner) 3. Twitch mouse or type on keyboard What is the expected output? What do you see instead? Screen is now monochrome (but still night mode) instead of in tinted mode. What version of the product are you using? On what operating system? Version 1.0.6, Leopard 10.5.6 Please provide any additional information below. What steps will reproduce the problem? 1. Configure nocturne to use a tint. 2. Trigger screen to turn off (either through power savings or through hot corner) 3. Twitch mouse or type on keyboard What is the expected output? What do you see instead? Screen is now monochrome (but still night mode) instead of in tinted mode. What version of the product are you using? On what operating system? Version 1.0.6, Leopard 10.5.6 Please provide any additional information below. Feb 11, 2009 issue 9 (Automatic switching with light sensors does not work with ne...) commented on by jon.chui - same for me! it doesn't work on the first gen macbook air same for me! it doesn't work on the first gen macbook air Feb 09, 2009 issue 9 (Automatic switching with light sensors does not work with ne...) commented on by han.yuan - Also does not work on Gen 2 MBA as well. Also does not work on Gen 2 MBA as well. Feb 03, 2009 issue 12 (Request: Global keybinding) reported by dreamcat4 - Nocturne could really do with a global keybinding. There would simply be just one user-assignable keybinding - to toggle day / night mode. Reasons: 1. Overall, some users are desktop users and therefore don't have a light sensor in their computer. 2. Laptop users may want a convenient manual control in addition to the auto-sensor. How to implement: Global keybindings can't be done in Cocoa. You must use a call which is part of the old Carbon API. There are enough examples on the web, including a sample project from Apple. Look for "RegisterEventHotKey" in Carbon API reference http://developer.apple.com/DOCUMENTATION/Carbon/reference/Carbon_Event_Manager_Ref/Reference/reference.html Other Links: http://developer.apple.com/samplecode/FunkyOverlayWindow/listing7.html http://www.cocoabuilder.com/archive/message/cocoa/2005/5/10/135502 http://www.red-sweater.com/blog/181/the-cocoa-carbon-advantage http://stackoverflow.com/questions/324032/how-do-i-get-keyboard-events-in-an-nsstatuswindowlevel-window-while- my-applicat http://forum.soft32.com/mac/hotkey-ftopict44116.html Nocturne could really do with a global keybinding. There would simply be just one user-assignable keybinding - to toggle day / night mode. Reasons: 1. Overall, some users are desktop users and therefore don't have a light sensor in their computer. 2. Laptop users may want a convenient manual control in addition to the auto-sensor. How to implement: Global keybindings can't be done in Cocoa. You must use a call which is part of the old Carbon API. There are enough examples on the web, including a sample project from Apple. Look for "RegisterEventHotKey" in Carbon API reference http://developer.apple.com/DOCUMENTATION/Carbon/reference/Carbon_Event_Manager_Ref/Reference/reference.html Other Links: http://developer.apple.com/samplecode/FunkyOverlayWindow/listing7.html http://www.cocoabuilder.com/archive/message/cocoa/2005/5/10/135502 http://www.red-sweater.com/blog/181/the-cocoa-carbon-advantage http://stackoverflow.com/questions/324032/how-do-i-get-keyboard-events-in-an-nsstatuswindowlevel-window-while- my-applicat http://forum.soft32.com/mac/hotkey-ftopict44116.html Dec 27, 2008 issue 10 (Terminal and Safari have scrambled characters) commented on by darnell....@gmx.net - Sorry, I got the version info wrong! I am using 1.0.6, not 1.0.4 of nocturne! dT Sorry, I got the version info wrong! I am using 1.0.6, not 1.0.4 of nocturne! dT Dec 27, 2008 issue 10 (Terminal and Safari have scrambled characters) reported by darnell....@gmx.net - What steps will reproduce the problem? 1. Switch nocturne to night mode 2. Open Terminal or 3. Open Safari The Terminal line showing the prompt has scrambled character and will often now allow recognizing a single character from the user input after the prompt. Same thing happens when a html page loaded in Safari defines css-rules that make the text color or background of a link text change while hovering with the mouse. 1.0.4 on OS X 10.5.5 Thank you for this excellent program! What steps will reproduce the problem? 1. Switch nocturne to night mode 2. Open Terminal or 3. Open Safari The Terminal line showing the prompt has scrambled character and will often now allow recognizing a single character from the user input after the prompt. Same thing happens when a html page loaded in Safari defines css-rules that make the text color or background of a link text change while hovering with the mouse. 1.0.4 on OS X 10.5.5 Thank you for this excellent program! Dec 15, 2008 issue 9 (Automatic switching with light sensors does not work with ne...) reported by kerenwieser - What steps will reproduce the problem? 1. Use the new (Nov. 2008) MacBook Pro and Nocturne 1.0.6 2. Set 'Use light sensors to switch' ON 3. Set lighting spectrum to any reasonable numbers 4. Work in a low-light environment (that would trigger Nocturne with same numbers on the old MacBook Pro) What is the expected output? What do you see instead? Night mode is expected, and it never changes. Also, actual lighting levels on the Preferences window seem extremely high all the time. What version of the product are you using? On what operating system? Nocturne 1.0.6 with OS X 10.5.5 Please provide any additional information below. What steps will reproduce the problem? 1. Use the new (Nov. 2008) MacBook Pro and Nocturne 1.0.6 2. Set 'Use light sensors to switch' ON 3. Set lighting spectrum to any reasonable numbers 4. Work in a low-light environment (that would trigger Nocturne with same numbers on the old MacBook Pro) What is the expected output? What do you see instead? Night mode is expected, and it never changes. Also, actual lighting levels on the Preferences window seem extremely high all the time. What version of the product are you using? On what operating system? Nocturne 1.0.6 with OS X 10.5.5 Please provide any additional information below. Dec 01, 2008 issue 5 (suggestion/request) commented on by traisjames - There is a program called CronniX. its hard to figure out, but what I did was set hour to 11, then everything else to . then for the command, I used "/usr/bin/open /Applications/Utilities/Nocturne.app" (I put Nocture into my utilities folder. If you want to turn it off automaticly, use "killall Nocturne". CronniX edits the Cron scripts which is responciable for maintanince of OS X There is a program called CronniX. its hard to figure out, but what I did was set hour to 11, then everything else to . then for the command, I used "/usr/bin/open /Applications/Utilities/Nocturne.app" (I put Nocture into my utilities folder. If you want to turn it off automaticly, use "killall Nocturne". CronniX edits the Cron scripts which is responciable for maintanince of OS X Dec 01, 2008 issue 8 (Tint + Hide desktop modes don't work with dual monitor) commented on by gordon.thompson - Many apologies, i didn't know there was another version available. This seems to fix the problem. Thanks Many apologies, i didn't know there was another version available. This seems to fix the problem. Thanks Dec 01, 2008 issue 4 (help info) Labels changed by papercrane - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Dec 01, 2008 issue 5 (suggestion/request) Labels changed by papercrane - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Dec 01, 2008 issue 6 (Request: Per-application settings) Labels changed by papercrane - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Dec 01, 2008 issue 8 (Tint + Hide desktop modes don't work with dual monitor) Status changed by papercrane - Please try 1.0.6 from the google code site, it should have most multi-monitor problems fixed. Status: Invalid Please try 1.0.6 from the google code site, it should have most multi-monitor problems fixed. Status: Invalid Nov 30, 2008 issue 8 (Tint + Hide desktop modes don't work with dual monitor) reported by gordon.thompson - What steps will reproduce the problem? 1. Open Nocturne on a dual monitor system 2. Select tint mode or hide desktop mode What is the expected output? What do you see instead? It ignores the values on the second monitor. The primary monitor works correctly though What version of the product are you using? On what operating system? 1.0.4 on OS X 10.5.5 on an imac 24" Please provide any additional information below. What steps will reproduce the problem? 1. Open Nocturne on a dual monitor system 2. Select tint mode or hide desktop mode What is the expected output? What do you see instead? It ignores the values on the second monitor. The primary monitor works correctly though What version of the product are you using? On what operating system? 1.0.4 on OS X 10.5.5 on an imac 24" Please provide any additional information below. Sep 02, 2008 issue 7 (Nocturne does not restore day mode colors if "Tint Colors" i...) commented on by nate+goo...@natesilva.com - More notes: This also happens with Nocturne 1.0.5. It does not happen with version 1.0.4. More notes: This also happens with Nocturne 1.0.5. It does not happen with version 1.0.4.

issue 14 (Autodetect and mask large light colored regions) reported by bsrini - The only issue with Nocturne is that some applications (such as Firefox) alternate light background content with dark background content. The dark content becomes a bright flash and can be very disturbing late at night. For example, if you close a full screen Terminal it will produce a bright flash. One way to get around this would be to detect and mask large regions that would be rendered as light colored. This would ensure that *all* windows and displays were dark at all times. I'm not a GUI programmer, but I assume that you have access to each frame before it's displayed on screen as well as each window. Pseudocode would then be something like this: for each rendered frame for each window in that frame determine if the window is majority light or dark (simple heuristic would work) if it is majority light, then render as dark using standard nocturne if it is majority dark, then it would be *rendered* as light using standard nocturne. Instead, *refrain* from inverting the colors in this region so that the normal dark display applies. This is a per-frame computation but would be pretty fast -- basically just summing up the fluorescence in each window before it's rendered. An more sophisticated algorithm would actually look at UI elements *within* each window -- for example, some web sites may have dark borders that become disturbingly light under Nocturne. What you could do then is segment the region into clusters of local fluorescence intensity and invert or leave uninverted as necessary. This segmentation would be tricky to get fast and right, but it would ensure that Nocturne *never* rendered a large bright flash.

The only issue with Nocturne is that some applications (such as Firefox) alternate light background content with dark background content. The dark content becomes a bright flash and can be very disturbing late at night. For example, if you close a full screen Terminal it will produce a bright flash. One way to get around this would be to detect and mask large regions that would be rendered as light colored. This would ensure that *all* windows and displays were dark at all times. I'm not a GUI programmer, but I assume that you have access to each frame before it's displayed on screen as well as each window. Pseudocode would then be something like this: for each rendered frame for each window in that frame determine if the window is majority light or dark (simple heuristic would work) if it is majority light, then render as dark using standard nocturne if it is majority dark, then it would be *rendered* as light using standard nocturne. Instead, *refrain* from inverting the colors in this region so that the normal dark display applies. This is a per-frame computation but would be pretty fast -- basically just summing up the fluorescence in each window before it's rendered. An more sophisticated algorithm would actually look at UI elements *within* each window -- for example, some web sites may have dark borders that become disturbingly light under Nocturne. What you could do then is segment the region into clusters of local fluorescence intensity and invert or leave uninverted as necessary. This segmentation would be tricky to get fast and right, but it would ensure that Nocturne *never* rendered a large bright flash.

Last 7 days

Last 30 days

Older