<?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: Trigger rule not applied correctly with mixed-DPI</title>
<atom:link href="https://www.displayfusion.com/Discussions/RSS/?TopicID=1fb185e5-1728-4eb0-9078-700016947675" rel="self" type="application/rss+xml" />
<link>https://www.displayfusion.com/Discussions/RSS/?TopicID=1fb185e5-1728-4eb0-9078-700016947675</link>
<description>DisplayFusion RSS: Trigger rule not applied correctly with mixed-DPI</description>
<lastBuildDate>Sat, 20 Jun 2026 05:53:26 GMT</lastBuildDate>
<language>en</language>
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<generator>https://www.displayfusion.com/Discussions/RSS/?TopicID=1fb185e5-1728-4eb0-9078-700016947675</generator>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#20</link>
<pubDate>Wed, 17 Jun 2020 22:38:05 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#20</guid>
<category>DisplayFusion</category>
<description><![CDATA[Excellent, glad to hear it!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Excellent, glad to hear it!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#19</link>
<pubDate>Wed, 17 Jun 2020 11:37:17 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#19</guid>
<category>DisplayFusion</category>
<description><![CDATA[I've been running the new beta for 3 days now. No problems.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I've been running the new beta for 3 days now. No problems.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#18</link>
<pubDate>Fri, 12 Jun 2020 14:18:15 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#18</guid>
<category>DisplayFusion</category>
<description><![CDATA[We've just released a new DisplayFusion beta version and this issue should be all fixed up. Please let us know if you run into any trouble after updating.
Thanks!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
We've just released a new <a href="https://www.displayfusion.com/Download/Beta/" target="_blank" rel="nofollow"><b>DisplayFusion beta version</b></a> and this issue should be all fixed up. Please let us know if you run into any trouble after updating.<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#17</link>
<pubDate>Tue, 26 May 2020 21:52:05 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#17</guid>
<category>DisplayFusion</category>
<description><![CDATA[Good catch on it being an issue with fixed sized windows, I was able to reproduce this issue with the Snipping Tool here as well. I've added it to our list to fix up, so we should have it sorted out for the next beta
Thanks for your help in tracking this down!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Good catch on it being an issue with fixed sized windows, I was able to reproduce this issue with the Snipping Tool here as well. I've added it to our list to fix up, so we should have it sorted out for the next beta <img src="https://www.displayfusion.com/MediaCommon/SVGs/FontAwesome/face-smile.light.svg" alt=":)" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":)" /><br/>
<br/>
Thanks for your help in tracking this down!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#16</link>
<pubDate>Tue, 26 May 2020 10:50:53 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#16</guid>
<category>DisplayFusion</category>
<description><![CDATA[Here's the result of my tests:
The issue also appears with  "Move Window to Next Monitor".
It disappears when I install DF 9.6.1, but I need to reset the "size and position" values by dragging the cross hair symbol over the target window with correct size and location. Using the old values whic...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Here's the result of my tests:<br/>
The issue also appears with  "Move Window to Next Monitor".<br/>
It disappears when I install DF 9.6.1, but I need to reset the "size and position" values by dragging the cross hair symbol over the target window with correct size and location. Using the old values which were generated with the latest beta does lead to the same problem.<br/>
I have several programs where this issue does not appear. But these are all windows which are not fixed size. I.e. mostly MDF with the resize corner bottom right.<br/>
I tried to identify a program whih is fixed size and publicly available. I found the snipping tool which comes with Windows:<br/>
C:\Windows\System32\SnippingTool.exe<br/>
That's fixed size and shows the same issue.<br/>
Important: The issue appears only, if the window opens on a monitor with 100% scaling and then is moved by DF to the monitor with 125% scaling.<br/>
Snipping tool saves the position on closing, so close it while it's on a 100% monitor, then try the trigger.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#15</link>
<pubDate>Fri, 22 May 2020 15:28:21 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#15</guid>
<category>DisplayFusion</category>
<description><![CDATA[Ok, could you roll back to 9.6.1 temporarily to confirm that you don't have that issue with WinFlash?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Ok, could you roll back to 9.6.1 temporarily to confirm that you don't have that issue with WinFlash?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#14</link>
<pubDate>Fri, 22 May 2020 04:52:15 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#14</guid>
<category>DisplayFusion</category>
<description><![CDATA[It started with the recent betas. The monitor scaling exists since mid of last year.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
It started with the recent betas. The monitor scaling exists since mid of last year.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#13</link>
<pubDate>Thu, 21 May 2020 18:45:10 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#13</guid>
<category>DisplayFusion</category>
<description><![CDATA[Ok, did that issue with WinFlash start happening only with the recent betas? Or did it start happening after your monitor DPI changed to 125%?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Ok, did that issue with WinFlash start happening only with the recent betas? Or did it start happening after your monitor DPI changed to 125%?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#12</link>
<pubDate>Thu, 21 May 2020 15:57:53 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#12</guid>
<category>DisplayFusion</category>
<description><![CDATA[I'll try next week.]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I'll try next week.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#11</link>
<pubDate>Thu, 21 May 2020 15:39:17 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#11</guid>
<category>DisplayFusion</category>
<description><![CDATA[If you just use the "Move Window to Next Monitor" function on WinFlash or that other window, does it have the same issue?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
If you just use the "Move Window to Next Monitor" function on WinFlash or that other window, does it have the same issue?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#10</link>
<pubDate>Thu, 21 May 2020 07:45:10 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#10</guid>
<category>DisplayFusion</category>
<description><![CDATA[no, WinFlash is not the only one. I have another program (Company proprietary), which I have set to be moved to monitor 1, and it shows the same bevahior. That program changes window content and size with any action, and once it does that, it goes back to normal.
There migth be other programs wh...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
no, WinFlash is not the only one. I have another program (Company proprietary), which I have set to be moved to monitor 1, and it shows the same bevahior. That program changes window content and size with any action, and once it does that, it goes back to normal.<br/>
<br/>
There migth be other programs which I jsut havent used recently. I can check, but not before next Tuesday.
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#9</link>
<pubDate>Wed, 20 May 2020 22:45:25 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#9</guid>
<category>DisplayFusion</category>
<description><![CDATA[The differing values may be expected, because of the different scaling levels, but I'm checking with our developers on that.
As for the window being distorted, is the WinFlash window the only one that does that?]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
The differing values may be expected, because of the different scaling levels, but I'm checking with our developers on that.<br/>
<br/>
As for the window being distorted, is the WinFlash window the only one that does that?
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#8</link>
<pubDate>Tue, 19 May 2020 10:22:13 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#8</guid>
<category>DisplayFusion</category>
<description><![CDATA[Hello,
same topic, new problem. A different program is not shown correctly, when I open it.
Same setup:
Laptop and two external monitors, all set to 1920 x 1080. The external monitors have a scaling of 100%, the laptop screen of 125%.
Laptop is on the right side, monitor numbering is (from le...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hello,<br/>
<br/>
same topic, new problem. A different program is not shown correctly, when I open it.<br/>
<br/>
Same setup:<br/>
Laptop and two external monitors, all set to 1920 x 1080. The external monitors have a scaling of 100%, the laptop screen of 125%.<br/>
Laptop is on the right side, monitor numbering is (from left to right): 3 - 2 - 1.<br/>
Monitor 2 is primary screen.<br/>
<br/>
A program which opens up on monitor 2 should be moved to monitor 1, using 'Move Window to specific Size and Location'.<br/>
First fun fact:<br/>
When I use the 'Drag this over a window to use its size and location' feature, I get different size results on different monitors.<br/>
If the window is on monitor 2, the result is W=665, H=516.<br/>
If it's on monitor 1, the result is W=830, H=645.<br/>
<br/>
If I try to have it moved to monitor 1, it's cropped on right and bottom.<br/>
And this regardless of any size which I enter manually.<br/>
See attached pictures 'Is_665x516.jpg' and 'Is_830x645.jpg' which use different size settings.<br/>
'Should.JPG' shows the original window, before it moves. I had that trigger active for a long time, it worked with the last stable release, but it seems not to work with beta 11.<br/>
<br/>
I also attached a log. Relevant entry:<br/>
2020/05/19 12:02:43.5823##_##INFO:L1 [...] Path: "[...]\KEFEX Winflash...<br/>
<br/>
CU,<br/>
Christian
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#7</link>
<pubDate>Fri, 08 May 2020 21:55:27 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#7</guid>
<category>DisplayFusion</category>
<description><![CDATA[Excellent, glad to hear it!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Excellent, glad to hear it!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#6</link>
<pubDate>Fri, 08 May 2020 08:51:42 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#6</guid>
<category>DisplayFusion</category>
<description><![CDATA[Hi Keith,
it seems to work now. Thanks!
Christian]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hi Keith,<br/>
<br/>
it seems to work now. Thanks!<br/>
<br/>
Christian
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#5</link>
<pubDate>Fri, 08 May 2020 01:38:08 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#5</guid>
<category>DisplayFusion</category>
<description><![CDATA[Ok, we've just posted 9.7 Beta 11, could you give it a try and let me know how it works out?
Thanks!]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Ok, we've just posted 9.7 Beta 11, could you give it a try and let me know how it works out?<br/>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#4</link>
<pubDate>Wed, 22 Apr 2020 20:41:20 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#4</guid>
<category>DisplayFusion</category>
<description><![CDATA[Thanks! I was able to reproduce this issue here as well. We're making some changes for 9.7 Beta 11 that might help here, so I'll re-test when that's ready and we'll go from there]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Thanks! I was able to reproduce this issue here as well. We're making some changes for 9.7 Beta 11 that might help here, so I'll re-test when that's ready and we'll go from there <img src="https://www.displayfusion.com/MediaCommon/SVGs/FontAwesome/face-smile.light.svg" alt=":)" style="box-sizing:border-box;position:relative;overflow:hidden;vertical-align:middle !important;width:16px;height:16px;" HelpButtonData=":)" />
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#3</link>
<pubDate>Tue, 21 Apr 2020 14:52:20 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#3</guid>
<category>DisplayFusion</category>
<description><![CDATA[Hello Keith,
the problem persists with the current beta version. Attached the log file.
I checked the data, the trigger is started at:
2020/04/21 16:40:21.5206
Window Text: '"TRACE32 PowerView"'
Thanks for your help,
Christian]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hello Keith,<br/>
<br/>
the problem persists with the current beta version. Attached the log file.<br/>
I checked the data, the trigger is started at:<br/>
2020/04/21 16:40:21.5206<br/>
Window Text: '"TRACE32 PowerView"'<br/>
<br/>
Thanks for your help,<br/>
Christian
</div>
]]></content:encoded>
</item>
<item>
<title>RE: Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#2</link>
<pubDate>Mon, 20 Apr 2020 16:48:33 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675#2</guid>
<category>DisplayFusion</category>
<description><![CDATA[I've moved this to a separate topic, as his issue was with the Window Position Profiles, and I believe your issue has a different root cause.
Could you try the latest beta and if it's still broken, send me a debug log?
On the DisplayFusion Settings  Troubleshooting tab, change the Logging drop-...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
I've moved this to a separate topic, as his issue was with the Window Position Profiles, and I believe your issue has a different root cause.<br/>
<br/>
Could you try the <a href="https://www.displayfusion.com/Download/Beta/" target="_blank" rel="nofollow"><b>latest beta</b></a> and if it's still broken, send me a debug log?<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>Reproduce the issue and note the time so we'll know where to check in the log file</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>
<br/>
Thanks!
</div>
]]></content:encoded>
</item>
<item>
<title>Trigger rule not applied correctly with mixed-DPI</title>
<link>https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675</link>
<pubDate>Mon, 20 Apr 2020 15:09:27 GMT</pubDate>
<dc:creator>Binary Fortress Software</dc:creator>
<guid isPermaLink="false">https://www.displayfusion.com/Discussions/View/trigger-rule-not-applied-correctly-with-mixed-dpi/?ID=1fb185e5-1728-4eb0-9078-700016947675</guid>
<category>DisplayFusion</category>
<description><![CDATA[Hello,
I have a similar problem as described by fpdragon.
My setup:
Laptop and two external monitors, all set to 1920 x 1080. The external monitors have a scaling of 100%, the laptop screen of 125%.
Laptop is on the right side, monitor numbering is (from left to right): 3 - 2 - 1.
Monitor 2 ...]]></description>
<content:encoded><![CDATA[<div class="CTDiscussions">
Hello,<br/>
<br/>
I have a similar problem as described by fpdragon.<br/>
<br/>
My setup:<br/>
Laptop and two external monitors, all set to 1920 x 1080. The external monitors have a scaling of 100%, the laptop screen of 125%.<br/>
Laptop is on the right side, monitor numbering is (from left to right): 3 - 2 - 1.<br/>
Monitor 2 is primary screen.<br/>
<br/>
I have a custom trigger which waits for a window to be created and then moves this window to size and location:<br/>
Left: -861<br/>
Top: 11<br/>
Width: 4689<br/>
Height: 1028<br/>
<br/>
This should span the window across all three screens and it works, if the laptop screen is set to a scaling of 100%. But if it is set to 125%, the window's right edge ends up at the right edge of monitor 2. And the left edge is far outside of the left edge of monitor 3.<br/>
<br/>
As per your suggestion to fpdragon I tried to call the action "move to size and location" a second time, but it doesn't work either.<br/>
<br/>
You wrote that you may have actually fixed this. Is it already implemeted in the current beta?<br/>
<br/>
Best regards,<br/>
Christian
</div>
]]></content:encoded>
</item>
</channel>
</rss>