FiveTech Software tech support forums

... just ones created with getstring(). What's the easy way to get all the possible methods, and variables from the TDC.OCX. Can you fix the column widths??? TDC is just something to know is out there; RDS is probably a better way to go, since it will also work with NutsScrape 4+; The only TDC Method ...

... loop. Anyway glad that the customer is happy with the speeds. The program has 3 main steps. 1. Parsing the data 2. Checking for maximum field widths 3. Writing DBF. Step 1 takes the least time. Can be optimized further but the benefits will not be perceptible and optimization excercise would ...

Above sample is extended to check field widths and write to DBF. #include 'fivewin.ch' #include 'xbrowse.ch' function Main() local cBuf local aData, aHeaders cBuf := MemoRead( 'input.txt' ) // parse and make a ...

... in between to right or left accordingly. 9. New Method: FontSize( +/- nIncr ): To increase or decrease the font size of the entire browse. Column widths are automatically adjusted. 10. Bitmaps were not correctly algned center earlier. Now Bitmaps are correctly centered when bStrData is nil. 11. ...

All, I have an xbrowse with six data lines. I set the length of each line to 25 chars and set all columns to be the same width. The problem is some of the datalines do not fit within the column width and require more room horizontally. This causes the other data lines to wrap and they are not visibl...

... be called with the array containing atleast one dummy row. This dummy row enables the browse object to assign columns with proper datatypes and widths. After oBrw:CreateFromCode(), add the two lines ASize( aData, 0 ), oBrw:Keycount(). * TXBrwColumn enhancements: a) New DATA nArrayCol. It is ...

... can be used for instant searching ( ie. you can set the order on a column, and start typing and reposition the highlight immediately ). 5) Column widths and alignment are easy to enact 6) It is easy to use alternate background colors on alternate rows. The problem with tSBrowse is that it loads ...

... source * * image. * * * * Notes: * * All HBITMAP parameters must be 24 bit-per-pixel DIB sections. * * All HBITMAP parameters must have the same widths and heights. * * Weighting values must be in the range of 0 .. 255. * * * \*********************************************************************/ ...

It sure would be.
I let the user select a font fontselect()
And then I want to save it, however, if the User chooses Arial 8 point,
I don't find that when I query the Font object. I get the heights and widths shown above.
If you can show me where the 0 amd -8 is found, that would be great.

... { || navega() }, "Checar nuevas versiones",; "Upgrade" ) oToolBar3:AddButton( { || oWnd:End() }, "Fin del programa", "Salida" ) // We set the widths for each toolbar oToolBar1:nWidth = 150 oToolBar2:nWidth = 500 oToolBar3:nWidth = 150 // Now we insert the toolbars into the rebar oReBar:InsertBand( ...

... }, "Users management", "Users" ) // oToolBar3:AddSeparator() oToolBar3:AddButton( { || oWnd:End() }, "Fin del programa", "Salida" ) // We set the widths for each toolbar oToolBar1:nWidth = 150 oToolBar2:nWidth = 500 oToolBar3:nWidth = 150 // Now we insert the toolbars into the rebar oReBar:InsertBand( ...

... }, "Users management", "Users" ) oToolBar2:AddSeparator() oToolBar2:AddButton( { || oWnd:End() }, "Fin del programa", "Salida" ) // We set the widths for each toolbar oToolBar1:nWidth = 290 oToolBar2:nWidth = 290 // Now we insert the toolbars into the rebar oReBar:InsertBand( oToolBar1 ) oReBar:InsertBand( ...

... }, "Users management", "Users" ) oToolBar2:AddSeparator() oToolBar2:AddButton( { || oWnd:End() }, "Fin del programa", "Salida" ) // We set the widths for each toolbar oToolBar1:nWidth = 290 oToolBar2:nWidth = 290 // Now we insert the toolbars into the rebar oReBar:InsertBand( oToolBar1 ) oReBar:InsertBand( ...

... does get displayed but then immediately overwritten by the original message. Also the SIZES clause in the documentation says that it contains the widths of the prompts, but it actually is the location of the right edge of the box containing the prompts. To be consistant with FW's other commands ...

... ENDPAGE oPen1:End() oPen2:end() oFont:End() ENDPRINT return nil And the two definable pens with different widths not shown correctly on the preview or the final printing . The final print out consist from a thin pen (oPen1) only. What can i do for this? ...