Thanks, Guga. This is old stuff, though - in the meantime, I've simplified it a bit...
GuiParas equ "Animated GIF viewer", w900, h700, icon Star
include \masm32\MasmBasic\Res\MbGui.asm
GuiControl Canvas, "canvas"
Event CanvasPaint
GuiImage wCL$(), fit
GuiEnd
Great work, but then i can´t see what is underneath. From the older code i saw you used
" gdi+ GdipImageGetFrameDimensionsList, gicbObj, addr DimensionIDs, 1
gdi+ GdipImageGetFrameCount, gicbObj, addr DimensionIDs, addr frames
mov ecx, frames
inc curFrame
If_ curFrame>=ecx Then and curFrame, 0
gdi+ GdipImageSelectActiveFrame, gicbObj, addr DimensionIDs, curFrame"
But, the new one..how it was created ?
Btw...Did you never considered creating a sort of "unfold macro" or a routine in masmbasic allowing to see the code being used underneath the macros/commands such as "GuiImage", "GuiControl" etc ? Altough i really like this form of simplicity, i fail to understand what Apis are involved behind those commands/macros.