> <OT here in fltk.general>
> To Ian: it's your code, and it compiles well with the /broken/ MinGW
> wingdi.h, but not with Visual C++ (STR #2623) and the
> corrected mingw64
> header files. If you have a better idea than an autoconf
> "feature" test,
> please give a comment on STR #2622. Thanks.
> </OT>
I've noted this on the STR now, but...
If I understand the STR, the problem is that the lpClass member of the
GCP_RESULTSW struct is given inconsistent type depending on which header
we get?
And I wrote my code to match the headers I have - and the headers I have
are wrong...
So... We don't need the lpClass data at all (we don't use it) but I
initially thought we had to provide it anyway.
It now *appears* that we can set that to NULL if we are not using it,
and that might appease all the different compiler versions.
Can others test this? It works just fine for me, but then it worked
before too...
Here's the "patch" as I have it so far. In fl_font_win32.cxx @ line 345;
gcp_res.lpClass = NULL;//c_buff; -- here's the "fix"
gcp_res.lpGlyphs = (LPWSTR)w_buff;
gcp_res.nGlyphs = wc_len;
gcp_res.lStructSize = sizeof(gcp_res);
I've tested this in my surrogate-pairs test and it seems to run fine,
and I'm not seeing any other side effects.
We need more opinions though!
If this works, then we can strip out any references to c_buff, as it is
no longer used at all...
Any good?
Does this work in all cases?
--
Ian
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
