Greg,
I've been pretty busy, but I'm trying to take a look at this again
this weekend...
Did you get it compiling OK with the MS compilers in the end?
I guess you will need to "update" the project files to reflect the
files that are given in the Makefiles - I think the src, test and
xutf8 Makefiles will all need small adjustments, I'm sorry to say.
On 5 Sep 2007, at 1:18, Greg Ercolano wrote:
> 1) scandir_win32.c wouldn't compile because it's a 'c' app (not c++),
> and therefore doesn't like variables declared within the code, eg:
>
> --- snip
> strcpy(d, "\\*");
> }
> unsigned wlen = fl_utf8toUtf16(findIn, strlen(findIn), NULL,
> 0); // Pass NULL to query length
> ^^ FAILS HERE
> wlen++;
> --- snip
Right - I'll need to fix that. The gcc in mingw (which I use) is
forgiving of that sort of behaviour, so I didn't notice it was a
problem.
>
> 2) There was a valid warning in src/fl_call_main.c, where a function
> argument is being overriden by a variable definition within the code:
>
> --- snip
> static int mbcs2utf(const char *s, int l, char *dst, unsigned dstlen)
> { /|\
> static xchar *mbwbuf; |
> unsigned dstlen = 0; // <-- overrides dstlen defined here
> --- snip
OK, that's just leftovers from some hacks I was doing. I'll tidy that
away. The passed parameter is redundant.
Also, I'm still thinking about how best to proceed on the Xft
set_font front.
Also (also!) are you OK with the whole XFT thing? I know you were
worried about whether that might be an issue with your end-users -
but it does make a lot of stuff *much* easier on the *nix hosts, so
if possible, I'd like to keep it. It is very much more prevalent now
than once it was - but I don't have much access to non-linux unix
hosts these days so don't know how it will play over there.
Does look nicer on the display though!
Another thought: do any of your (non-latin-language) end-users need
to use XIM (or SCIM, or other platform specific composed character
entry method) ?
If so, that'll be something else to look at, as I'm not certain I
haven't broken the work that OksiD had done in that area.
Cheers,
--
Ian
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
