On 11-Feb-09, at 21:30 , Graham Cox wrote:
On 12 Feb 2009, at 12:27 pm, Louis Demers wrote:
I Had not thought about plugins because all the devices are
identical in capabilities. The devices are complex cameras. I
wanted to have each cameras have it document window to display the
specific video feed, but a single palette to control the brightness/
zoom of the frontmost window/camera. This is an over simplification
because in reality, each camera has lots of controls and status. If
each camera/device has its own exclusive gui element, the screen
will be cluttered beyond acceptable. I was modeling my solution
around something like Photoshop or Illustrator where multiple
documents use the same set of palettes.
What you're saying is that you have many cameras, but want to
control one at a time. You are using the active window (or document)
as a selection mechanism to choose which camera to control.
Seems to me that if you want one camera per window, you'd want the
controls for that camera in that window, though I see what you're
saying about having too many controls. Maybe it's the selection
mechanism that needs more thought? You could have a single window
with a list of cameras and you select one to control.
I considered that and I'm still interested in that solution.
Then it becomes more like a master-detail interface which would be
probably more manageable.
If you do want to stick to one window per camera and have the
controls apply to the from window, you can use notifications to
listen for window activate/deactivate notifications and track down
the related camera via the window's controller, which would be a
class you developed.
I do not care about sticking with that paradigm of one window per
camera, but I'm conformable with that approach. But how to I get all
the sliders and gui elements of my palettes to now bind to the object/
camera that is selected.
In my current app, in the bindings inspector of the gui element, I
select my instantiated object in the bind to popup and enters the
model key path to the key of my object I want to control/display. That
works because the instantiated object in unique and in my MainMenu.xib.
But in the above scenarios, how do I configure my binding ? the key is
the same all over, but the bound object will be swapped by whatever
selection process I end up using. Or do I have hit a limit of the
binding mechanism. I doubt it, more likely a limit of my own
understanding of bindings 8-)
--Graham
Louis Demers eng.
www.obzerv.com
_______________________________________________
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 arch...@mail-archive.com
