Hello Scott,
Sorry to clutter things with another post but there was one thing I forgot to
include: the actual content of the variables. Sometimes the exact form of a
string is what trips me up so perhaps this will be helpful. I walked through
the debugger as this section of code was running
Wow,
Folks, this kind of stuff should be easy. Can we abstract that code into a
library? Also, Scott, did you solved it for Mac?
Cheers
andre
--
http://www.andregarzia.com All We Do Is Code.
___
use-revolution mailing list
Hello Scott,
The relaunch handler (in the stack script of the executable) should
still be in the message path even if you close the stack... unless I
misunderstand the design, the executable that stack is attached to
would still be in memory and running.
-Scott Morrow
Is it possible that
Recently, Scott Morrow wrote:
This post has the scripting I use for Relaunch so that multiple instance of
the app won't launch. I'm using it with a Splash-screen design as well. There
are 2 script blocks, the first of which has to go at the stack level.
[ snip ]
Thanks Scott.
I'm part way
Andre Garzia wrote:
Folks, this kind of stuff should be easy. Can we abstract that code into a
library? Also, Scott, did you solved it for Mac?
The problem of multiple instances doesn't happen on Macs, so you don't
have to do anything on that OS. The file associations are all handled in
the
Is it possible that app name entries in the registry need to be in 8.3
format? My app name is 31 chars long, including spaces. Maybe Vista is
choking on this?
Regards,
Scott Rossi
Creative Director
Tactile Media, UX Design
___
use-revolution
On Mar 3, 2010, at 3:17 PM, Scott Rossi wrote:
Is it possible that app name entries in the registry need to be in 8.3
format? My app name is 31 chars long, including spaces. Maybe
Vista is
choking on this?
You could try wrapping the name in quotes. I think you mentioned you
are using
Hi,
It is right that you need to catch the relaunch message in the stack
script of the stack that is opened first. This is always the stack
that is embedded in the executable. It can't be any other stack. In
your case, it is the splash stack. As far as I know, this is all
explained in
I'm still trying to get Windows file associations on Vista worked out over
here and am looking for suggestions.
I've set up registry entries based on Ken Ray's tips:
http://tinyurl.com/yfmdsht and everything appears to in place. But
documents created by my app continue to show up as generic
Are you trying to set the registry under Vista without administrative
privileges? (If UAC is enabled, and it is by default, then even if you are the
primary admin user of the system you won't have sufficient privileges to set
the registry. If you are testing this from the IDE, before
Recently, Scott Morrow wrote:
Are you trying to set the registry under Vista without administrative
privileges? (If UAC is enabled, and it is by default, then even if you are the
primary admin user of the system you won't have sufficient privileges to set
the registry. If you are testing
Recently, I wrote:
For documents launching multiple instances see relaunch in the
dictionary
where there is a note to look at an example stack.
In my stack, the relaunch message is apparently not being called for some
reason. I've tried placing it in the stack script and in a stack
From: cott Rossi
I'm still trying to get Windows file associations on Vista worked out over
here and am looking for suggestions.
I've set up registry entries based on Ken Ray's tips:
http://tinyurl.com/yfmdsht and everything appears to in place. But
documents created by my app continue to
Hello Scott
This post has the scripting I use for Relaunch so that multiple instance of
the app won't launch. I'm using it with a Splash-screen design as well. There
are 2 script blocks, the first of which has to go at the stack level. The pile
of comments indicates how insecure I was with
Hello Scott,
I'm not using Inno Installer but a custom installer application made with Rev.
Before trying to set the registry my installer has elevated itself to have
administrative privileges (by adjusting the manifest with Resource Tuner as
described by Trevor DeVore)
I believe this is all
Hi Scott,
It looks like you found all the information you need. I'm using the
same for an installer, which I use for quite a few different projects.
There are several intresting posts about this subject in the archives
of this list. On of them can be found here http://qurl.tk/4x You
Recently, Mark Schonewille wrote:
There are several intresting posts about this subject in the archives
of this list. On of them can be found here http://qurl.tk/4x You
probably have that info already, since it is Ken's.
Thanks Mark. The one (?) item I'm unclear on is the script example:
on
Scott,
That's right. You double-click a file in Windows and Windows starts
another instance of the executable for that file. In that executable,
you catch the relaunch message. If file $1 exists, don't return any
value from the relaunch handler. The new instance will be terminated
and
Hi Peter,
Add the following handler to the main stack script:
on appleEvent pClass, pID, pSender
switch pClass pID
case aevtodoc
request appleEvent data -- extract the path of the file to open
-- put here the code to process the file
break
default
pass appleEvent
end switch
Hi Thierry
Thanks very much for an excellent solution - just the job!
With best regards
Peter
Add the following handler to the main stack script:
on appleEvent pClass, pID, pSender
switch pClass pID
case aevtodoc
request appleEvent data -- extract the path of the file to open
-- put here
Ian Wood wrote:
On 27 Feb 2004, at 01:01, Mark Talluto wrote:
On Feb 26, 2004, at 1:08 PM, Richard Gaskin wrote:
I'm using the same standalone building process I've used for the last
year, only now on Panther my standalones won't recognize my custom
document types.
Also, when I modify the
I sometimes have to stuff the standalone. Then delete the
original. Then unstuff to get it all to work again. On really
bad cases, I file transfer the standalone to another mac and then
bring it back. This always does the trick.
As I mentioned recently on the list, deleting the standalone
Could you edit the finder flags and turned the Inited bit off and then open
the folder again?
At 11:18 AM 2/27/2004, you wrote:
I sometimes have to stuff the standalone. Then delete the
original. Then unstuff to get it all to work again. On really bad
cases, I file transfer the standalone
Yes, that is one of the tricks for MAc Classic. Not sure whether
still works under OSX.
Robert
Could you edit the finder flags and turned the Inited bit off and
then open the folder again?
At 11:18 AM 2/27/2004, you wrote:
I sometimes have to stuff the standalone. Then delete the
original.
Actually I have this same problem with windows xp.
I have to close a folder (or go up one level) and then reopen it to see
the 'correct' version of my rev standalones every time I build a new
one.
When I update my OSX standalones they are updated once the the folder
window is brought to the
On 27 Feb 2004, at 01:01, Mark Talluto wrote:
On Feb 26, 2004, at 1:08 PM, Richard Gaskin wrote:
I'm using the same standalone building process I've used for the last
year, only now on Panther my standalones won't recognize my custom
document types.
Also, when I modify the core engine name
26 matches
Mail list logo
