On 24 Jun 2016, at 16:43, Nicolai Hess <nicolaihess@gmail.com> wrote:

2016-06-24 16:03 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
if you send me the code, I can take a look.

Sorry if this sounds rude, but
did you actually read my mail, I mean the first one.

well�� after search, it was from 25 apr�� and my client didn��t show it to me (because I removed it, to clean)�� and it folded the quoted so yes, I read it�� like a month ago :)

If you don't have the time to look at this, it is ok. I will just try to find it out myself, or maybe torsten has an idea.

No problem.

well, but I��m particularly interested in UFFI, since is my new toy :)

and seriously, I want to make him really solid, so I jump in whenever I see a problem, even if I��m doing something different (merging pharo-vm with os-vm, now).

Anyway, I see the error: WinWndClassEx is generated with bad mapping�� this is fixed in new versions of UFFI so you need to regenerate the fields:

WinWndClassEx rebuildFieldAccessors. (Torsten needs to

but then�� I spotted a bug, because FFIConstantHandle>>value is not defined so you will still have an error :)

anyway, I updated both, OSWindow and UFFI so if I you load bleedingEdge of both, you will see something like this:

I already posted the code multiple times. There is no code I could send. It is all in the image (+ the OSWindow) project.

I'll try it again.

OS: Windows
- take a fresh
- load (from catalog browser) OSWindow

- execute this

| hInst wndClass |
hInst := WinProcess getVMModuleHandle.
wndClass := WinWndClassEx new.
wndClass hInstance: hInst.

Error :
Unable to resolve external type: HMODULE

OK, getVMModuleHandle expects a HMODULE type
We need to define a missing type, HMODULE, but that works (just like all the other H-WinHandle-Types).

Now execute it again:
New error:
"MessageNotUnderstood: SmallInteger>>isExternalAddress"

The question is:

Any Idea what is missing here, I need a way to store the HMODULE handle
in the structure of the WinWNdClassEx