Data Grid objects in standalones
tore.nilsen at me.com
Fri Feb 6 16:41:39 EST 2015
Thanks for pointing me in this direction. I have read this lesson, and I have also made the data grid templates dud, although there should be no need for it, as the compiler does include the correct data grid template as a substack. The problem arises when I choose to move substacks into individual files during compiling. Then the application seems to lose contact with the data grid template stack. This happens whether or not I include a substack called data grid templates dud or not. As I need to get my application ready for my students for Monday, I think I will do as Bob S suggests and just “rewire” the structure in code.
> 6. feb. 2015 kl. 22.32 skrev Mike Bonner <bonnmike at gmail.com>:
> Tore, read this.
> Specifically the part of bulding with a datagrid using a splashstack. The
> easiest way to get functional datagrids that are parts of seperate stack
> files is to incuded a single substack in your main that is named "datagrid
> templates dud" so that the builder will decide to include all the datagrid
> support libraries. More detail available in the link from above.
> On Fri, Feb 6, 2015 at 2:27 PM, Tore Nilsen <tore.nilsen at me.com> wrote:
>> The problem with letting the compiler handle this is that I cannot access
>> the Data Grid Template stack from the main stack if it is not a part of the
>> engine file. The standalone setup dialog is somewhat confusing in the sense
>> that it seems as if it is possible to choose which substack files to
>> include with the engine file and which substack files to branch out in a
>> folder of its own. As far as I have discovered it is all or nothing. I
>> guess I will have to dive into the code of the main stack again and write
>> relative paths to all the stacks I don’t want to be a part of the engine.
>> Luckily there are not very many of them, and they are not called from more
>> than a couple of handlers.
>> Tore N
>>> 6. feb. 2015 kl. 22.17 skrev Bob Sneidar <bobsneidar at iotecdigital.com>:
>>> As mentioned in the past, the easiest way around this is to have a
>> mainstack that calls your actual application stacks. Password protect the
>> app stacks if you like to protect the code. That way the app stacks are not
>> actually a part of the read-only application, they are like support files
>> that can be modified if put in the right place, which the compiler does for
>>> Bob S
>>> On Feb 6, 2015, at 12:47 , Tore Nilsen <tore.nilsen at me.com<mailto:
>> tore.nilsen at me.com>> wrote:
>>> I am using several Data Grid objects, as tables, in a standalone. When I
>> try to manually enter data into fields in the data grid object it works
>> alright as long as the main stack and the substacks are built as a single
>> file, but not when I try to build the standalone with the substacks as
>> separate files. I guess the reason is that the main stack loses connection
>> with the Data Grid Template stack once this is moved into a separate file.
>> I would however prefer to have the substacks as individual files in order
>> to be able to upgrade them easily, without the need for an upgrade of the
>> application as such. Are there any solutions to this problem that does not
>> require a total rebuild of the application structure.
>>> Tore N
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode