https://www.displayfusion.com/Discussions/RSS/?TopicID=d6696d4e-a30e-4080-a818-dde40190939e DisplayFusion RSS: Titlebar button compatibility Tue, 07 Apr 2026 12:13:27 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=d6696d4e-a30e-4080-a818-dde40190939e https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#25 Tue, 08 Oct 2013 18:42:33 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#25 DisplayFusion Yep, it should! Those are the properties DisplayFusion uses to determine whether TitleBar Buttons should be added. ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#24 Tue, 08 Oct 2013 15:16:29 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#24 DisplayFusion 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? ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#23 Mon, 07 Oct 2013 19:29:10 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#23 DisplayFusion Unfortunately not

We looked at all of the properties and details for those drop-down boxes that you sent us, and they are all identical to the main Sage 200 window.

However, I just had an idea. The width of the drop-down boxes would be significantly smaller than the main window. Could you try setting the TitleBar Buttons > Minimum Window Width option in the Advanced Settings to something like 500, to see if that helps? ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#22 Mon, 07 Oct 2013 08:29:42 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#22 DisplayFusion 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? ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#21 Thu, 26 Sep 2013 18:33:51 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#21 DisplayFusion 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! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#20 Fri, 03 May 2013 19:17:48 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#20 DisplayFusion Thanks Chris, I can see the line for Sage 200, so hopefully this will have the information we need. I'll keep you posted ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#19 Fri, 03 May 2013 08:46:58 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#19 DisplayFusion Ok, The log entries that are time-stamped 9:42x.xxx are the ones that relate to the combo box being opened and closed twice. ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#18 Thu, 02 May 2013 20:22:42 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#18 DisplayFusion 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! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#17 Thu, 02 May 2013 15:49:44 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#17 DisplayFusion 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". ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#16 Thu, 02 May 2013 14:13:17 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#16 DisplayFusion 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! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#15 Wed, 01 May 2013 20:14:27 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#15 DisplayFusion Thanks Chris! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#14 Wed, 01 May 2013 09:42:25 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#14 DisplayFusion Hi Keith

Here is a new log file with 5.0.1 running. ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#13 Fri, 19 Apr 2013 14:00:37 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#13 DisplayFusion Sorry for the long delay on this, we're still hoping to fix this up for 5.0.1 though. The previous log didn't contain enough info, so we've added more logging info for the TitleBar Buttons. Could you update to Beta 4 (http://www.displayfusion.com/Download/Beta/) and then perform the debug logging steps from post #10 again?

Thanks! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#12 Fri, 22 Feb 2013 20:03:38 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#12 DisplayFusion 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. ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#11 Wed, 20 Feb 2013 14:12:56 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#11 DisplayFusion 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! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#10 Wed, 20 Feb 2013 13:49:05 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#10 DisplayFusion Ah ok, that would be an issue then

Could you do the following instead?

• Enable debug logging on the Troubleshooting tab (set it to Logging: Important Only) and click Apply.
• Open and close the combo box a few times to make the TitleBar Buttons appear and disappear. Note the time so I'll know where to look in the log.
• Send me the %appdata%\DisplayFusion\DisplayFusion.log file (can be found by clicking the 'Open Log' button on the Troubleshooting tab).
• Disable debug logging after sending me the log.

From the log we should be able to get the info we need to exclude those Sage 200 combo boxes from getting TitleBar Buttons.

Thanks! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#9 Mon, 18 Feb 2013 09:41:48 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#9 DisplayFusion 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. ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#8 Fri, 15 Feb 2013 20:51:07 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#8 DisplayFusion 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! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#7 Thu, 14 Feb 2013 11:32:33 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#7 DisplayFusion 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? ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#6 Wed, 13 Feb 2013 16:44:17 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#6 DisplayFusion Sorry, I should have been more clear in my previous post

We didn't add the ability to create Compatibility rules based on Window Class, but the issue of the TitleBar Buttons showing up on the IntelliSense popup should be fixed. Is it not? ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#5 Tue, 12 Feb 2013 09:22:27 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#5 DisplayFusion 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 ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#4 Tue, 05 Feb 2013 15:42:41 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#4 DisplayFusion No problem Chris! The final version of 5.0 should be available in the coming weeks as well ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#3 Tue, 05 Feb 2013 15:35:57 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#3 DisplayFusion Thank you Keith for this. Unfortunately, I cannot apply a beta version to my development environment. Not that your software is buggy but I cannot take a risk on a live dev box.
If I get a chance, I will create a another test vm and put 5.0 beta on that and give it a whirl.
Many thanks. ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#2 Tue, 05 Feb 2013 15:22:07 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e#2 DisplayFusion I believe we've actually fixed this up in the recent DisplayFusion 5.0 Beta versions. Could you give the latest one a try from the link below?

http://www.displayfusion.com/Download/Beta/

Thanks! ]]> https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e Tue, 05 Feb 2013 13:57:37 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/titlebar-button-compatibility/?ID=d6696d4e-a30e-4080-a818-dde40190939e DisplayFusion 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? ]]>