ons then exit AutoSaveStack
if autosave not true then exit AutoSaveStack
put msg into x
put "saving stack" && s
save this stack
put x into msg
end AutoSaveStack
# -Original Message-
# From: Serge Grenier [mailto:[EMAIL PROTECTED]]
# Sent: 20 September 2000 05
Thanks Pierre,
here's my autosave script, as you can see you dont have to specify the path
to save!
here's my autosave handler
on AutoSaveStack
global autosave,autoSaveExceptions
if autosave="" then put the hilite of btn "Auto Save Stacks" of stack
"home" into autosave
put "execution err
[EMAIL PROTECTED] wrote:
> Lastly, I decided to put all the handlers into the stack of MCtools
The trouble with this approach is that it adds work
everytime you upgrade to a new version of MetaCard,
since they comme with a new version of MCTools also.
That's why I tend to leave MCHome and MCTool
I've seen msgs go
> through without being intercepted - needs more testing. Am I wrong? Is
> MCTools the very top of the hierarchy? can someone confirm or deny this?
>
> Thanks
> Xavier
>
> # -Original Message-
> # From: Serge Grenier [mailto:[EMAIL PROTECTED]]
>
hierarchy? can someone confirm or deny this?
Thanks
Xavier
# -Original Message-
# From: Serge Grenier [mailto:[EMAIL PROTECTED]]
# Sent: 19 September 2000 15:03
# To: [EMAIL PROTECTED]
# Subject: Re: Problem with scrollbar redraws
#
#
# > > IF ANYONE HAS A FORCE SAVE SCRIPT/STACK
> > IF ANYONE HAS A FORCE SAVE SCRIPT/STACK or CARD
> > AT ANY EVENT OF MC IM VERY VERY INTERESTED
Hypercard is built with the idea of saving all the time
so it saves rapidly just a little chunk at a time
and we barely notice it.
MetaCard is built with the idea of saving at the end of the sessio
.
It's quite nice...
# -Original Message-
# From: Dave Cragg [mailto:[EMAIL PROTECTED]]
# Sent: 18 September 2000 16:47
# To: [EMAIL PROTECTED]
# Subject: Re: Problem with scrollbar redraws
#
#
# At 1:08 PM +0200 9/18/00, [EMAIL PROTECTED] wrote:
# >Here's a twisted problem...
At 1:08 PM +0200 9/18/00, [EMAIL PROTECTED] wrote:
>Here's a twisted problem...
>
>I use my stacks on different systems (NT, metaframe NT, and sometimes Mac).
>
>When I open stacks made on NT (std) in a metaframe session, the colors of
>the toolbars seems to be all faded. For example the scrollbar
On 18/9/00 2:28 pm, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> well, I lost all my changes again. This is the most annoying thing of this
> product.
>
> You can change the stack properties, save it again and things still
> disappear. Anyone has had this???
>
> So I have to start all my test
IM VERY VERY INTERESTED
cheers,
Xavier
# -Original Message-
# From: Kevin Miller [mailto:[EMAIL PROTECTED]]
# Sent: 18 September 2000 14:30
# To: [EMAIL PROTECTED]
# Subject: Re: Problem with scrollbar redraws
#
#
# On 18/9/00 1:11 pm, [EMAIL PROTECTED]
# <[EMAIL PROTECTED]>
#
On 18/9/00 1:11 pm, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> # Hm - what bit depth are you running? If its 256 mode perhaps
> # you're running out of colors.
>
> im running in 256 colors... But if you draw a new field, and it looks
> correct. Could it be that metacard creates differnet co
# > When I open stacks made on NT (std) in a metaframe session,
# the colors of
# > the toolbars seems to be all faded. For example the
# scrollbar button looses
# > it's edges shadows, etc... Result is it's all grayed even
# though it works.
# Hm - what bit depth are you running? If its 2
On 18/9/00 12:08 pm, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
> Here's a twisted problem...
>
> I use my stacks on different systems (NT, metaframe NT, and sometimes Mac).
>
> When I open stacks made on NT (std) in a metaframe session, the colors of
> the toolbars seems to be all faded. For
13 matches
Mail list logo
