Fred Kiefer wrote: > While tracking down a wrong behaviour in my own backend code I found > that this time it was not me getting things wrong but NSWindow. When > creating a new window the content size is handed on to the backend while > the very similar method placewindow:: takes the full frame not just the > content area. But if this is the way we want it it is fine for me, now > that I know it and adjusted my code to it. >
I think this could probably be fixed. It used to be hard because the old window:: method didn't have the stylemask included, so we couldn't calculate the content size (i.e. without title bar). Now that it's included we can do that. > Could anybody (Adam?) explain the semantic of the findwindow::::: > method? As our only official window server does not implement it an it > is never used from gui, we could perhaps drop it as well. > I took it out. I think it might be useful at some point, but we can always add it back. > Then there is this NSWindowDepth stuff, according to NSGraphics this are > rather complicated values that describe the availabe colours of a > window or screen. But in NSWindow 8 is returned as a NSWindowDepth and > the method [windowdepth] on XGServerWindow also returns rather just a > bit size. So what is the use of all this and what would be the correct > beahviour. > I'll have to look at that also... -- Adam Fedor, Digital Optics Corp. | I'm glad I hate spinach, because http://www.doc.com | if I didn't, I'd eat it, and you | know how I hate the stuff. _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
