I cannot view or edit dock properties except under the 'Content' tab. When I hover or click on any other tab (ie, Position, Behavior, Appearance, Effects, Themes) nothing happens.

So, I can view and make modifications only under the 'Content' tab but none of the other tabs.

I'm running Nexus Ultimate v12.02.1005 on Win7 SP1.

Is there a fix for this problem? Thx, Rob

did you change your windows dpi settings? if so change them back to default.

Thanks. Yes, that did work. However, it's lame that a user using a non-default DPI is required to do that to customize the product for his/her needs. What a PITA.

Microsoft says "Third-party Windows applications can leverage High DPI settings and adjust the user interface accordingly, by declaring themselves High DPI aware. Application developers should no longer assume that 96 dpi is the ideal resolution for all applications."

http://msdn.microsoft.com/en-us/library/windows/desktop/dd940516%28v=vs.85%29.aspx

All due respect, Microsoft should first fix their own broken DPI approach and algorithms and then lecture others on how to do it.
As far as I'm concerned, normal 100% "magnification" is the only way to have a properly rendered GUI. Change that and things start going nuts all over, *including* the OS itself.

you do know one of the reasons for the setting being able to be adjusted is so people with eyesight problems DON'T always have to use the magnifier. you guys like to blame winstep shortcomings on anything and everything else.

Whatever. All I know is with my poor and failing eyesight, I have no choice but use a high DPI setting (134%) on my Win7 system. Without high DPI I may as well forget about using my PC. I'm sure I'm not the only user in this situation.

chucky: I don't really care what you think "we guys" do or don't do or should do. The cold hard FACT is that Microsoft's approach is broken. Another fact is that they only added it on top of the Windows renderer (many years ago), so that they could use the same code on other devices, like TV sets and touch-enabled monitors of the time.
And it's broken. Windows are ugly and there are discrepancies everywhere, bitmaps don't quite match and wherever there are both bitmaps and rendered text... it's like Hiroshima.
Obviously, I too would like to see Winstep fixed. But that is something entirely different from what I said.

unbob: Personally, I'd invest on a larger monitor. Small-ish TV sets (20-25") make for excellent monitors, due to their large pixel size, and you won't strain your eyes nor will you have to adjust the DPI of Windows to more than 100% and suffer the consequences, not only to Winstep, but everywhere... even Windows themselves don't render properly!
As I said previously, though, that doesn't mean that Winstep shouldn't be fixed.

as i said one of the reasons for higher dpi settings is because of people with eyesight problems, meaning ALL program creators should be making sure that their programs work properly with the higher dpi settings. not doing so is like not making sure your program works with different screen resolutions. next time ASK how big the OP's monitor is, don't assume it's a small one. if unbob wants to, or needs to use the higher dpi settings THAT is his choice. i'm willing to be winsteps biggest competitor stardock does not have this problem under the higher dpi settings.

Chucky, as usual you talk about things you know nothing about. Microsoft's approach *IS* broken.

Windows uses two different high-DPI solutions (the one they call 'XP compatible' and DPI virtualization), and BOTH are broken/buggy.

I've spent a lot of time trying to work around the high DPI bugs and making Winstep applications high-DPI compatible, but I can't solve Microsoft's own bugs/inconsistencies.

If an application uses *ONLY* common controls (i.e.; buttons, UI tabs, etc...) and is run-of-the-mill then Microsoft's solution *usually* works. The problem is when you are dealing with highly graphical applications such as Winstep programs (and many others, this is Windows after all) that push the boundaries of what is possible.

For instance, with DPI virtualization Windows will lie to the application regarding the current DPI setting so that, in theory, the application doesn't need to do anything. Problem is, Microsoft 'forgot' to provide a function that reveals the true DPI setting, which in itself will cause a lot of problems because some of the API functions respect DPI virtualization and others DO NOT.

Worse, since Microsoft's implementation is buggy, sometimes and under certain circumstances, it will de-virtualize the application while, at the same time, maintaining visual aspect. This makes it impossible to fix and results in stuff like what you are seeing, simply because Windows is passing wrong mouse coordinates to the application itself.

My advice to the user is to play with the DPI settings, i.e.; use standard DPI values or switch the 'XP compatible' setting.

Most non-standard applications (and even many standard apps) have problems when run in a high-DPI environment.

jorge as usual you are the one in the wrong. it's not an issue if it is or isn't broken, it isn't an issue if microsour did it the way they did it to save having to update code. the issue is most programs DO work just fine with the user increasing the dpi settings. it IS the users choice on what to have his/her dpi settings at. it is not skagon or you place to tell someone to just get larger monitor.

I explained why Microsoft's approach is buggy and what the problems are, with hands-on knowledge. If you still think you know better, nothing I say will convince you otherwise.

Just to chime in and for the record...
Windows' DPI setting is NOT meant for people with eyesight problems. In fact, it is there for... guess what... !!! monitors with greater pixel density !!!
For people with eyesight problems, Microsoft has the magnifier and other "accessibility tools" and also "themes" with bigger fonts!
The DPI (Dots Per Inch) setting was put there, as smaller LCD panels started being manufactured, with densities far more than the usual for normal monitors (which, again, varies).
Some people actually *needed* length accuracy with their display -- that's why the DPI dialogue is giving you an inch or a centimetre "measure".
Others just had to make the GUI elements bigger, so that use on a small touch-enabled mobile device were possible.

All that is actually documented from Microsoft itself.

i never said their approch wasn't flawed. i more or less said the op isn't going to care about that. skagon regardless of what microsour has documented most people that change their dpi settings do so to see what's on their screen better.