Windows, Shortcut, Strange.........

[Viktoras Didziulis]

Hi Garrett, 
 
you should set the working directory of the shortcut to the directory of
application and not the default (which is the directory where the shortcut
resides). 
 
If you use Inno setup to create your installer then installer directives
should contain WorkingDir: "{app}"; and appear like this: 
 
[Icons] 
Name: "{group}\YourSoft"; IconFilename: "{app}\YourSoft.ico"; Filename: 
{app}\YourSoft.exe"; WorkingDir: "{app}" 
Name: "{group}\{cm:UninstallProgram,YourSoft}"; Filename: "{uninstallexe}" 
Name: "{userdesktop}\YourSoft"; IconFilename: "{app}\YourSoft.ico";
Filename: "{app}\YourSoft.exe"; WorkingDir: "{app}"; Tasks: desktopicon 
Name: "{userappdata}\Microsoft\Internet Explorer\Quick Launch\YourSoft";
IconFilename: "{app}\YourSoft.exe"; WorkingDir: "{app}"; Filename: 
{app}\YourSoft.exe"; Tasks: quicklaunchicon 
 
 
To test whether this is the real source of your problem try manually editing
properties of your shortcut: 
right click it and check if "start in" field indicates the directory where
your program is installed. If it shows desktop directory instead - modify it
manually and try executing it again. Hope this helps. 
 
Best wishes 
Viktoras 
-------Original Message------- 
 
From: Garrett Hylltun 
Date: 04/28/06 06:21:52 
To: How to use Revolution 
Subject: Windows, Shortcut, Strange......... 
 
Rev 2.6.1 
 
Greetings, 
 
I was putting a project through it's paces before sending it to the beta 
team, when I encountered something really strange. 
 
I used an installer to install my program to Windows, setup a shortcut 
and uninstaller and then I ran the program by clicking the shortcut. 
 
Program launches just fine, but when I type a word in an edit box and 
hit the enter key, or return key, my program did not respond. I have 
the messages set. But also, I have a button that will send to the same 
code that the enter and return keys would send to, and again, nothing, 
as if the code in the stack just didn't exist. 
 
Closing the program and launching it again, either via the shortcut or 
directly double clicking on the program exe in the program files 
directory resolves the problem. Everything works as intended. 
 
This does not occur on OS X, and I haven't tried Linux, but I suspect it 
won't happen there either. 
 
Has anyone ever encountered such a strange thing like this before on 
Windows? 
 
Thanks, 
-Garrett 
_______________________________________________ 
use-revolution mailing list 
use-revolution at lists.runrev.com 
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences: 
http://lists.runrev.com/mailman/listinfo/use-revolution