Good. From now onwards please use this function to copy any image to clipboard. Do not use any other existing functions and not even tclipboard class (till we improve in next version) function CopyImageToClipboard( cImage ) local hBitmap := FW_ReadImage( nil, ...
... so that we can assume, that the clipboard runs well under UTF-8 :D From now onwards, please use the above two functions. I noticed a small bug in TClipboard class and do not use it till it is fixed (for Unicode only) Both the above functions are available in FWH2204 but the second function requires ...
... oClp will arrive as a nil to function ColToString() and there should be no error TGet():MsgNotFound(0) also you need to define a local oClp := TClipboard():New() inside function ColToString()
... * Nueva función FW_CopyToClipBoard( uValue, [nFormat] ) --> lSuccess Función simple para copiar al portapapeles, sin tener que crear un objeto TClipboard. El segundo parámetro no es necesario si el valor es texto (ansi/utf8) o un manejador de imagen GDI+. * Nueva función (source\function\filename.prg) ...
... * New function FW_CopyToClipBoard( uValue, [nFormat] ) --> lSuccess Simple function to copy to clipboard, without having to create TClipboard object. Second parameter is not necessary of the value is text (ansi/utf8) or hBitmap of GDI+ image. * New function (function\filename.prg) ...
... * New function FW_CopyToClipBoard( uValue, [nFormat] ) --> lSuccess Simple function to copy to clipboard, without having to create TClipboard object. Second parameter is not necessary of the value is text (ansi/utf8) or hBitmap of GDI+ image. * New function (function\filename.prg) ...
... strings inside an excel file, using the clipboard for pasting the datas. The problem is that if I don't have a window or a dialog I cannot use the tclipboard class because it gives error saying this : Application=========== Path and name: C:\fw\excel_export.exe (32 bits) Size: 1.755.648 ...
... - Se ha solucionado una pérdida de recursos en el método Paste(). * TClipboard: - El método SetBitmap( ohBitmap ) informa de pérdida de recursos. Solucionado !!! http://forums.fivetechsupport.com/viewtopic.php?f=6&t=40035&p=239130&sid=32a11be08a7956146c2a481125f368d1#p239130 ...
The main issue raised in the topic is "Resource Leakage." The method oImage:CopyToClipboard() has apparent resource leakage because TClipBoard():SetBitmap( ohBmp ) has the leakage again because the C level function "SetClipboardData( CF_BITMAP, hBitmap ) )" has this "apparent" ...