Magic Formation - launcher
Magic Formation - launcher
Magic Formation is a cool, free, and highly customizable, dock like program that can be invoked anywhere by a circular mouse gesture (or assigned hotkeys).
It doesn't write to the registry (settings are saved in an .ini file in the application folder)
A few good tweaking tips @ http://www.aqua-soft.org/board/showthread.php?t=45974
It doesn't write to the registry (settings are saved in an .ini file in the application folder)
A few good tweaking tips @ http://www.aqua-soft.org/board/showthread.php?t=45974
ooooh i like this! you can bring it up by hitting CTRL twice, then each app in the menu can have its own hotkey. so CTRL-CTRL-F gives me Firefox, while CTRL-CTRL-U gives me UniExtract. or, if my hand is on the mouse instead of the keyboard it still works nicely with the gesture.
even better, hit up and it switches to task mode, then hit a letter to switch to that window.
sweet
even better, hit up and it switches to task mode, then hit a letter to switch to that window.
sweet
This may be my favorite dock-style launcher, if only because it makes it so easy to use either the mouse or the keyboard or both.
Be aware that the default is to store "per-machine" settings. It prepends the ini file with the computer name, so that the settings are portable inasmuch as they're stored in the same folder as the executable, but they won't get used when you run it on another machine. To make the settings get used on any computer you can either disable this in the options ("Other"), or just delete the computer name from your ini to make it "MagicFormation.ini".
That's an nifty feature, something I haven't seen in any portable app, but it's too bad that you can't have both: if MagicFormation.ini exists, those are the settings it uses, even if MACHINEMagicFormation.ini exists and you're on MACHINE. It'd be nice to have generic settings for most computers and specific settings for the machines you use most often.
Since it wasn't mentioned here, it does support portable paths (as well as passing arguments and setting working directories).
Be aware that the default is to store "per-machine" settings. It prepends the ini file with the computer name, so that the settings are portable inasmuch as they're stored in the same folder as the executable, but they won't get used when you run it on another machine. To make the settings get used on any computer you can either disable this in the options ("Other"), or just delete the computer name from your ini to make it "MagicFormation.ini".
That's an nifty feature, something I haven't seen in any portable app, but it's too bad that you can't have both: if MagicFormation.ini exists, those are the settings it uses, even if MACHINEMagicFormation.ini exists and you're on MACHINE. It'd be nice to have generic settings for most computers and specific settings for the machines you use most often.
Since it wasn't mentioned here, it does support portable paths (as well as passing arguments and setting working directories).
This application rocks
The title says it all
One really crazy thing though. Am using Vista, and when I do the twiddly thing with my mouse (or the double shift/CTRL) over Internet Explorer nothing happens. I don't have the same problem with any other programme showing... (BTW, was only on IE because I was backing up my PortApps - including Firefox! so it won't be a problem... but it's a strange thing...)
One really crazy thing though. Am using Vista, and when I do the twiddly thing with my mouse (or the double shift/CTRL) over Internet Explorer nothing happens. I don't have the same problem with any other programme showing... (BTW, was only on IE because I was backing up my PortApps - including Firefox! so it won't be a problem... but it's a strange thing...)
Try to contact Koji - the developer of MagicFormation, through the MagicFormation Feature Suggestions Forum @ http://winflip.stylekings.de/board/inde ... sg125.htmlLupo73 wrote:Someone know how to contact the author?
-
- Posts: 133
- Joined: Wed Sep 05, 2007 8:42 pm
relative paths how?
Ashghost (or whomever else can answer), how do you get this to work with relative paths? It's probably my favorite launcher so far, I'm using on my laptop extensively, but I haven't succeeded with relative paths at all yet.
When I do:
\Program Files (portable)\subpad\subpad.exe (trying from the root of the drive)
it just plain doesn't work. No icon, no nothing. When I try:
..\subpad\subpad.exe (Magic Formation is in its own directory under the "Program Files (portable)" one)
it apparently finds the .exe, since it displays the correct icon, but when I click on it, it does NOTHING. And this is the case for every program, I just picked Subpad as an example.
Oh, and apparently no support for standard environment variables like %USERPROFILE% either?
When I do:
\Program Files (portable)\subpad\subpad.exe (trying from the root of the drive)
it just plain doesn't work. No icon, no nothing. When I try:
..\subpad\subpad.exe (Magic Formation is in its own directory under the "Program Files (portable)" one)
it apparently finds the .exe, since it displays the correct icon, but when I click on it, it does NOTHING. And this is the case for every program, I just picked Subpad as an example.
Oh, and apparently no support for standard environment variables like %USERPROFILE% either?
I don't know about the %USERPROFILE% variable.
However, the relative path you gave in your second example works fine for me, and is similar to how I have mine set up:
F:\
--Apps\
----ActiveIsoBurner\
----FreeCommander\
--------FreeCommander.exe
----MagicFormation\
--------MagicFormation.exe
etc.
The path ..\FreeCommander\FreeCommander.exe works just fine for me, but your other example does not. Have you tried using quotes, since you have spaces in your path?
However, the relative path you gave in your second example works fine for me, and is similar to how I have mine set up:
F:\
--Apps\
----ActiveIsoBurner\
----FreeCommander\
--------FreeCommander.exe
----MagicFormation\
--------MagicFormation.exe
etc.
The path ..\FreeCommander\FreeCommander.exe works just fine for me, but your other example does not. Have you tried using quotes, since you have spaces in your path?
-
- Posts: 133
- Joined: Wed Sep 05, 2007 8:42 pm
Hmm, interesting - it actually removes quotes! No, that didn't help. I also tried putting into a temp. directory structure where none of the folders had spaces. In all cases, the correct icon's showing, so it found the .exe, but it just won't execute for some reason.
I'm changing both ITEM_PATH and WORK_PATH to be relative (identical, except for the addition of \prog-name.exe at the end of ITEM_PATH) and doing so by editing in Notepad. Any difference from what you're doing?
Thanks for the help!
I'm changing both ITEM_PATH and WORK_PATH to be relative (identical, except for the addition of \prog-name.exe at the end of ITEM_PATH) and doing so by editing in Notepad. Any difference from what you're doing?
Thanks for the help!
I just tried setting a working directory and had the same problem, but then removed the trailing backslash, and it worked.
There aren't many portable apps for which I bother setting the working directory anyway - of several hundred I have configured to launch with PStart, I have a working directory set for only 3.
There aren't many portable apps for which I bother setting the working directory anyway - of several hundred I have configured to launch with PStart, I have a working directory set for only 3.
-
- Posts: 133
- Joined: Wed Sep 05, 2007 8:42 pm
So ..\subpad\ wouldn't work, but ..\subpad did? (as a working directory).
Completely removing the WORK_PATH worked for the program I tried, but neither of the above variants of WORK_PATH did...
Come to think of it, I've never had a trailing backslash (assuming I understood you right, as above), yet it didn't work either.
BTW, I just went and looked up "working directory" on Wikipedia. Not sure I entirely understand it all. What apps/types of apps require working directories?
Completely removing the WORK_PATH worked for the program I tried, but neither of the above variants of WORK_PATH did...
Come to think of it, I've never had a trailing backslash (assuming I understood you right, as above), yet it didn't work either.
BTW, I just went and looked up "working directory" on Wikipedia. Not sure I entirely understand it all. What apps/types of apps require working directories?
The programs I have that need a working directory are:
PCOrd and R: statistical programs, which use a working directory to determine where to find/save temporary (and sometimes non-temporary project files) that they necessarily create during operation.
Mnemosyne: rather than just looking for configuration and data files in the directory where the application is stored, it relies on having a working directory set.
Most of the portable applications in the database either automatically store settings in the application directory, look for configuration settings in the application directory before looking in user directories, or store nothing.
PCOrd and R: statistical programs, which use a working directory to determine where to find/save temporary (and sometimes non-temporary project files) that they necessarily create during operation.
Mnemosyne: rather than just looking for configuration and data files in the directory where the application is stored, it relies on having a working directory set.
Most of the portable applications in the database either automatically store settings in the application directory, look for configuration settings in the application directory before looking in user directories, or store nothing.
There definitely seems to be a bug in this program processing relative paths where the working directory is the same as the application directory. I thought I might have had this fixed a few times, but realized the garbled pop-up message I couldn't read was telling me I was setting my working directory to be different from my application directory. However, for icon options, relative paths where the path is relative to the root directory appear to work fine.
I think (i hope) i found an answer:
Just like old times in dos the name can only be 8 digits. So if you have something like clean after me.exe you should change it in
cleana~1.exe. (six digits, a tilde and a 1)
The whole thing looks like ..\cleana~1.exe.
Just the same for the path
Hope it works for you
Just like old times in dos the name can only be 8 digits. So if you have something like clean after me.exe you should change it in
cleana~1.exe. (six digits, a tilde and a 1)
The whole thing looks like ..\cleana~1.exe.
Just the same for the path
Hope it works for you