Did you include "stack" in the variable name? Pretty sure you just need the stack's name, so maybe that was causing a failure.
As a quick and dirty test, I tried creating 3 new stacks, and executed variations of this line from the message box: set defaultStack to "untitled 3";create fld When running this here, switching the number after "untitled" causes a field to be created in the designated stack as expected. Maybe some other part of your script is forcing a change of the defaultStack. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 2/15/16, 10:16 PM, "use-livecode on behalf of Matt Maier" <use-livecode-boun...@lists.runrev.com on behalf of bluebac...@gmail.com> wrote: >It didn't. I set the defaultstack once when the whole thing loaded and >again right before creating the field, then had it put the defaultstack >into a variable so I could confirm it was correct. The words in the >variable were exactly what I wrote on the line (stack "HowstrBeta"). > >On Mon, Feb 15, 2016 at 10:07 PM, Scott Rossi <sc...@tactilemedia.com> >wrote: > >> If the goal is create an object in a specified stack, does setting the >> defaultStack first not work? >> >> Regards, >> >> Scott Rossi >> Creative Director >> Tactile Media, UX/UI Design >> >> >> >> >> >> On 2/15/16, 8:35 PM, "use-livecode on behalf of Matt Maier" >> <use-livecode-boun...@lists.runrev.com on behalf of >>bluebac...@gmail.com> >> wrote: >> >> >As far as I know I didn't make any changes that would explain this. >> > >> >All of a sudden this line: "create field stack "HowstrBeta" is giving >>me >> >this error "(Chunk: source is not a container), char 1" >> > >> >After some experimentation and googling I discovered that it would work >> >again if I changed that line to this: "create field (the long ID of >>stack >> >"HowstrBeta"). >> > >> >BTW, it was the same error for two other areas which created graphics >> >instead of fields. >> > >> >Any ideas why Livecode would happily take "create field stack >>"Whatever"" >> >for many months and then suddenly demand it be phrased differently? >> >_______________________________________________ >> >use-livecode mailing list >> >use-livecode@lists.runrev.com >> >Please visit this url to subscribe, unsubscribe and manage your >> >subscription preferences: >> >http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> >_______________________________________________ >use-livecode mailing list >use-livecode@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
