Actually Tom, I think I figured out a way around this. I've already put my 
stack scripts for the subModules into behaviors. By adding a selectionChanged 
handler in that behavior and checking to see if the dgControl of the target is 
empty, I can pass selectionChanged for fields and handle it for datagrids. Word 
5 to -1 of the dgControl is the long id of the datagrid. 

The only bugaboo will be when I send selectionChanged. The target will not be a 
control of the datagrid, but I can work that out easily enough. 

Thanks for kicking my mind in the butt. 

Bob S


> On Jul 19, 2018, at 07:38 , Bob Sneidar via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> Hi Tom. 
> 
> I usually find a way around things myself, but in this case, not. I have a 
> main form, where all the datagrids behave the same way on doubleMouseUp, 
> selectionChanged etc. I then have what I call subForms (substacks that detail 
> a given table and it's dependent tables like devices and accessories for 
> example) that behave in a different way, but all subForm datagrids have the 
> same behavior, different from the main form. 
> 
> I was hoping to be able to insert a special behavior between the datagrids 
> and the default behaviors. I also tried what apparently used to work, copying 
> the datagrid behavior to a button then setting the datagrid behavior to the 
> new button. That also does not work. 
> 
> 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

Reply via email to