[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] WM_REPOSED implementation
Selon Evan Langlois <Evan@CoolRunningConcepts.com>:
> On Thu, 2005-12-08 at 22:54 +0100, olivier.landemarre@utbm.fr wrote:
>
> > You are true, but unfortunatly some software doesn't like or simply not do
> it.
> > But for your question, it was write on PureC doc!
>
> The PureC documentation actually said that? Wow. I know the early days
> of the Atari had bad developer tools, but thats just aweful.
>
> The old GEM Developers Kit uses sample code like this...
>
> case WM_SIZED:
> case WM_MOVED:
> if(msgbuff[3] == wi_handle){
> if(msgbuff[6]<MIN_WIDTH)msgbuff[6]=MIN_WIDTH;
> if(msgbuff[7]<MIN_HEIGHT)msgbuff[7]=MIN_HEIGHT;
>
> wind_set(wi_handle,WF_CURRXYWH,msgbuff[4],msgbuff[5],msgbuff[6],msgbuff[7]);
> wind_get(wi_handle,WF_WORKXYWH,&xwork,&ywork,&wwork,&hwork);
> }
> break;
>
>
>
> > This look stupid, and in fact I agree it's stupid, but this is the life. Do
> an
> > AES compatible with application is sometime not easy to do or enhanced it.
> Don't
> > think only some softwares have trouble, because if we think this and if
> it's
> > true, there is so many case of misworking software, that if we not do some
> > effort in AES side probably 80% of softwares couldn't work correctly (ex
> > Papyrus, Calamus...)
>
> Well, if the software bites ass, what is the point? If you're saying
> even Calamus and Papyrus are crap hacks, then there isn't much left.
> Maybe its time to spend less time tweaking the OS for old hacks and more
> time replacing old apps.
But wich applications? Who have 4 or 5 year to spend to write a Papyrus replace
for example? For one mistake perhaps in the code (Papyrus call AES before doing
appl_init() for example so for some function we should admit that application
could call aes before appl_init()), correct source code is easy, but we have
not source code for this.
>
>
>
>
>
Olivier
--