FiveTech Software tech support forums

I have solved for me!

But as suggestion for XBROWSE:
A function similar to "SKIP FOR bFor WHEN bWhen" espacially for rows with one or more editable cells.
z.B. "SKIP FOR empty(Col1)"

I must compile fwpdf.prg as it is incompatible with printer.prg in case of ::say(...). And where are the source from HPDF_Page_TextRect(--)?

Sorry, but this is not compatible with printer.prg!! I never use nWidth and then the align right or center are not respected.

Please try without nWidth! oPrn:RoundBox( 3, 2.5, 9, 12.5, 1, 1, oPen, CLR_YELLOW, nil, "CM" )    oPrn:Say( 4, 2.5,   "Left at 4 cm",     oFont, , nil, nil, 0, "CM" )    oPrn:Say( 5, 2.5,   "Right at 5 cm",    oFont, , nil, nil, 1, "CM" )    oPrn:Say...

After compiling fwpdf.prg:
Error: Unresolved external 'HPDF_Page_TextRect(void *, float, float, float, float, const char *, unsigned int, unsigned int *)' referenced from C:\EUROSTAR\FWPDF.OBJ

If i remove all 'HPDF_Page_TextRect(...) it compiles and link correct!

As workaround in fwpdf.prg i make this correction: and now is functioning.
But this is not correct code, as nWidth is not respected as in printer.prg!!!!

Uwe,
it seems, that the C-function HPDF_Page_TextRect() are missing in the lib from (x)harbour. (or in source fwpdf.prg!?)

In fwpdf.prg ther are: but the \fwh\lib\hbhpdf.lib are not present!

Short: In a xbrowse a editable cell should only get the focus if a specified function gives .T., otherwise skip to the next row where the function gives the next .T.. I do with bChange but the skip should functioning in both directions with the up-/down keys and also with the V-scroll and after clic...

I have a xbrowse with a normal cell to edit and oBrw:nMoveType := MOVE_DOWN. Now i will skip to the next cell with value over 10. This should functioning also with arrow-keys and V-scroll. All lines <= 10 should not be reachable.

Mr. Nages, is this corrected in 20.02?

Mr. Nages, have you any answer?
Thanks

Karinha, the software is also using in a automode if after start nobody types in a password. After 10 secs the password-dialog ends and a predefined password is using. If inside the 10 secs a user types in a char, the timer stops and the user must type in the password. This problem is solved. NOT SO...

Hello karinha, now i found the reason for this problem. In my routine to sign in a have a timer, which go to standard-user after 10 secs. On the password get i have a clausula ON CHANGE: oTimer:deactivate() Now if i press letter for letter this is always executed and i cannot input further. Now i us...

Please Mr. Nages, show to that!
Thanks