On Sun, 03 Jul 2011, Ken Ray wrote:
Sorry Wilhelm, misread your post - ignore what I said in my previous
post to
the list.
Not at all, Ken. Your hint to the Livecode tab in the new preferences
was new information for me, as it places the path to the preferred
Livecode version then
Our new SB could maybe be considered to possess a similar simplicity,
but it is surely not obvious, unless of course you know which entries
are required.
After a lot of trial and error - yesterday and today - I think I found
out the minimal requirements to build a standalone (I am though
Wilhelm, I had the same problem with an old stack, Saving the stack in MC fixed
it.
Rob
___
metacard mailing list
metacard@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/metacard
Many thanks to Richard and Ken for the release of the new Standalone
Builder and the 4.1 IDE, not to forget the new Metacard Setup 2.01 by
Jacqueline - and I assume that the preparations by Klaus were helpful
for the developments of these tools..
The releases coincided with a palpable
For LiveCode Folder/Bundle - in the upper region of the Standalone Builder
- I had first chosen the Livecode runtime folder where the standalone
files reside - following in essence the procedure I had used before in the
3.0 MC IDE, namely locating the necessary file standalone. Instead we
Sorry Wilhelm, misread your post - ignore what I said in my previous post to
the list.
My proposal is to allow to point to the runtime folder only, which
could be copied into the Metacard folder. This would mean that you need
not have both the full Metacard and Livecode installations on the
