Omnis Studio - Multi Library Tasks

[Stephane Pras]

Brian,

Further to your comments I discarded tasks LaunchA/LaunchB from MyLib and
directly inserted in MyLib:

Open library (Do not close others) {LibA}
Do LibA.$autoactivate.$assign(kTrue)

And same for LibB. Point (2) from paragraph below is gone, I'm only left
with (1) MyLib's Startup_Task and (3) the $activate in LibA and LibB (don't
know where else to put it) to enforce the use of the proper datafile at each
active task switch.

I can open and close both libraries at will, and each one is running fine
independently of the other (as required). LaunchA and LaunchB tasks were
overkill. I was mislead by Omnis Programming manual p.46 etc. I understood
additional task classes had to be created, while the Startup_Task instances
of each library are enough to do the job.

Do not hesitate to correct if I'm wrong on something !

Stephane

From:  Brian O'Sullivan <brian.os at verizon.net>
Reply-To:  OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
Date:  Tuesday, January 13, 2015 2:00 AM
To:  OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
Subject:  Re: Omnis Studio - Multi Library Tasks

On Jan 12, 2015, at 12:30 PM, Stephane Pras <stephane.pras at noos.fr> wrote:

>  Effectively inserting:
>  
>  $activate()
>       Set current data file {myFile}
>  
>  is enough to ensure that the proper data file will be used each time a task
>  is activated. But where to put it?
>  1. Not in the Startup_Task of the container MyLib;
>  2. Nor in any of the LaunchA or LaunchB tasks I put in MyLib to open and
>  close LibA or LibB respectively;
>  3. But only in the Startup_Task/Class methods of LibA and LibB.
>  Don't ask me why, I tried all, only (3) is working !


(..)

-brian o¹sullivan; bear, DE
(USA)_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com