Hi Mark Actually I wasn't, but when I commented out my whole newGraphic handler, the issue in my app remained the same. Works in the IDE (usually), doesn't work in the standalone.
So thanks for the thought, but it's got to be something else: also choosing the pointer tool (which works) does not then allow selection of graphics on the card even though they can be selected via script. I believe I have no cantSelect or cantModify properties set to true (though that may be the answer in the end, since the inability to select looks very much as if one of these props is true). I am still trying to strip it down to essentials, while doing other stuff (like driving from the South of France to London - all the way - tomorrow, and getting ready for that). Thanks Graham On 10 Jun 2013, at 18:02, Mark Wieder wrote: > Graham- > > Monday, June 10, 2013, 3:55:41 AM, you wrote: > >> There is just one 'newGraphic' handler, in the script of a >> mainstack which is acting as a library. All it does is log >> information like the cantSelect of objects - logging is just putting >> text into a field somewhere. When I comment it out, the program > > Are you passing the newGraphic message along after you process it? > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > 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
