Fast read pixel of the image file

[Eugene Lutsenko]

Thank you, Roger! I will try to learn and use. The results are presented to the board.

[Eugene Lutsenko]

Roger! I get to work with the standard graphic functions only in your test function and another function of another variable oStatic. In other features, the schedule hangs or error occurs when you create a graphic object. Please, help. Maybe for each function needs its own oStatic?

[Auge_Ohr]

Maybe for each function needs its own oStatic?

Windows use Device Context (hDC) while Xbase++ use Presspace (oPS)
if you want to "paint" with Windows API into Presspace you have to assign it as Device.

Code: Select all

   // make the presentation space and assign to Device
   //
   ::oPS := XBpPresSpace():New()
   ::oPS:Create(::Static1:WinDevice())
   ::oPS:mode := XBPPS_MODE_HIGH_PRECISION

   // hDC need for DLLcall
   //
   ::hDC := ::Static1:winDevice():getHDC()

i recommend to use Xbase++ Presspace and GRA Function to "paint" Lines and Circles.
i only use ::hDC for GetPixel() while Xbase++ does not have a GRA Function for it.

[Eugene Lutsenko]

Thank you, Jimmy!
I understand this and wanted. Roger gave an example and I based it did something very similar. But I was prepared to do so only partially, not fully. With these features Alaska I still feel some problemmy. Of course, I've seen and your implementation. But for me it is even more difficult. The problem in understanding the methods and classes. I will try next.

[Auge_Ohr]

The problem in understanding the methods and classes. I will try next.

the Problem why i have not used your Code are your Variable ... some declare as PUBLIC and other not ...

i recommend to compile with /W and declare all Variable

iVar Member of a Class are also "visible" everywhere in Class ( PRG ) but you must declare it !
Methode are the same as Function or Procedure include Parameter Syntax.
the benefit are those Class iVar which you do not have to pass as Parameter ... like a fieldwide STATIC (on Top) in a PRG.