Yes, but the message watcher is way too verbose. I do not need every system 
message, only the ones called by my own code, and I need to at least be able to 
discern when procedures exit. 

My reason is that I have 15+ modules that all need to use  the publish and 
subscribe method I am implementing, and it is a LOT easier to grok a summary of 
handlers as in the format below to ensure I am standardizing things in all the 
modules. 

I thought about using a common behavior, but each module has to subscribe to 
only the messages it needs. The messages are almost all querys of a database 
and populating of datagrids, which I am trying to synchronize throughout the 
application without repeatedly querying the same data over and over again. To 
simplify things, each module's subscriptions and the handlers they call are 
located in the respective card script. Opening the card sets up the 
subscriptions for that module, and closing the card clears them. 

Bob S


> On Oct 28, 2021, at 10:07 , J. Landman Gay via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> Like LC's Message Watcher?
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On October 28, 2021 11:28:34 AM Bob Sneidar via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
>> Has anyone written something that will trace the flow of a command or 
>> procedure and create some kind of rudimentary flow diagram? It can be text 
>> based something like:
>> 
>>      stack "Main Form"
>>              Openstack
>>                      setSubscriptions
>>                               subGetMainData, getMainData
>>                               subSetMainGrids, setMainGrids
>>                      broadcast subGetMainData
>>                      broadcast subSetMainGrids
>> 
>> etc.
>> 
>> Bob S
>> 
>> 
>> _______________________________________________
>> 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

Reply via email to