On Thu, 09 Oct 2008, Gerald Drouillard wrote:

Hi Gerald,

> The row position should not change if you are not on row 1 in a tbrowse and 
> you issue a refreshall.
>     proc main()
>        local o:=tbrowsenew()
>       o:gotop()
>       o:forcestable()
>       ?o:rowPos()     //1
>       o:down()
>       o:forcestable()
>       ?o:rowpos()     //2
>               o:refreshAll()
>       ?o:rowpos()     //1  - this should be 2
>     return

In CL5.2 the above code hangups. In CL5.3 it shows:
   1
   1
   1

Just like in Harbour:
   1
   1
   1

Though I've found one difference - Harbour tbrowse clear tbrowse area
even if there is no column just like in this test. The same is for
navigation which is skipped when there are no column.
But the results are exactly the same as in Clipper and the
skip block inside refreshAll() is executed exactly like in Clipper
if you add any column with exactly the same parameter.

I tested it with xHarbour original tbrowse and yes it gives different
results then Clipper and Harbour.

>> I cannot say how tbrowse code will work in xHarbour. Harbour does not
>> have some important functionality which exist only in Harbour and maybe
>> used by this code in some places.
>> Anyhow if you will find any incompatibilities to Clipper then please
>> send a message here. Maybe sth has to be fixed yet.
> Well, that one line is the only line that is holding back xhb users from 
> using it.

Maybe but I cannot promise that some other problems will not be exploited.
There are many small differences between Harbour and xHarbour which may
or may not effect this code.

>  I'll send it to xhb list to see if they want to fix 
> DESCEND/__enumindex()

xHarbour does not support __enum*() iterator messages, DESCEND,
multiple iterations in one loop, native hash item iterations,
assigning in string item iterations and enumerators message overloading
by user at all. I see that some simple emulation was added as PP rule
but it does not cover even 10% of Harbour functionality.
Maybe it's the only one problem but it's possible that also some other
problems will be exploited by this code not related to FOR EACH.
Just try. If you will find sth then please inform me. Maybe I'll
be able to help you.

best regards,
Przemek
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to