Progress Reporting When Building Standalones

Rob Cozens rcozens at pon.net
Mon Mar 6 12:29:28 EST 2006


Hi All,

When the RunRev Team requested that more people try v2.7.1 on WinXP 
last week, I decided to give it a go.

Here's what I reported back to them:

> My first experience -- Motion M1300 running XP TPC Edition 2005 -- 
> went beautifully until I built my first standalone.
>

At that point I thought RR had hung the system because I saw _nothing_ 
change on the screen for several minutes and when I tried to close the 
Revolution window XP told me it was not responding; so I shut the 
computer down.

It turns out I was just impatient (and perhaps gun-shy from others' 
reports): I was building standalones for both MacOSX and Windows from 
my 90M Photo Portfolio stack, and I now know the process takes in 
excess of four minutes... during which the IDE does nothing -- not even 
a cursor change -- to provide any progress feedback.

So I've added an enhancement request to Bugzilla asking for progress 
reporting during standalone builds.  If you wish to support my request, 
vote for bugzilla #3369
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=3369>

The good news is this is the _only_ issue I have encountered so far in 
v2.7.1 on XP.  All the stacks I tried so far open, could me modified, 
and run with no problem.  Ditto for the standalones... once I gave the 
IDE time to build them.     :{`)

Rob Cozens
CCW, Serendipity Software Company

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)




More information about the Use-livecode mailing list