datagrid scrolling question

[Brian Milby]

You can get/put data from/into the grid one row at a time without needing to figure out the group name, so you could have it update in real time in your external button. You should be able to use the same behavior script (possibly with a slight modification) everywhere.

I’m not at a computer right now so I will work out an example later if someone else doesn’t beat me to it.

Thanks,
Brian
On Aug 5, 2018, 10:02 AM -0500, Douglas Ruisaard <dougr at telus.net>, wrote:
> Thanks very much for the reply.
> Good question .. made me think about why that won't work very well for me (but it would, of course, work).
>
> The button on each row not only queries the associated wi-fi module, but the "mouseUp" handler in the Behavior Script acquires a response back from each module. That message gets put into one of the fields in the row... so even if I didn't try to make a "mouseUp" call to within the row, I'd still want to populate each of the row's fields with the returning result... which would, of course, entail using the pseudo-group names again... *if* I wanted to display the returning information for each row "in real time"... which I do.
>
> There are two simple solutions, one of which I have done. Expand the grid to show all 8 rows and the scrolling issue disappears. Or ... as you suggest, "acquire" each row's data "outside" of the grid and then just display the complete set of data at once. Currently I do the former. Works very well on my big desktop monitor but not very "practical" to port to my iPad or Android... or any small display device.
>
> Another caveat is that each call to a wi-fi module take about 1 second to complete. This is a function of the module and what I am asking it to do... NOT an issue with "tsnet" (which is great!). So, taking the latter (your) approach, I'd lose the "real time" aspect and have to wait (#-of-modules * 1 second) before seeing any results. Currently that would be 8 seconds... not a *long* wait but annoying (in this age of microsecond responses). Expanding the project to more modules, obviously, increase the wait time... and I like the real-time display.
>
> However, this is as much a learning exercise as anything else... so I still would greatly appreciate if you or anyone could suggest an alternative methodology for issuing any sort of message to a datagrid, if there is one. Perhaps my method *is* the only one. THAT would be valuable information to have, as well.
>
> Douglas Ruisaard
> Trilogy Software
> (250) 573-3935
>
> From: Brian Milby [mailto:brian at milby7.com]
> Subject: Re: datagrid scrolling question
>
> > My question is why use the button? Loop through the data in the grid and make the tsnet call manually for each line.
> > If the button is calling a script outside of the DG, then you can use the same call.
> > Then you don’t have to do any of those things to figure out the name of the row group.
>