[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] usage of wind_calc()



tir, 05,.07.2005 kl. 21.45 +0200, skrev Arnaud BERCEGEAY:
> Hello,
> 
> >> >  WM_xxx messages contain work instead of full area coordinates,
> >> > wind_set/get() works with work areas too. No change in the way things
> >> > are handled here, except from cases where the application needs to
> >> > modify the new positions. For example snap this is what is needed now;
> >> >
> >> >  1. new_pos = WM_MOVED coordinates
> >> >  2. new_pos = wind_calc(WC_WORK, new_pos)
> >> >  3. snap(new_pos)
> >> >  4. new_pos = wind_calc(WC_BORER, new_pos)
> >> >  5. wind_set(handle, WF_CURRXYWH, new_pos)
> >>
> >> I don't agree at all ? Do you do such nasty stuff in your own  
> >> applications
> >
> >  Have you ever tried to snap a window containing text using the fonts
> > with/heigh? Have you ever looked at Qed source? Have you ever seen
> > Everest? You tell me how else to snap coordinates!
> 
> I cannot believe it ;)
> 
> Your only argument is application optimised to be faster on old "real  
> ATARI" computer without graphic card and with old VDI.
> 
> I don't remember why exactly the snap is needed, but i think it's because  
> of a line-A function to paste bitmap of characters to the screen, or  
> something like that. Maybe a VDI guru can give more information.
> 
> Anyway, the snap stuff is no more usefull...

 Ok. Tell that to Lonny Pursell. Tell that to the dude who wrote Qed.
Tell that applications that force the window width/height to be no
larger than a picture it shows. The above shows that you are so ignorant
that I dont want to discuss this with you any further.


 Good bye!