Hello Andre,
Thanks for the lesson!
-Scott Morrow
On Jul 28, 2008, at 9:49 PM, Andre Garzia wrote:
Scott,
using something like
launch -a app name
will free you from dealing with path references, for example:
launch -a firefox
will launch firefox no matter where firefox.app is located,
We received notification of your registration on Friday 25 July at 19:39.
Your keys were issued the same day at 21:42. You wrote to us on Monday 28 at
17:34, and we responded at 17:40 advising that your keys had been issued to
the email address you supplied and that you may wish to confirm your
Richard Gaskin wrote:
Corruption of a stack file per se is very rare with Rev
Yes, and strictly speaking this is not what is happening. What seems to
happen, single number of times a year on a stack in daily use, is that
quitting produces an abortive save. The stack script calls for
Hi Andre,
This doesn't work. Opening a corrupted stack doesn't throw an error.
You need to check the result.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Benefit from our inexpensive hosting services.
Le 29 juil. 08 à 06:07, Andre Garzia a écrit :
Using the property inspector to do so, added path references that
would not be mantained once you distributed your app. Doing it on the
message box is easier and safer I think.
Not the case in my context.
Debugging Externals, I was wandering
A couple of Applescript tips and a working script
[1] Remember, File type and creator codes are always 4 characters long.
[2] The Finder uses an indirect syntax to refer to a file on the hard drive
as string =
Macintosh HD:Users:sivakatirswami:Desktop:_temp:a tst creator:image.tiff
as alias
VMWare allows multiple shared folders, just go to preferences for each
virtual machine. This means that the folder is visible/read/write for both
Mac and Win. This should be the same for Parallels.
Jim Ault
Las Vegas
On 7/28/08 9:51 PM, Bill Vlahos [EMAIL PROTECTED] wrote:
In Parallels you
Thanks Andre - but destroystack is not the issue. For instance:
delete stack test
closes and removes a stack from memory (for a mainstack not substack)
regardless of the destroystack/window status or whether the stack is used as
a library. The issue is that it does not always work - and I could
Sivakatirswami, check your In Box.
I semt you a stack yesterday afternoon in an email titled File Typer
which I use here for getting and setting file types. Since this thread
persists I'm guessing you haven't gotten it yet
--
Richard Gaskin
Managing Editor, revJournal
Peter Alcibiades wrote:
What seems to happen, single number of times a year on a stack
in daily use, is that quitting produces an abortive save. The
stack script calls for save this stack on close. The stack
itself is not corrupted, it is saved as eg stack.rev~.
Your handling of that
Not sure, But I think the property inspector will not 'see' the bundle
that is in the OSX package. When building a standalone I have been
having trouble get my app to work until I copied the external outside
of the package and use the set the externals of stack . to get
it to work.
On Jul 29, 2008, at 6:46 AM, David Bovill wrote:
closes and removes a stack from memory (for a mainstack not substack)
regardless of the destroystack/window status or whether the stack is
used as
a library. The issue is that it does not always work - and I could
not track
down why. Thought
2008/7/29 Trevor DeVore [EMAIL PROTECTED]
On Jul 29, 2008, at 6:46 AM, David Bovill wrote:
Every time the engine checks for the existence of a stack, accesses a
property or issues the go command using the filename of a stack the stack is
loaded into memory. In your Galaxy example what is
Richard Gaskin wrote:
Your handling of that sounds good, but I'm curious: have you pinned
down what's causing these saves to be interrupted?
I think it must be something to do with the on/off switch. Maybe when they
switch off using that, if they hold it down long enough, it just
Here is a question that if it can't be done easily now might
be a good idea for a simple improvement to Rev;
Let's say I have a stack that uses many different buttons
groups the state of these controls changes during using
the program but when I quit and restart I want the original
control
On Jul 29, 2008, at 11:05 AM, David Bovill wrote:
2008/7/29 Trevor DeVore [EMAIL PROTECTED]
Every time the engine checks for the existence of a stack, accesses a
property or issues the go command using the filename of a stack the
stack is
loaded into memory. In your Galaxy example what is
JB,
Why don't you report the objects hilite state to a preference stack
you can save and retrieve by a simple start using stack
prefrences.rev each time your standalone starts up ? I use this way
all the time at start time of my Win32 and OSX standalones, to save
texts and buttons
I always get the generic 500 server error. I don't have access to the
error logs, but a copy that was sent to me had no script errors in it at
all, only the generic premature end of headers statement.
Is it possible that there's a missing library on the server? I ran into this
a long time ago,
If there is a stack C:/myStack.rev then
else
end if
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
Thanks, it looks like I will take your good advice. But
it would be nice to be able to just make it a selection
with the other control settings.
-=JB=-
On Jul 29, 2008, at 9:06 AM, Pierre Sahores wrote:
JB,
Why don't you report the objects hilite state to a preference stack
you can save
For one project I've been working on that includes many form fields
and suchlike, I've been giving each control a custom property
initialState that may contain text (or empty) for fields, true|
false for checkboxes etc, and so on. Then I have a handler that loops
through all the controls in
Peter Alcibiades wrote:
Richard Gaskin wrote:
Your handling of that sounds good, but I'm curious: have you pinned
down what's causing these saves to be interrupted?
I think it must be something to do with the on/off switch.
LOL. Yep, that'll do it. :)
Linux doesn't provide shutdown
Bonsoir JB,
On any platform, you can't modify a standalone:
So the best way, even for a simple stack, is to always save it in the
right state.
And it will open as you wish the next time.
To ensure that, all my stacks have a 'CleanStack' handler I feed
along my project gets ahead.
It sets
Thanks, that info helps a lot. I am still fairly new to Rev and have
never even made one of my stacks into a standalone yet so you
provided me a better understanding.
thanks again to everyone who replied.
-=JB=-
On Jul 29, 2008, at 10:23 AM, Eric Chatonet wrote:
Bonsoir JB,
On any
Trevor DeVore wrote:
Polling is entirely possible. delete stack is very reliable. Like I
said, I've never had it fail. When it *appears* to fail it is usually
because something is going on in the background that brings the stack
right back into memory.
If the stack has any pending messages
Ken Ray wrote:
I always get the generic 500 server error. I don't have access to the
error logs, but a copy that was sent to me had no script errors in it at
all, only the generic premature end of headers statement.
Is it possible that there's a missing library on the server? I ran into this
a
On Jul 29, 2008, at 1:44 PM, J. Landman Gay wrote:
Trevor DeVore wrote:
Polling is entirely possible. delete stack is very reliable. Like I
said, I've never had it fail. When it *appears* to fail it is
usually because something is going on in the background that brings
the stack right
On Jul 29, 2008, at 2:03 PM, Trevor DeVore wrote:
On Jul 29, 2008, at 1:44 PM, J. Landman Gay wrote:
Trevor DeVore wrote:
Polling is entirely possible. delete stack is very reliable. Like
I said, I've never had it fail. When it *appears* to fail it is
usually because something is going
Trevor DeVore wrote:
On Jul 29, 2008, at 2:03 PM, Trevor DeVore wrote:
On Jul 29, 2008, at 1:44 PM, J. Landman Gay wrote:
Trevor DeVore wrote:
Polling is entirely possible. delete stack is very reliable. Like I
said, I've never had it fail. When it *appears* to fail it is
usually because
On Jul 29, 2008, at 2:25 PM, J. Landman Gay wrote:
No, you're right, it closes and is removed. What I was thinking is
that since pending messages prevent quitting, they also prevent
closing -- but they don't. So scratch that. Like you, I've always
found delete stack to be reliable.
The
Merci beaucoup, Eric!
templatefield is very smart. First creating the properties and
later the field.
I did not know it before. I think I will change some of my scripts ;-)
Reinhold
Am 28.07.2008 um 19:00 schrieb [EMAIL PROTECTED]:
You can't set the style of a field to 'table': it would
Aloha, Richard:
Not yet... means Postini or Google blocked it. our domain is actually
having it's email hosted on google now...
I will go on line and check our quarantines
Or you could post to Rev Online; or I can let you on our wiki and you
can upload there...
Meanwhile we are
Sarah Reichelt wrote:
In my tests, using the or not made no difference, but file
references are a bit strange in AppleScript.
Try using:
set creator type of alias Macintosh
HD:Users:sivakatirswami:Desktop:_temp:a tst creator:image.tiff to
8BIM
and add the alias keyword to the file type line
Sivakatirswami wrote:
Richard Gaskin wrote:
I sent you a stack yesterday afternoon in an email titled
File Typer which I use here for getting and setting file
types.
Aloha, Richard:
Not yet... means Postini or Google blocked it. our domain is actually
having it's email hosted on google
Richard Gaskin wrote:
I sent you a stack yesterday afternoon in an email titled
File Typer which I use here for getting and setting file
types.
I just dropped it in RevNet - in Rev, see Development-Plugins-GoRevNet
Once it loads, see the Stacks section.
got it, thanks!
On Tue, Jul 29, 2008 at 12:41 PM, Andre Garzia [EMAIL PROTECTED]wrote:
get shell(touch tFile)
where tFile is the path of the app bundle.
and then backup solution, time machine and everything start working again
Just to reiterate, as tested by myself and Sarah. TimeMachine already looks
The statement: set the randomseed to x is not consistent. In both the
Rev and MC documentation, x must be an integer. So, for example, set
the randomseed to the seconds works in the sense that a new and
different sequence is subsequently generated by random and any
statements. But set
37 matches
Mail list logo
