<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/">
<channel>
<title>DisplayFusion RSS: two second delay before &quot;move window to next monitor&quot; appears</title>
<atom:link href="https://www.displayfusion.com/Discussions/RSS/?TopicID=4ea7d719-579a-410d-aa13-7531c3afaed9" rel="self" type="application/rss+xml" />
<link>https://www.displayfusion.com/Discussions/RSS/?TopicID=4ea7d719-579a-410d-aa13-7531c3afaed9</link>
<description>DisplayFusion RSS: two second delay before &quot;move window to next monitor&quot; appears</description>
<lastBuildDate>Tue, 16 Jun 2026 11:41:38 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.displayfusion.com/Discussions/RSS/?TopicID=4ea7d719-579a-410d-aa13-7531c3afaed9</generator>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#17</link>
<pubDate>Thu, 23 May 2019 14:04:04 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#17</guid>
<category>DisplayFusion</category>
<description><![CDATA[Ok, so update on this. We don't have any idea why adding a command line switch to the shortcut makes it faster. We don't have any hard coded exceptions to delay the adding of the titlebar buttons for those apps, DF just waits until Windows says the window is visible. Windows must be doing somethi...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Ok, so update on this. We don't have any idea why adding a command line switch to the shortcut makes it faster. We don't have any hard coded exceptions to delay the adding of the titlebar buttons for those apps, DF just waits until Windows says the window is visible. Windows must be doing something differently under the hood when there are command line parameters that's causing that to happen quicker.<br/>
<br/>
Please let us know if you have any further questions at all.<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#16</link>
<pubDate>Thu, 16 May 2019 19:36:06 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#16</guid>
<category>DisplayFusion</category>
<description><![CDATA[That's super weird! I have no idea why that works, but I will pass this over to our devs to see if they know.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
That's super weird! I have no idea why that works, but I will pass this over to our devs to see if they know.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#15</link>
<pubDate>Wed, 15 May 2019 16:00:06 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#15</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
Quote:
How about if you enable the "TitleBar Buttons: Don't Hide for Top-Tabs" option in the Advanced Settings?
Good call. After making that change and rebooting Firefox now has the button appearing immediately on program load.  Irfanview and Lotus 1-2-3 still do have the delay.
Thanks...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div><div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>How about if you enable the "TitleBar Buttons: Don't Hide for Top-Tabs" option in the Advanced Settings?</div></div><br/>
Good call. After making that change and rebooting Firefox now has the button appearing immediately on program load.  Irfanview and Lotus 1-2-3 still do have the delay.</div></div><br/>
Thanks for digging into this. I think I have fixed it but have no clue why so if you want to weigh in on why the below works I would be appreciative.<br/>
<br/>
Lotus 1-2-3 has the delay even without the compatibility rule in place. But based on your point that irfanview relies on DF polling since it briefly enters a not responding state upon startup, I tried doing a few things to see if I could get the two programs to load more quickly. Starting them with realtime priority did not make a difference. Then I came across the tweak of appending the shortcut program path and file name with the argument /prefetch:1. That eliminated the delay in lotus BUT also produced an error message of REFETCH:1 file does not exist. It was as though the shortcut was able to digest the /p, but not the refetch:1. So then I tried changing the shortcut to just c:\lotus\123\123w.exe /p. No idea what a /p does, but we're just trying whatever here. Lo and behold lotus then starts with the same instant speed, produces no error message, and the move window to next monitor button appears instantly. Then I changed the irfanview shortcut to also include a /p and it also now has no delay for the button to appear. No idea why this is working, but I will take it.<br/>
<br/>
The image below describes the above. The /p argument does not appear to do anything, other than eliminate the move window button delay!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#14</link>
<pubDate>Wed, 15 May 2019 15:47:41 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#14</guid>
<category>DisplayFusion</category>
<description><![CDATA[still working on this, thanks for the feedback]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
still working on this, thanks for the feedback
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#13</link>
<pubDate>Wed, 15 May 2019 14:32:10 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#13</guid>
<category>DisplayFusion</category>
<description><![CDATA[For Lotus, it looks likes you've got a Compatibility rule for it that disables the hooks. That would likely cause the issue here as DF has to then rely on polling to know when to add the buttons.
For IrfanView, there's not likely anything we can do there. The debug log you sent shows that IrfanV...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
For Lotus, it looks likes you've got a Compatibility rule for it that disables the hooks. That would likely cause the issue here as DF has to then rely on polling to know when to add the buttons.<br/>
<br/>
For IrfanView, there's not likely anything we can do there. The debug log you sent shows that IrfanView is reporting as "Not Responding" while it's starting up, which makes DisplayFusion wait to add the buttons.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#12</link>
<pubDate>Tue, 14 May 2019 19:12:15 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#12</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
How about if you enable the "TitleBar Buttons: Don't Hide for Top-Tabs" option in the Advanced Settings?
Good call. After making that change and rebooting Firefox now has the button appearing immediately on program load.  Irfanview and Lotus 1-2-3 still do have the delay.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>How about if you enable the "TitleBar Buttons: Don't Hide for Top-Tabs" option in the Advanced Settings?</div></div><br/>
Good call. After making that change and rebooting Firefox now has the button appearing immediately on program load.  Irfanview and Lotus 1-2-3 still do have the delay.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#11</link>
<pubDate>Tue, 14 May 2019 18:57:17 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#11</guid>
<category>DisplayFusion</category>
<description><![CDATA[How about if you enable the "TitleBar Buttons: Don't Hide for Top-Tabs" option in the Advanced Settings?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
How about if you enable the "TitleBar Buttons: Don't Hide for Top-Tabs" option in the Advanced Settings?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#10</link>
<pubDate>Mon, 13 May 2019 20:34:14 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#10</guid>
<category>DisplayFusion</category>
<description><![CDATA[delay also still there with beta 3]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
delay also still there with beta 3
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#9</link>
<pubDate>Mon, 13 May 2019 18:02:56 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#9</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
In the Settings &gt; Advanced Settings window, if you enable the "Disable Hung Window Detection" option, does that make any difference at all for either Firefox or Irfanview?
Thanks for the idea.  I tried it, rebooted, but the delay is still there.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>In the Settings &gt; Advanced Settings window, if you enable the "Disable Hung Window Detection" option, does that make any difference at all for either Firefox or Irfanview?</div></div>Thanks for the idea.  I tried it, rebooted, but the delay is still there.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#8</link>
<pubDate>Mon, 13 May 2019 17:39:12 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#8</guid>
<category>DisplayFusion</category>
<description><![CDATA[In the Settings  Advanced Settings window, if you enable the "Disable Hung Window Detection" option, does that make any difference at all for either Firefox or Irfanview?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
In the Settings > Advanced Settings window, if you enable the "Disable Hung Window Detection" option, does that make any difference at all for either Firefox or Irfanview?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#7</link>
<pubDate>Fri, 10 May 2019 19:14:53 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#7</guid>
<category>DisplayFusion</category>
<description><![CDATA[Quote:
Could you send me a debug log for this?
On the DisplayFusion Settings &gt; Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Try opening Firefox and IrfanView
Click the "Export Info to File" button on the Settings &gt; Troubleshooting tab
Reply wit...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
<div class="BackGrey"><div class="Text"><div><b>Quote:</b></div>Could you send me a debug log for this?<br/>
<br/>
<ul class="ListBullet">
<li>On the DisplayFusion Settings &gt; Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply</li>
<li>Try opening Firefox and IrfanView</li>
<li>Click the "Export Info to File" button on the Settings &gt; Troubleshooting tab</li>
<li>Reply with the file attached</li>
<li>Disable debug logging after sending the log</li></ul></div></div><br/>
log attached.  By the way the delayed appearance of "move window to next monitor" also occurs when I load the DF settings window itself.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#6</link>
<pubDate>Fri, 10 May 2019 18:57:34 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#6</guid>
<category>DisplayFusion</category>
<description><![CDATA[Could you send me a debug log for this?
On the DisplayFusion Settings  Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Try opening Firefox and IrfanView
Click the "Export Info to File" button on the Settings  Troubleshooting tab
Reply with the file attac...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Could you send me a debug log for this?<br/>
<br/>
<ul class="ListBullet">
<li>On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply</li>
<li>Try opening Firefox and IrfanView</li>
<li>Click the "Export Info to File" button on the Settings > Troubleshooting tab</li>
<li>Reply with the file attached</li>
<li>Disable debug logging after sending the log</li></ul>
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#5</link>
<pubDate>Fri, 03 May 2019 19:04:02 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#5</guid>
<category>DisplayFusion</category>
<description><![CDATA[Just did a test of the delay and got this:
Two second delay
-----------------
lotus 1-2-3
firefox
irfanview
Zero delay (move window to next monitor button appears at the same time as the rest of the titlebar)
-------------
chrome
notepad
explorer
internet explorer
ccleaner
mspaint
m...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Just did a test of the delay and got this:<br/>
Two second delay<br/>
-----------------<br/>
lotus 1-2-3<br/>
firefox<br/>
irfanview<br/>
<br/>
Zero delay (move window to next monitor button appears at the same time as the rest of the titlebar)<br/>
-------------<br/>
chrome<br/>
notepad<br/>
explorer<br/>
internet explorer<br/>
ccleaner<br/>
mspaint<br/>
microsoft excel<br/>
ultraiso<br/>
<br/>
btw - On my system all of these programs load pretty much instantaneously, maybe .1 or .2 seconds<br/>
<br/>
Then I was curious about what made the top three programs unique so I ran a few scenarios using just irfanview.  Here is what i found<br/>
<br/>
1) If I load irfanview by going into my start menu and navigating to the shortcut and INSTEAD of hitting left click like I normally would, but instead selected "right click-open" (I made a screenshot of it below to show what I mean), the program load instantly AND the "move window to next monitor button" ALSO loads instantly.  Further, going to the actual program file using explorer and clicking on the exe file directly (whether with a left double click OR a right-click-open) ALSO loads both the program and the move window button instantly.<br/>
<br/>
2) But if I load irfanview that way I normally do, by navigating to its shortcut within the start menu and hitting left click, THEN the program loads instantly BUT the move window button appears two seconds later.<br/>
<br/>
So then I wondered if maybe this had something to do with irfanview's need to load its ini file or its plugins, so I deleted both and re-ran items 1 and 2 above, and the result were the same as before.<br/>
<br/>
Edit: One more data point.  Disabling my AVG antivirus also had no impact on the results<br/>
<br/>
Edit #2: Everything within 1) & 2) above also applies to lotus 1-2-3.  It also applies to firefox IF I use a blank page as my home page.  But if I use an internet page as the home page (mine is www.google.com), the move window button appears only after a delay no matter whether I start it from a menu shortcut or even using right-click-open on the exe file. It appears the menu button waits for the page to load no matter what.  And yet on chrome and IE, the move window button appears instantaneously, prior to the home page loading, no matter what method I use to start the program.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#4</link>
<pubDate>Fri, 03 May 2019 18:39:46 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#4</guid>
<category>DisplayFusion</category>
<description><![CDATA[Thanks! Are they slow to appear on all applications, or only certain ones?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Thanks! Are they slow to appear on all applications, or only certain ones?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#3</link>
<pubDate>Fri, 03 May 2019 18:33:59 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#3</guid>
<category>DisplayFusion</category>
<description><![CDATA[here you go]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
here you go
</div>
]]></content:encoded>
</item>
<item>
<title>RE: two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#2</link>
<pubDate>Fri, 03 May 2019 18:27:24 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9#2</guid>
<category>DisplayFusion</category>
<description><![CDATA[Normally it shouldn't take that long, no. Could you attach a copy of your troubleshooting info?
Open the Settings  Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Normally it shouldn't take that long, no. Could you attach a copy of your troubleshooting info?<br/>
<br/>
<ul class="ListBullet">
<li>Open the Settings > Troubleshooting tab</li>
<li>Click the "Export Info to File" button</li>
<li>Reply with the file attached</li></ul>
</div>
]]></content:encoded>
</item>
<item>
<title>two second delay before &quot;move window to next monitor&quot; appears</title>
<link>https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9</link>
<pubDate>Thu, 02 May 2019 00:36:28 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/two-second-delay-before-move-window-to-next-monitor-appears/?ID=4ea7d719-579a-410d-aa13-7531c3afaed9</guid>
<category>DisplayFusion</category>
<description><![CDATA[Opening a program on my system takes maybe 0.2 seconds. But then it takes about two more seconds for the "move window to next monitor" button to appear on the titlebar.  Is that delay normal?  Any way to speed it up? Thanks.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Opening a program on my system takes maybe 0.2 seconds. But then it takes about two more seconds for the "move window to next monitor" button to appear on the titlebar.  Is that delay normal?  Any way to speed it up? Thanks.
</div>
]]></content:encoded>
</item>
</channel>
</rss>