x is for architecture-specific integers: http://www.jsoftware.com/help/user/call_procedure.htm
On 1/11/2012 9:40, Cliff Reiter wrote: > In thinking about the best way to move forward the best of image3 addon > to 64 bit and J7 it seems to me that using OS resources would be > preferred over porting the image3 dll source to 64 bit. In the platimg > addon I see that Oleg managed that nicely in J6 32. I presume this has > also been done in J7 based on the J7 api/gdi addon. Any pointers to > where I should look for examples to that? > > In particular, Oleg uses > > GdipBitmapLockBits=: 'gdiplus GdipBitmapLockBits> i i i i i *i ' cdi > > while the API/GDI uses > GdipBitmapLockBits=: 'gdiplus GdipBitmapLockBits i x *i i i *x'&cd > > What do the x's mean. > > In J6 64bit neither work (using gdiplus.ijs I get furthest), further still > with > adding oleg's version above, but the actual memory data read fails > > z=. (h,w)$memr p,0,(w*h),4 > |domain error: memr > | z=.(h,w)$ memr p,0,(w*h),4 > |[-17] c:\data\io.ijs > > Ideas? > Best, Cliff > > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
