Chris Gorringe
35 discussion posts
If you use DisplayFusion with something like SQL Management Studio for example and you have child windows that popup for intellisense (RedGate SQL Prompt), these windows get the DisplayFusion buttons added to them even though they do not have a title bar as such. This then causes information to be obscured. These windows have the same application name as SSMS so I do not want to turn off DisplayFusion for the whole of SSMS. These windows do have their own Class string so would it be possible to filter the compatibility settings by Application, Window and Class?
Chris Gorringe
35 discussion posts
Hi Keith
I have now installed the release version of DF 5.0 but I cannot easily see how to filter windows by their class name. Could you point me in the right direction.
Thanks
Chris Gorringe
35 discussion posts
It does appear to be corrected in SSMS with intellisense but it is not correct in other applications that use pop-up type windows. Sage 200 uses combo style lookups that are seen by DF as windows but they aren't. Either DF has to "know" about all the possible apps out there or it needs a way of being configurable so any app can be configured correctly. I suggest the latter.
The Auto-It program for example provides a useful tool to identify the window details etc. Why don't you use a similar tool and have an intelligent "browse" button that allows you to choose an active window rather than an executable, or both?
We'll definitely look into that for 5.1. In the meantime, would you be able to grab the window info for that window as per the attached instructions?
Thanks!
Chris Gorringe
35 discussion posts
One slight problem. In order to run the Window Detective, you have to click on the app to drag the cross hairs over the target window. This means that the window that has popped up in the Sage application, loses focus and immediately closes because it is a combo box type control. I cannot seem to get around this.
What I need is to be able to launch the windows properties box of the Windows Detective program from a title bar button. That way, the window stays open and the window being discovered is the one that launched the properties window.
Chris Gorringe
35 discussion posts
Hi Keith
I set everything up and then cleared the log, enabled logging, performed the popup on the window a couple of times and turned off the loggin so you only have the details relating to the popup window.
Enjoy!
• Attachment [protected]: DisplayFusion.log [29,214 bytes]
Perfect, thanks Chris! We'll check out the log and see what we can do. I'll post an update as soon as we have one.
Chris Gorringe
35 discussion posts
Hi Keith
Here is a new log file with 5.0.1 running.
• Attachment [protected]: DisplayFusion.log [37,559 bytes]
This log doesn't show any lines for TitleBar Buttons being added to the Sage 2000 combo boxes. Could you try logging again and open/close the Sage 2000 combo boxes a few times, confirming that the TitleBar Buttons are being added/removed from them?
Thanks!
Chris Gorringe
35 discussion posts
Hi Keith
I have done the test again but I have also included the "combo" that I am opening and closing. You will notice that the Code "combo" has the form functions obscuring the column heading "Quantity".
• Attachment [protected]: Capture.JPG [77,529 bytes]
• Attachment [protected]: DisplayFusion.log [16,674 bytes]
Sorry Chris, the log only shows about 1 second worth of data, just looks like the lines that get written when the settings are saved. Could you try restarting DisplayFusion after enabling the logging, then do the test again where you open/close the combo box a few times?
Thanks!
Chris Gorringe
35 discussion posts
Ok, The log entries that are time-stamped 9:42
x.xxx are the ones that relate to the combo box being opened and closed twice.
• Attachment [protected]: DisplayFusion.log [66,479 bytes]
Sorry for the long delay again, but I'm going to be the bearer of bad news today. The combo boxes in Sage 200 have a generic window class, so we can't exclude the TitleBar Buttons based on the class. Also, the reason they get TitleBar Buttons in the first place, is because they have the WS_MAXIMIZEBOX and WS_MINIMIZEBOX window properties set on them (even though they clearly don't have caption or maximize buttons).
So, unfortunately there's nothing we can do from our end. The only workaround would be to add a Compatibility rule for Sage 200 to remove the TitleBar Buttons, but that will affect all Sage 200 windows.
Sorry!
Chris Gorringe
35 discussion posts
Hi Keith
Is it not possible to improve the compatibility rules capabilities so that an exclusion can be made without removing DisplayFusion from the whole Sage 200 application?
Chris Gorringe
35 discussion posts
The min window width would be a good idea except that some of the "lookups" on some forms are wider than the whole width of other forms so I have difficulty finding a size that would be workable.
I may me able to customise Sage 200 so that the lookups do not have the WS_MAXIMIZEBOX and WS_MINIMIZEBOX properties. If I could achieve this on a global basis, would this prevent the TitleButtons from showing?
Yep, it should! Those are the properties DisplayFusion uses to determine whether TitleBar Buttons should be added.
