LiveCode Forums.

Hello All,

I'm trying to solve a lock up issue when loading my data grid and moving my card window.

I'm having issues where the window(the card window the data grid resides on) would report 'not responding' when I load data into my data grid and I try and re-position the window.

Is there a way solve this? Any known methods would be appreciated.

Ideally I'd like to move the window while the data grid loads and not have the card window lock up.

I don't believe it's a data grid issue since I experience this same problem when loading files as well.
It seems to stem from the fact I'm loading continuous data while I try and move my application Window around.

Thanks!

Hi tasdvl9,
Have you tried it as a standalone?
I think you'll find it doesn't react the same way.

Simon

tasdvl9 wrote: I'm having issues where the window(the card window the data grid resides on) would report 'not responding' when I load data into my data grid and I try and re-position the window.

Could you tell us how exactly do you load the data into your datagrid ?

And how long the whole operation takes ? And what is the total number of columns and rows of your datagrid ?

Do you use some kind of long SQL query, sent to a remote server, with a superlarge dataset, and a long script to process the data afterward and then to load them into the datagrid ?

Hi tasdv19

I was researching a similar situation recently can found this (thanks Google) https://www.mail-archive.com/use-liveco ... 46363.html where a "wait 100 millisecs" gave relief. It may be that even "wait 0 millisecs" helps - but I would suggest you add "with messages" (as in "wait 0 millisecs with messages")

Basically it sounds like you are maxing out the engine doing something (downloading large data? line by line population of the data grid?) - and not only do you want to free up the engine, you need to do so sufficiently that your OS doesn't slap a 'Non Responsive' label on your app.

Thanks for the replies everyone.

The wait 0 millisecs with messages seems to alleviate the issue.
Now it's just a matter of optimizing my code.