Search found 12 matches

In those case:

LOGFONT.java
LOGFONTA.java
LOGFONTW.java

We should use struct, cuz those struct are passed to Win32 API, java version use class then thru the wrapper .c files are sorta convert ...

and also subversion version is the DWT M6 version, my branch is from M8 version, and i did, cuz i didnt wanted to modify the DWT one, i started clean to keep the original import in the same order etc. ...

the file only content the headers and the classes, i want to make the whole kit to compile with only the declaration, the implementation is all commented out.
then if the interface can compile, then ...

I now have a swt-3.0m8-win32.lib with 276 .obj in it. Very Happy

- Steve

Aye my example is ALL the files of the swt m8 version, it might be a bit big Razz

- Steve

tryed new DMD 0.82

now where i had forward reference error, i get assertion in glue.c of the compiler....

- Steve

different approach and some hacking Razz

- Steve

the make generate me 32 .obj file now

im tired, going to bed now...................zzzzz

- Steve

my observation is that, inheritance in separate file only work on the fist one, as soon as i inherite a class from a already inherited one, i get forward reference issue.

Ex:

- Widget > Cont ...

that scary Razz

- Steve

I personaly prefer the use of struct. but in the current state of the project, i think its better idea to leave thing that can work as is. and change only thing that cant.

Traceability is very impo ...

SWT is a combination of classes and a native API wrapper written in C. for the D port we dont need the wrapper, we can call the native one directly.

So the port itself is more a port of the classes ...