FiveTech Software tech support forums

... I stopped was 6.1 for the moment I don't remember the point I changed to another project. I still remember that I tested to convert in both directions. http://www.pflegeplus.com/IMAGES/Csvdbf1.jpg The problem was to find a solution, converting from CSV to DBF using a CSV-file ...

... 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 click enterafter editing.

Thank You very much that works fine and I could finish the tool If You downloaded the tool and it slows down with empty gradients ( shown as black ) please download again There is a problem with the gradient-position 0 I changed this value to 0.1 and it is working fine now http://www.pflegeplus.com/...

s there maybe a solution to protect a cell from to be covered from the focused rowcolor
to keep the cellcolor / gradient visible like used for images ?

oCol:bClrSelFocus := oCol:bClrStd

Thank You very much. It works with the same syntax like the normal gradientdesign. Is there maybe a solution to protect a cell from to be covered from the focused rowcolor to keep the cellcolor / gradient visible like used for images ? http://www.pflegeplus.com/IMAGES/gradsave1.jpg o...

Yes
Please try this way:

Code: Select all  Expand view

oBrw:aCols[ n ]:bClrStd := { || { CLR_BLACK, {{ 0.5, nClr1,nClr2 },{0.5, nClr2,nClr1}, .F. } } }

If the last element of the gradient array is not an array but logical .T. is vertical and .F. is horizontal,

James thank You now it works in all directions Just one little problem : the rows of browser 2 and 3 are drifting apart after a new field selection ( picture 1). Could it be possible to force them to show the result with the same row-position ...

I tested a solution that works in all directions The problem is not with bitmaps. The problem is with the painting of XBrowse. When we navigate to the cell with arrow-keys with go-up, go-down or go-left, the gap is not visible. But when we navigate ...

The calculation of a image-matrix resized in both directions http://www.pflegeplus.com/IMAGES/Zoom21.jpg FUNCTION SHOW_IMG( oWnd, nImgRow, nImgCol, nImgSpace, nFactorW, nFactorH, lWZoomed )LOCAL oGraphics := Graphics():New( ...

Hi Rao, Well explained. I will keep this open for some time.. for a while, I will test based on your directions how to avoid the issue (fields getting cleared) when trigger/procedure fires up. I will also check oRS:field => oRec:field while editing on screen. Thanks much ...

Thanks, this is no problem to respect!
But i test also ::move(,,nWidth,nHeight) or ::SetSize( nWidth, nHeight). This methods also give differences. (in VCC also the 10 Pixels to small in both directions)

I'm afraid Laiton is on x a i ler - minigui directions - but I'm not sure

... maybe go to meeting, come back after an hour and you find a lot of things that no longer work. Maybe we are unprepared and Microsoft has given directions on how to do with customers , I do not know..

Silvio, add to this sample the following : ( works in both directions ) ... ... ACTIVATE WINDOW oWnd ; ON RESIZE ( oVSplit:AdjLeft(), oHSplit:AdjRight(), ADJUST_POS(oWnd) ) return nil // -------------------------- // DEFINE WINDOW oWnd FROM 1, 1 TO 400, ...

Uwe,

very good

many thanks,