Re: Resizing Funky
Re: Resizing Funky
- Subject: Re: Resizing Funky
- From: Walker Argendeli <email@hidden>
- Date: Mon, 25 May 2009 10:48:13 -0400
Because the nib has gotten crowded, I'm taking your second option.
Things are working well so far, with a few exceptions. The table's
vertical scrollbar remains the same size and moves to the left,
still. Secondly, when I resize the window, I'm having issues with
things going back to normal. I have a table view over a graphical
date picker, and when I make the window larger and smaller again, the
window goes right over the date picker, and when the window gets to
the minimum size, the table view is expanded almost to the bottom,
with the date picker barely showing. I haven't made many connections
yet, so I can't imagine it has to do with my code. Perhaps it's me
doing something weird in the size inspector, but some of these seem odd.
Thanks for the help,
- Walker Argendeli
On May 23, 2009, at 12:51 PM, Fritz Anderson wrote:
On 21 May 2009, at 11:33 AM, Walker Argendeli wrote:
I have a window with a tableview inside it, along with many other
views. When I click the resize button, most things do what they're
supposed to, except for two things: the table and title bar. The
title bar goes completely white, except for the "hide toolbar"
button which moves into a spot inside the table view (perhaps all
the buttons in the title bar have moved there and are simply out of
view). The table itself isn't expanding all the way to the left,
and the vertical scrollbar moves a third to the left and just
floats over the table, leaving a white bar where it should be. It
also remains at its original size. If I click on the "remove
toolbar" dimple twice, I get my title bar back and the scroll bar
goes to the correct size and moves over, leaving a black line where
it used to be. The table also remains not entirely expanded.
In Xcode, I get this in the console: Column identifiers used with
NSTableView autosave feature must conform to NSCoding protocol.
I don't use column identifiers that I was aware of (or autosave)
I'm not even sure how to use that...
Lastly, it's very difficult to resize by dragging the corner: moves
a pixel or two and stops.
If anyone could give me ideas on what to look for to solve this,
I'd appreciate it.
- Walker Argendeli
That's funky. I've never seen a view so screwed-up that it corrupts
the drawing of an NSWindow.
The fact that objects are showing up with unexpected types suggests
that something is being over-released, and an object of a different
class then gets assigned to the same memory block. Research
NSZombieEnabled and Tech Note 2124, section Cocoa/Foundation.
Second choice is that the relevant NIB is corrupted beyond repair,
or at least has accumulated a tangle of settings. Try starting a new
NIB and rebuilding by hand.
— F
--
Fritz Anderson -- Xcode 3 Unleashed: Now in its second printing -- <http://x3u.manoverboard.org/
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden