On Wed, 23 Apr 2008, Lorenzo Fiorini wrote: > A user has reported ( and I've verified ) that there is a condition > where oBrw:forcestable() goes to a never ending loop. > Replacing only tbrowse.prg with a previous one ( not Harbour code ) > "solves" the problem.
I will need your help to locate it. In theory it's possible but it will need some interaction from user codeblocks, f.e. skipBlock can call some methods which will force tbrowse reconfiguration. In other situation it hsould not happen. > Now I'm trying to create a self contained test If you can then it will greatly help to find and fix the problem. > but in tbrowse.prg I've found: > /* TODO: CA-Cl*pper does not call ::stabilize() if TBrowse object > * is stable and does not need screen update. It may be important > * for applications which do not expect that cursor position may > * be changed. I'll change it in the future but first I will have > * to revert my stupid modifications in Harbour core code. Looking > * at old TBrowse implementation I replaced some: > * WHILE !oBrw:stabilize(); END > * with: > * oBrw:forceStable() > * In Clipper it's not the same because oBrw:forceStable() > * may not set cursor position and only ::stabilize() does it. > * [druzus] > */ > should I wait for the fix? It will rather not help. The old code also makes the same. Of course probably it's possible to hack forceStable to resolve the exact problem you have but it's not a serious solution and problem may return in the future. For real fix I need to exactly know what is wrong and compare it with Clipper. BTW have you tested this code with Clipper? best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
