Le 25 juin 2014 à 14:38, Christian Schmitz a écrit:
Did you load Growl framework?
Does our example work for you?
Ok, your examples work and I had not loaded the framework. Still, the
documentation doesn't tell anything about the need to load a framework (and the
link for more information
Hi Christian,
If you run the following code on Cocoa vs. Win32 (with GDI+ enabled), the final
picture result is different, it appears as if the pixels are mis-ordered:
Pushbutton1.Action
' testing PictureMBS byte order
dim w,h as integer
w=32
h=32
dim p as new picture(w,h)
dim r as
It seems that a workaround is to add this:
#if TargetWin32
data.EndianU32_LtoBMBS(0,data.size/4)
#endif
On Jun 27, 2014, at 9:03 AM, Michael Diehr m...@xochi.com wrote:
Hi Christian,
If you run the following code on Cocoa vs. Win32 (with GDI+ enabled), the
final picture result is
Am 27.06.2014 um 17:48 schrieb Michael Diehr m...@xochi.com:
Hi Christian,
A few questions:
1. Do you have any idea what's the fastest way to get access to the pixel
data ARGB (etc.) in a Xojo Picture? I'm trying to avoid making extra copies
of the data, both to avoid the memory
Am 27.06.2014 um 18:03 schrieb Michael Diehr m...@xochi.com:
Hi Christian,
If you run the following code on Cocoa vs. Win32 (with GDI+ enabled), the
final picture result is different, it appears as if the pixels are
mis-ordered:
fixed for next version.
Also for future I make the Offset
