Remember that all controls are views. Overlapping sibling controls
have a definite user interface smell.
Assuming that the overlapping controls are visible at the same time,
the appearance is likely to be unsatisfactory. Issues of mouse based
picking arise. Which control will be hit by w
On Sep 10, 2009, at 8:40 PM, Erik Buck wrote:
Don't overlap sibling views. Even though it works reliably now, it
is still a poor practice for controls and has a definite user
interface "smell."
Do you mean sibling *views* shall not overlap, or do you mean
*controls* shall not overlap?
On Sep 10, 2009, at 9:19 PM, Graham Cox wrote:
There are exceptions though. For example, two square buttons placed
side by side such that they share a 1 pixel frame border. That flags
an overlap warning, but it's the right placement for the best look
for the buttons.
One might be incline
On 11/09/2009, at 4:40 AM, Erik Buck wrote:
Don't overlap sibling views. Even though it works reliably now, it
is still a poor practice for controls and has a definite user
interface "smell."
There are exceptions though. For example, two square buttons placed
side by side such that the
On 9/10/09 3:51 AM, Steve Cronin said:
>I know I'm late to the game here but I just took my app for a compile
>under XC3.2 for the first time...
>
>A few NSString encoding loose ends OK but WHAMO my .xib files are
>hammered with ~100 errors (not warnings!)
>
>".. This view overlaps one of its sib
Don't overlap sibling views. Even though it works reliably now, it is still a
poor practice for controls and has a definite user interface "smell."
If you must use the same area of the user interface for different purposes at
different times, consider using a tab view with no visible tabs and
On Sep 10, 2009, at 9:39 AM, Steve Cronin wrote:
Do you have to re-jigger everything because IB can't fathom that
they might not be visible at the same time?
Probably. Can you combine those buttons and then change them as you
go? That would also conserve memory, disk space, & loading times
Nick;
Hey thanks for the reply!
Yes, I'm aware of the IB target setting.
If you still want to target Tiger this is a BIG surprise that these
are now treated as errors.
The really big question for me is how do you deal with 2 buttons that
lie one on top of the other but are never drawn at t
On Sep 10, 2009, at 2:51 AM, Steve Cronin wrote:
My base SDK is set to 10.6 and a deployment of 10.4.
Everything was peachy under 10.5 and XC3.1 no such warnings or errors.
Sooo does this mean I cannot use XC3.2 unless I fix all these issues?
Nib deployment targets are actually set in the ni
Folks;
I know I'm late to the game here but I just took my app for a compile
under XC3.2 for the first time…
A few NSString encoding loose ends OK but WHAMO my .xib files are
hammered with ~100 errors (not warnings!)
".. This view overlaps one of its siblings. Overlapping sibling views
10 matches
Mail list logo
