zryip theSlug wrote:
It could be a good indication that the datagrid library is simply
missing in the standalone.
As the library is not included, setting the dgText of the datagrid is
not trapped by the library. It should result of a group with the
dgText data included and stored in a dgText custom properties of the
DG object instead to be interpreted as a virtual property, the one
which populated each column and row of the datagrid group.
Given the flexibility of how standalones can be built, it may also be a
case of the behaviors not loading prior to the UI that relies on them,
one of the nuances of using behaviors that can make them cumbersome in
some setups.
To alleviate such issues I've requested that the team consider adding a
"resolve behaviors" command, which would be called at any time to
trigger the existing behavior resolution already in the engine, but
allows resolution to happen at a time of the developer's choosing:
<http://quality.runrev.com/qacenter/show_bug.cgi?id=8993>
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
LiveCode Journal blog: http://LiveCodejournal.com/blog.irv
_______________________________________________
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
