anks,
Steve Denney
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Ault
Sent: Tuesday, 28 November 2006 8:42 AM
To: How to use Revolution
Subject: Re: Copying many cds to a stack causes standalone to hang
On 11/27/06 1:58 PM, "Steve Denney" &
On 11/27/06 1:58 PM, "Steve Denney" <[EMAIL PROTECTED]> wrote:
> Hi PL,
> The app is a catalogue where users can view pics of the products & click on
> them to order (amongst other things).
> Currently each product page (card) is kept in a single cd stack file and all
> the pages are copied into
Steve,
How about having a stack with one card for each brand (that is to say, one of
each card that looks different from the rest)? Have this small stack open on
startup. Link each card to the database for that brand (or whatever determines
unique cards). As the user "opens" each card it is popu
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, 28 November 2006 2:22 AM
To: use-revolution@lists.runrev.com
Subject: Re: Copying many cds to a stack causes standalone to hang
Steve,
I don't know if this has been mentioned:
Rev opens, manipulat
Steve,
I don't know if this has been mentioned:
Rev opens, manipulates, and saves stacks with a lot of cards slowly.
We were updating one large stack that seemed to hang each time. It was
a stack imported from HyperCard where the same update took about half
an hour. The update consisted of pulli
2006 6:58 PM
To: use-revolution@lists.runrev.com
Subject: Re: Copying many cds to a stack causes standalone to hang
Hi Steve,
I *think* it might be related to the "start using" part of your
script. If you run in standalone mode the number of allowed library
stacks is limited (I
Malte Brill wrote:
Bill wrote:
That is a good catch; but shouldn't Rev throw an error message
instead of locking up?
...Regarding error throwing: In standalone mode the execution
halts regardless of the error, with no user feedback. I wouldn´t
expect anything to be thrown, unless explicitly
--- Steve Denney <[EMAIL PROTECTED]> wrote:
> I'm writing a product catalog application (for
> windows).
>
> The standalone is a splashscreen.
>
> A .rev file contains the main body of the
> application.
>
> Product pages (cards) are copied to the main body on
> start up (so pages can
> be added
Bill wrote:
That is a good catch; but shouldn't Rev throw an error message
instead of locking up?
I am not completely sure if it really is the problem. Normally I
would expect a stack to automatically be put out of use, once purged,
so my suggestion is really a shot in the dark. Regarding
That is a good catch; but shouldn't Rev throw an error message instead of
locking up?
Malte Brill wrote:
> I *think* it might be related to the "start using" part of your script.
> If you run in standalone mode the number of allowed library stacks is
> limited (If I recall correctly to 50). T
Hi Steve,
I *think* it might be related to the "start using" part of your
script. If you run in standalone mode the number of allowed library
stacks is limited (If I recall correctly to 50). Try inserting stop
using stack tCatalgPage before you close the stack.
hope that helps,
Malte
__
Steve,
- Does this behavior occur only in the standalone?
- What version of the product are you using?
- Can you try it with the 2.7.5 beta 1? Get it at
http://support.runrev.com/beta_test.php
- Does it crash 100% of the time?
- If so, can you file a bug on it and attach your stack/standalone:
h
I'm writing a product catalog application (for windows).
The standalone is a splashscreen.
A .rev file contains the main body of the application.
Product pages (cards) are copied to the main body on start up (so pages can
be added, edited, deleted). Product pages are between 200 - 750 KB (text +
13 matches
Mail list logo
