Robert Brenstein wrote:
>
>
> If your saving is done on different cards in a multi-card stack or in
> multiple stacks, then you can do the above but show a substack
> instead of a field to ensure it is always above the card controls.
>
> disable all controls saving their enabled state
>
On Nov 11, 2010, at 6:15 PM, Mark Smith wrote:
Peter Brigham MD wrote:
The saving of the time in a customProp is because I have scripted
things so the stack is automatically saved every 20 minutes, or at
whatever interval the user chooses in the preferences. That feature
was irrelevant to yo
On 11.11.10 at 19:02 -0600 Mark Smith apparently wrote:
Hi Thanks, more like:
show something
save this stack
hide something
I'm on the verge of testing "something" to be some sort of modeless
stack/window. We shall see how it goes.
Thanks for the suggestion - M
If your saving i
revolution-boun...@lists.runrev.com
[use-revolution-boun...@lists.runrev.com] On Behalf Of dunb...@aol.com
[dunb...@aol.com]
Sent: Sunday, November 07, 2010 4:30 PM
To: use-revolution@lists.runrev.com
Subject: Re: alerts
I reread your post. I might still be confused by "without user interactio
Joe Lewis Wilkins wrote:
>
> Hi Mark,
>
> Why don't you create an image, paste it wherever you want into your stack;
> then when you want it to appear, just show it; when you're through with
> it, then hide it. I've done this a number of times. I usually create such
> images using MacDraft, but
Peter Brigham MD wrote:
>
> The saving of the time in a customProp is because I have scripted
> things so the stack is automatically saved every 20 minutes, or at
> whatever interval the user chooses in the preferences. That feature
> was irrelevant to your question and I could have taken
On Nov 10, 2010, at 11:46 PM, Mark Smith wrote:
Peter Brigham MD wrote:
Here's the way I do it. I show a small display stack, the idea is
just
that it's a billboard to tell the user that the saving is occurring.
It closes after the save is done.
on doSave
modeless stack "savingAlert"
william humphrey-2 wrote:
>
> Except it should have a progress bar.
>
One step at a time. But thanks for suggesting a future question :-)
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/alerts-tp3031113p3037243.html
Sent from the Revolution - User mailing lis
Peter Brigham MD wrote:
>
> Here's the way I do it. I show a small display stack, the idea is just
> that it's a billboard to tell the user that the saving is occurring.
> It closes after the save is done.
>
> on doSave
> modeless stack "savingAlert"
> wait 10 millisecs
> save s
In my case the save takes at most 2 seconds. Progress bar probably not
needed. Also, it's impossible (AFAIK) to tell in advance how long a
save will take, to the only progress bar possible for this situation
would be a barber-pole type bar.
-- Peter
Peter M. Brigham
pmb...@gmail.com
http:/
Except it should have a progress bar.
On Mon, Nov 8, 2010 at 8:47 AM, Peter Brigham MD wrote:
> Here's the way I do it. I show a small display stack, the idea is just that
> it's a billboard to tell the user that the saving is occurring. It closes
> after the save is done.
>
> on doSave
> mode
Here's the way I do it. I show a small display stack, the idea is just
that it's a billboard to tell the user that the saving is occurring.
It closes after the save is done.
on doSave
modeless stack "savingAlert"
wait 10 millisecs
save stack "pdData"
set the lastSaved of stack "pd
Hi Mark,
Why don't you create an image, paste it wherever you want into your stack; then
when you want it to appear, just show it; when you're through with it, then
hide it. I've done this a number of times. I usually create such images using
MacDraft, but I'm sure you can do the same with vari
Hi Craig,
Forget the part about not knowing when a save is done... I'm a little tired
at the moment but did figure it out.
I have code that says:
on mouseUp
save this stack
end mouseUp
Pretty simple. But there is no visible indication to the user in my stack
that anything happened. So what
Hi Craig, I looked up dialogs and what not in the dictionary and user guide
and all I found where ones driven by ask and answer (nothing like a 1 way
conversation like tell). In this case we don't need the user to dismiss
the dialog, or answer anything, we just want to inform them that somethi
I reread your post. I might still be confused by "without user interaction
when the action is complete". Is "the action" just the showing of the
dialog?
But if all you want is to show some sort of dialog, and then dismiss it,
just:
showYourDialog
wait 120--or whatever
hideYourDialog
Is you
Not sure what you mean. The save dialog has its own life: It does its
thing, and dismisses itself.
If there is no user interaction, you can just hide the dialog after a
certain amount of time has passed from when it appeared. Is that what you
needed
advice about? How to arrange that it dismiss
17 matches
Mail list logo
