• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Non-square (triangular) views
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Non-square (triangular) views


  • Subject: Re: Non-square (triangular) views
  • From: Uli Kusterer <email@hidden>
  • Date: Sat, 18 Nov 2006 21:23:44 +0100

Am 18.11.2006 um 19:38 schrieb Gregory Weston:
Rosyna wrote:
Such as? The NSButton objects often overlap (it's frame is much
larger than is shown). Yet there are no issues.

Actually, I think this could be better settled if someone could show
a case of overlapping views becoming a problem having an issue rather
than people quoting documentation other people are misreading.

But strictly speaking that's all that's necessary. It's not about demonstrating positively that in some circumstance today they don't work. It's about an active statement from the library vendor that they cannot be relied on. Which means something that works fine in 10.4.8 may well break in a hypothetical 10.4.9.

I'm too lazy to dig them out, but anyone who doesn't believe that overlapping views don't work should search the list archives. I distinctly remember a couple problems with overlapping views scrolling by on this list months ago. Essentially, it boils down to Apple taking shortcuts in some cases when redrawing windows, so you can get odd redrawing bugs where half a view is missing if you overlap.


It's unsupported in the same way that assuming "int" is a specific size is unsupported.

Well, the difference being that binary compatibility for IA32 guarantees that "int" will be that size. However, considering we have 64 bit CPUs, it's obvious that those who didn't make that assumption are better off now, because their code will recompile for those with less changes.


A better example may be Apple's requirement that the stack be aligned on 16 bytes, which some custom compilers ignored because aligning only on 4 bytes as the processor manufacturer documented their CPUs worked fine on a G3. However, on the G4 all menus suddenly became coloured because AltiVec-optimized menu drawing code doesn't like its stack misaligned. So, even if it works for you, if Apple tells you you shouldn't rely on that, it's their way of telling you they have unannounced stuff in the pipeline that will break that.

OTOH I'd probably get a Leopard seed before I spent ages on implementing my own overlapping stuff, just in case they added that in the meantime.

Cheers,
-- M. Uli Kusterer
http://www.zathras.de



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Non-square (triangular) views
      • From: "I. Savant" <email@hidden>
    • Re: Non-square (triangular) views
      • From: Gregory Weston <email@hidden>
    • Re: Re: Non-square (triangular) views
      • From: "Bertrand Landry-Hetu" <email@hidden>
References: 
 >Re: Non-square (triangular) views (From: Gregory Weston <email@hidden>)

  • Prev by Date: Re: Determining system version revisited for Tiger
  • Next by Date: Re: Determining system version revisited for Tiger
  • Previous by thread: Re: Non-square (triangular) views
  • Next by thread: Re: Re: Non-square (triangular) views
  • Index(es):
    • Date
    • Thread