[ros-dev] Problem with out current NtGdiExtGetObjectW implementation
jimtabor at adsl-64-217-116-74.dsl.hstntx.swbell.net
Mon Apr 30 17:21:46 CEST 2007
Timo Kreuzer wrote:
> 2. Use the old method of first calling IntGdiExtGetObjectW to get the
> needed buffer size then allocate a kernelmode buffer then call
> IntGdiExtGetObjectW again to tranfer the data then copy to usermode.
> This is slower and needs extra memory.
Calling kernel space is a bad idea, if you can avoid it. If the function can be
handled in user mode, intercept it there and return to the calling app. Most NtGdi
functions have no choice but to be called due to compatibility and test cases.
So, if that is the only way to get the size than we are stuck with it, until
we have a better way of fixing it.
I haven't imp the DC_ATTR yet, this may fix some issues.
More information about the Ros-dev