Kurt Wendt wrote on 2016-02-03:
To be more specific about what happens.
As I am trying out the Grid & doing Multi-Selects, at times I get the
spinning gizmo that replaces the mouse pointer/curser. But, it keeps on and keeps on spinning - then, if I click in the grid or on the screen - then entire session goes Hazy White. Then - if I click on that session again - I get the request about application not responding - Wait or Close.
I don't normally have these issues w/Grids. Could it be caused by the
Sub-Classing of a Grid - or maybe the Code in the Grid???
There's no way I can have this happening when I move all the changes to
Production - that would be Seriously BAD if it should happen in Prod! It would make Me look bad!
So - any help would be greatly appreciated.
TIA, -K-
Kurt,
It is acting like you are in a loop.
How do you test?
I launch a separate VFP session and run the CODE from it. (I use a custom config.fpw to launch the main prg for me.) This allows me to see things in the debugger. When a grid is involved, having focus on the debug window will often change the behavior seen.
Another way I test is start a separate VFP session with a custom config.fpw that launches startup.prg which will set up some variables and configurations, then launch the EXE.
Tracy Pearson PowerChurch Software