This project is read-only.

Browse For Folder Font/Info Bug


FYI, Just noticed something popping up again that I thought had resolved itself in the latest issue - it's been there since before .8

When the [Source:] button is pressed, and [DVD/Blue Ray Folder] is selected, the Dialog Box that appears (a Windows default box?) has jibberish in the area above the folder selection list. Is this intended information from the code that is being passed to the dialog routine that is being corrupted?

Mostly boxes appear, but also non-standard font characters appear. XP artifact not in WV/7?
[see screenshot enclosed]

PS - Loving the multiselect and additional menus in the completed list window!

When I think of it, VidCoder is the only program besides TSR's and Outlook I've usually got running 24/7 these's always busy doing something I've got queued. Ever thought of making it Status Bar available instead of just Task Bar?

Windows XP SP3
3.2 Ghz Intel Pentium 4 HT

file attachments


RandomEngy wrote Aug 5, 2011 at 8:50 PM

Interesting. I'm using a 3rd party dialog ( ) to choose folders. On Vista and 7 it gets you the new awesome dialog that's not available through standard means in C#/WPF. I've never tested it on XP. Anyway I may just let this bug go. It's cosmetic and affects only an old version of Windows. Should fade away as people upgrade. :)

deltaecho5 wrote Aug 5, 2011 at 8:54 PM

LOL...I will let go of XP when they pry it from my cold dead fingers! LOL Not sure why, just hate Vista and V7 GUI is a pain to use. I'm an old reject from DOS 2.11 days, do the AOL style of computing has never appealed to me!

Something seems to be corrupted when passed from code. What is supposed to be there? Or is typically blank and extraneous tidbits are leaking in?

deltaecho5 wrote Aug 5, 2011 at 9:01 PM's in the handler for .NET 3.5.

"The Ookii.Dialogs.VistaOpenFileDialog, Ookii.Dialogs.VistaSaveFileDialog and Ookii.Dialogs.VistaFolderBrowserDialog provide these dialogs for Windows Forms (note that in the case of the OpenFileDialog and SaveFileDialog it is recommended to use the built-in .Net classes unless you hit one of the scenarios where those classes use the old dialogs). The Ookii.Dialogs.Wpf.VistaOpenFileDialog, Ookii.Dialogs.Wpf.VistaSaveFileDialog and Ookii.Dialogs.Wpf.VistaFolderBrowserDialog classes provide the same functionality for WPF.

The classes have been designed to resemble the original Windows Forms and WPF classes to make it easy to switch. When the classes are used on Windows XP, they will automatically fall back to the old style dialog; this is also true for the VistaFolderBrowserDialog on WPF; that class provides a complete implementation of a folder browser dialog for WPF, old as well as new style. "

RandomEngy wrote Aug 5, 2011 at 9:42 PM

I could not imagine going back to a user interface where I couldn't type the first few letters of whatever I wanted to get it. Menu hierarchies are just bleh. I bet if you spent a month using and learning Win7 you'd never want to go back to XP.

Anyway, not quite sure what you mean by "It's in the handler for .NET 3.5". From that description you copied it makes it sound like running the dialogs in XP is supported. And I don't give it any gibberish like that for any parameters. It's the same code for me no matter what so if it was on my side you'd see it in both XP and Win7. If there's a problem it's probably in the Ookii dialogs source.

deltaecho5 wrote Aug 5, 2011 at 10:09 PM

I agree it's in the ookii side. I actually think it's a (WPF) font issue, from reading the site it's probably Japanese!

Don't agree on the Vista. Keyboard to mouse, mouse to keyboard transition issues. Perhaps why I didn't see the Menu Tree additions you made in that release. As someone who uses the keyboard to type, and the mouse to compute (leaving hands free to use the phone), buttons and mouse friendly GUI's are where it's at for me.

Some of it's today type/text more than average, as my generation had it's fill of typing (DOS) so we like the click method now.
I know some day I will have to upgrade to Windows 10+...but for now, most of corporate america is still running NT/XP, if it ain't broke, don't fix it.
They should have upgraded the motor, and left the GUI to skin how we like.

What about the TSR that a W7 non-issue to? ;)

RandomEngy wrote Aug 6, 2011 at 5:28 PM

Oh, missed that suggestion. Yeah, minimizing/closing to the notification tray is something that I've thought about but no one has ever asked for before. I'll put it on the feature backlog. As for the gibberish in the folder dialog problem: I hear you but may have a limited ability to fix it since I don't have an XP install to reproduce the problem. Would be happy to take a patch or an updated Ookii DLL though.

deltaecho5 wrote Aug 7, 2011 at 1:00 AM

Lemme look into Ookii...maybe bug report him and see if he can trace it. Unless of course he's a W7 borg as well...Lol