<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[&quot;Disable when using&quot; should have a change delay]]></title><description><![CDATA[<p dir="auto">"Disable when using" should have a delay when switch away momentarily from the application set for disable.</p>
<p dir="auto">For example, Photoshop. If set to disable, works great. But if you alt-tab to check on a file in Windows Explorer, f.lux starts changing temperature.  Alt-tab back to Photoshop, changes again.  That generates a headache for me rather quickly.</p>
<p dir="auto">So some of delay is desirable. Or instead of attempting to be "smart", simply trigger "disable for 1 hour" upon what f.lux thinks is an app exit/switch-away.</p>
]]></description><link>https://forum.justgetflux.com/topic/6237/disable-when-using-should-have-a-change-delay</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 07:55:32 GMT</lastBuildDate><atom:link href="https://forum.justgetflux.com/topic/6237.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 06 Mar 2018 06:56:08 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to &quot;Disable when using&quot; should have a change delay on Thu, 08 Mar 2018 00:33:59 GMT]]></title><description><![CDATA[<p dir="auto">We do have kind of a complicated state model that considers how long it's been disabled, but we can always do better.</p>
]]></description><link>https://forum.justgetflux.com/post/19206</link><guid isPermaLink="true">https://forum.justgetflux.com/post/19206</guid><dc:creator><![CDATA[herf]]></dc:creator><pubDate>Thu, 08 Mar 2018 00:33:59 GMT</pubDate></item></channel></rss>