On Aug 22, 2008, at 12:09 PM, Kyle Sluder wrote:
On Fri, Aug 22, 2008 at 10:58 AM, Paul Bruneau
<[EMAIL PROTECTED]> wrote:
I am forcing the view to update after a change to one of the order
step
objects in what I am sure is The Wrong Way™ by basically chucking
setNeedsDisplay into areas of my code such as the contextual menu
handling
code, etc. This works great for GUI-driven changes even though it's
wrong,
but it falls apart of course when changes occur due to Applescript.
Are you saying that when some GUI event occurs (like clicking a
button), you are calling -setNeedsDisplay: on your custom view?
Pretty much, yes, I'm sorry to say. There are no buttons, but you have
the idea. In that screenshot you see the contextual menu. I can set
some things from there, and one of the items in the menu makes a sheet
for some other choices. When the sheet is finished
Where's is your controller object?
It's in my nib! But which controller do you mean? I have an array
controller for the array that holds these orders and it is the
datasource of the table and is bound to the columns of the table.
All of your model changes should
be going through a controller, and this controller would know to
update the other views.
Yes I think we agree on that part! The problem I am trying to
communicate is where do I learn to make my model changes go through a
controller, and how do I teach this controller to know to update the
other views? As I said, I think I could get my way through this if the
properties were in the order objects, but they can be in the children
of the children of the order objects._______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
