3.3.0 no longer respects HKCU\...\MinWidth?

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

porcupine_advocate

8 discussion posts

Hi,

I have Window's native taskbar buttons set to as wide as possible, via HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics\MinWidth

DisplayFusion Pro 3.2.0 would use the value stored there to set its own button width (http://www.binaryfortress.com/Forum/index.php?topic=1508.0). I've just updated to 3.3.0 and button width is now 160 again. Is this a regression or some bug on my system?

Feb 18, 2011 • #1

Are you using the DF taskbar button grouping, and which version of Windows are you using?

Feb 28, 2011 • #2

porcupine_advocate

8 discussion posts

Windows 7 x64 SP1

I'm not sure what you mean by DF's taskbar button grouping. Taskbar buttons are set to show icons and text. When I check the troubleshooting tab, it has this:

Quote:

Code
Copy
Select All

***** Taskbars *****************************************
Enabled: True
Taskbar Mode: ShowRelevant
Middle-Click Behaviour: OpenNewInstance
Button Style: IconsAndText
Opacity: 100
Flash Blink: False
Thumbnail Preview: Win7Style
Thumbnail Preview Animations: True
Sizing Bar Size: 0
Button Width Max: 160
Button Width Override: 0
Button Icon Size: 16
Button Gap Size: {Width=2, Height=0}
Clock Time Format (use/default): hh:mm tt / hh:mm:ss tt
Start Menu Handle: 0x00120166 ~ "DV2ControlHost" ~ {X=0,Y=238,Width=491,Height=632}
Windows Taskbar Side: Bottom
Windows Taskbar Size: {Width=1600, Height=30}
Windows Taskbar Bounds: {X=0,Y=870,Width=1600,Height=30}
Windows Taskbar Monitor Bounds: {X=0,Y=0,Width=1600,Height=900}
Disabled Taskbars: None
Colour Tracking Override: None
Button Height: 30
Text Glow Size: 0
Count: 1

***** Taskbar 1 ****************************************
Location: {X=1600,Y=870,Width=1366,Height=30}
Monitor ID: 1
Position (Setting/Current): Automatic / Bottom
Size: Automatic
Auto-Hide: Disabled
Button Grouping: False
TopMost: True
Buttons (7):
[...]

So... Button Grouping: False.

Feb 28, 2011 • #3

Good news, I found the issue and it has been fixed for the upcoming Beta 1.

Just enable the auto-updates for Betas and you'll get a notification when it's released.

Feb 28, 2011 • #4

porcupine_advocate

8 discussion posts

Thanks!

Will update again once the beta is out.

Mar 1, 2011 • #5

porcupine_advocate

8 discussion posts

Updated. It works great now!

But there's an error when installing; it prompts that it can't find the previous language (English United States); apparently it is now just "English" (Canadian flag)? I'm in the UK at the moment so the beta updater may be downloading the wrong language. No idea if this is expected behavior.

Attempting to change languages back to English (United States) gives this error:

Language file missing keys:
- frmErrorMessage_btnCopy
- frmErrorMessage_btnMoreInformation
- frmSettingsCompatibility_lblTitleBarButtonOffsetMax
- frmWallpaper_lblInfoType
- frmWallpaper_lblNoteImageInfo
- frmWallpaper_pageInfo
- frmWallpaper_rdoInfoBottomLeft
- frmWallpaper_rdoInfoBottomMiddle
- frmWallpaper_rdoInfoBottomRight
- frmWallpaper_rdoInfoTopLeft
- frmWallpaper_rdoInfoTopMiddle
- frmWallpaper_rdoInfoTopRight
- frmWallpaper_InfoType_Filename
- frmWallpaper_InfoType_FilenameAndPath
- frmWallpaper_InfoType_None
- frmWallpaper_InfoType_Title
- frmWallpaper_InfoType_TitleAndFilename
- frmWallpaper_InfoType_TitleAndFilenameWithPath
- Words_NeedProLong

the version number on all the other languages is 3.3.0.0; the version number on English (Canada) is 3.3.0.101, so I'm guessing it is probably just missing strings for the beta. The error message when updating was unexpected, though.

Mar 1, 2011 • #6

Sorry, the language thing was an issue with Beta 1 that is fixed for Beta 2.

Mar 14, 2011 • #7