Yeah, I had to talk to Mark Waddingham about it at one of the
conferences before I understood what I was doing. He asked me how many
images and what size each one was in pixels, whipped out his calculator,
and showed me a calculation that overran the length of the display.
Neither of us tried t
On 4/10/14, 1:14 PM, Phil Davis wrote:
I KNEW there had to be a good use for unplaced groups! Thanks. Do you
think it still works that way?
It does, I'm still working with the project. In retrospect I could have
used a substack but there are so many other substacks that I didn't want
to add a
I really appreciate you posting this. It's pretty eye opening for someone
less "under-the-hood" savvy like me who has been told for years that
LiveCode loads everything into memory at startup. I would never guess
that "load into memory" could have two different "definitions".
Regards,
Scott Ros
I KNEW there had to be a good use for unplaced groups! Thanks. Do you
think it still works that way?
Phil
On 4/10/14, 10:56 AM, J. Landman Gay wrote:
In my case, the solution was to unplace the group from any cards; an
unplaced group can still serve as a storage repository but won't be
loaded
On 4/10/14, 11:41 AM, la...@significantplanet.org wrote:
I changed the drive to which I build apps and both built just fine.
Don't know why.
Me either, that's pretty odd. I wonder if the standalone builder is
looking for resources in the wrong place. Now that you've narrowed it
down, it would
hello Jacqueline,
In response to my problem of building a standalone, you asked:
Does it have a lot of images?
Well, actually it does. But I had the same problem building an app with no
images. I changed the drive to which I build apps and both built just fine.
Don't know why.
Anyway, my
