Little offbeat timing on these notes but… who cares. Last week I was supposed to continue my work with the UI platform but decided to create the basics before that. I did lot’s of research on what it takes to add cross-platform support. Also been learning things about FPC which I’ll be using to compile CE 2.0. I won’t bother with Lazarus because I only need the compiler. I’ll do the coding in Delphi’s IDE which is much better IMHO.
Register as Default File Manager
On weekend I somehow ended up working with the “Register as Default File Manager” feature. Not really sure why I did it but it’s done now. It should work in XP, Vista and Win7, at least those I’ve tested. It probably will work in 2000, 2003 and 2008 too.
Notice, in Vista and Win7, Control Panel will open in Windows Explorer. Also child items in Control Panel will open in a separate window. At the moment I’m out of ideas on how to fix it. But it’s only a minor grief I think.
Change Log
- Added option to register CE as default file manager.
- Fixed bug in session loading when /icon switch is used.
- Fixed separator bug in FileSearch when using multible locations.
- Search button now shows progress dots when running.
- CurrentDirectory is now changed to the active path.
- Changed path handling to support environment variables.
- Updated Dutch translation (thanks to Karel Baerten).
- Updated Romanian translation (thanks to Stefan Arhip).
CubicExplorer 0.95.1.1449 (SVN Snapshot)
Installer (2.9MB)
Portable (3.4MB)
Default file manager…. Absolutely brilliant, and works like a dream
THANKS!!!
One question, though.. I could of course test it, but..: What happens if I delete the folder with CE or move CE to another location?
kick ass!!!
You da man!!! fantastic addition as always big thanks Marko
Loving the progress, but I noticed something of a bug. Registering CE as the default file explorer seems to prevent my Dropbox folder from syncing properly.
If I register CE as the default, then add something to my dropbox folder, dropbox won’t recognize that anything has been added and it won’t be synced. As soon as I “Unregister” CE, dropbox starts working again.
I wish I could be more help as far as looking into why this happens, but all I’ve noticed is that it does. Just a heads up
Another small bug – the command prompt button (from the customizer) won’t open a command prompt at the correct path if a hard drive is partitioned into multiple sections.
For example, my 128gb drive is split up into a C drive for programs and a D drive just for media/storage/etc. When opening a command prompt using the button in CE, it will be set to the root of a (seemingly) random drive. I say seemingly because I don’t know why what’s happening is happening, but obviously there’s a reason.
@Steinsk
That will cause an issue as you might guess. There’s really nothing that can be done to prevent this, well except warn users to unregister before moving/deleting CE. The Unregister button will work from any folder so it’s a quick fix, just Unregister and register again.
If uninstaller is used, there shouldn’t be a problem since it unregisters CE automatically.
@James
Dropbox seems to work fine here (Win7 64bit). Not sure what kind of voodoo dropbox is using but the default file manager setting shouldn’t have anything to do with how dropbox works. But again, who knows how they do things.
Not sure what’s up with the command prompt, everything seems to work fine here. What Windows version are you using?
Aside from the previous feature request, about Ctrl+PgUp behavior i would also like to report a bug: when switching tabs the status bar does not refresh.
I’m using CE version 0.95.1.1434 on windows XP sp3.
I’m on Win7x64.
The dropbox issue turned out to be unrelated, my mistake, I just coincidentally noticed it right after I registered CE as the default file manager.
As for the command prompt, here’s a more complete description of what happens.
My 128gb hard drive is split up into a C drive and a D drive. Say that I’m in D:\test1\test2\ the first time I hit the command prompt button in CE. A command prompt window will be opened to that location. Any other location on the D drive that I navigate to in CE, and then hit the command prompt button from, will start a command prompt in the correct directory.
However, after doing that, if I navigate to C:\test3\test4\ in CE and hit the command prompt button, a command prompt will open to the root of my D drive. If I type “C:” into this prompt and hit enter, the directory will change to C:\test3\test4\.
I’m not familiar with how command prompt handles keeping track of directories on multiple drives, but based on this behavior, it looks like it keeps track of the current location on each drive separately. When CE attempts to open a command prompt window in C:\test3\test4\, it successfully sets the C: directory to \test3\test4\, but ultimately ends up opening to the root of my D: directory instead of behaving properly.
Hopefully this is a bit more help in figuring out what’s going on.
Nice tips .Thanks.