Stop Microsoft

All Things Microsoft => Microsoft Software => Topic started by: muzzy on 23 March 2006, 10:50

Title: Unicode script processor and reinventing the wheel
Post by: muzzy on 23 March 2006, 10:50

Goddamnit microsoft! This can't be right. GDI+ has its own unicode script processor and doesn't use Uniscribe to do its work. Why in the name of Eris does it do this?!

So, I just want to render some text. I'm using richedit as an editbox and displaying in a GDI+ rendered control. Turns out, the two render same string completely differently when there's some funny content in the string.

It looks like I'll have to do my text rendering using Uniscribe and GDI while the rest of the application renders itself with GDI+. Otherwise I'll have internal inconsistencies.

So, the GDI+ text rendering api is WORTHLESS, goddamn fscking WORTHLESS. Why was it implemented in the first place? Is unicode script processor really such a small thing that it gets reimplemented by microsoft on a daily basis or something? WTF? ASDFSLDFJLKDSFJGLKDJFLGKDJFLGK!L!J!!!!!!

Title: Re: Unicode script processor and reinventing the wheel
Post by: Refalm on 23 March 2006, 14:23

I know this is kinda off-topic, but are the transparant effects part of GDI+ too?

Title: Re: Unicode script processor and reinventing the wheel
Post by: muzzy on 23 March 2006, 16:50

With "transparent effects" I think you mean layered windows and they're not GDI+ although GDI+ provides easy way to implement per-pixel transparency with layered windows.  If you're interested in the programming perspective, you can read about WS_EX_LAYERED in msdn or you could check out my clock application (sources included) to see both layered windows and GDI+ in the same context:  http://hack.fi/~muzzy/code/

Title: Re: Unicode script processor and reinventing the wheel
Post by: H_TeXMeX_H on 23 March 2006, 21:30

AOENTHDUEOISNTAOEHDIUESONTDAOIE !!!!!

Title: Re: Unicode script processor and reinventing the wheel
Post by: WMD on 24 March 2006, 00:04

Quote from: H_TeXMeX_H

AOENTHDUEOISNTAOEHDIUESONTDAOIE !!!!!

I can feel my IQ dropping... :p

Title: Re: Unicode script processor and reinventing the wheel
Post by: H_TeXMeX_H on 24 March 2006, 00:23

Hey, but you can tell I use dvorak :D ... sorry, I felt the

Quote from: muzzy

WTF? ASDFSLDFJLKDSFJGLKDJFLGKDJFLGK!L!J!!!!!!

was unnecessary ... CAPS and senseless keyboard smashing

Title: Re: Unicode script processor and reinventing the wheel
Post by: piratePenguin on 24 March 2006, 00:27

Heh, I thought TexMex was just saying exactly what I was thinking. Nevertheless....

Quote

Goddamnit microsoft! This can't be right. GDI+ has its own unicode script processor and doesn't use Uniscribe to do its work. Why in the name of Eris does it do this?!

So, I just want to render some text. I'm using richedit as an editbox and displaying in a GDI+ rendered control. Turns out, the two render same string completely differently when there's some funny content in the string.

It looks like I'll have to do my text rendering using Uniscribe and GDI while the rest of the application renders itself with GDI+. Otherwise I'll have internal inconsistencies.

So, the GDI+ text rendering api is WORTHLESS, goddamn fscking WORTHLESS. Why was it implemented in the first place? Is unicode script processor really such a small thing that it gets reimplemented by microsoft on a daily basis or something? WTF? ASDFSLDFJLKDSFJGLKDJFLGKDJFLGK!L!J!!!!!!

GREAHTJYJEVAGFDSGREFAFDS!GREAW!"!!