I did something like this once. I'm not sure if this is a good way to
tackle the problem or not but here's what you need:
- A BOOL ivar exposed as a property on one of your controllers:
BOOL isTableViewSelected;
@property(assign) BOOL isTableViewSelected;
@synthesize isTableViewSelected;
Thanks a lot Mark,
This works great. The only change I made is to test with isEqualTo for
the table view's specific instance to prevent adding rows when the
master table is the first responder. And no flickers when presenting a
sheet :-)
Thanks again,
Andre Masse
On Dec 19, 2008, at 06
On Dec 18, 2008, at 15:43, I. Savant wrote:
The issue Andre mentioned is that the app is mostly keyboard-driven
(and the key combo fires the button, which he fears can be triggered
inadvertently). This means it doesn't matter where the button is - the
key combo can still trigger the action wit
On Dec 18, 2008, at 15:42, I. Savant wrote:
I've only ever seen it return NO when the content collection isn't
present. In other words, if your Widget Detail controller's content
array (or set) is bound to the Master's selection.widgets and a valid
Master object is selected, it would return YES
On Thu, Dec 18, 2008 at 3:32 PM, Kyle Sluder wrote:
> If you place the control correctly (using a small square button with
> the standard plus symbol, located directly underneath the table view
> it modifies and flush with its left edge) then there will be no
> confusion. Clicking the button sho
On Thu, Dec 18, 2008 at 3:27 PM, Andre Masse wrote:
> BTY, when does NSArrayController canInsert: returns NO?
From the docs: "Returns a Boolean value that indicates whether an
object can be inserted into the receiver's content collection."
I've only ever seen it return NO when the content co
On Dec 18, 2008, at 15:32, Kyle Sluder wrote:
If you place the control correctly (using a small square button with
the standard plus symbol, located directly underneath the table view
it modifies and flush with its left edge) then there will be no
confusion. Clicking the button should transfer
On Thu, Dec 18, 2008 at 2:52 PM, Andre Masse wrote:
> 1- user select a row in the master table view,
> 2- press the button's shortcut (intentionally or not)
> 3- a row is added to the detail's table view but since it does not have the
> focus, the row selection's is grayed and its not that evident
On Dec 18, 2008, at 15:10, I. Savant wrote:
It's almost the classic "more security == less convenience"
scenario. In this case "security"
refers to that of your data integrity. :-)
Exactly :-)
Perhaps all your tables should use a datasource (and delegate). This
way your add button can
On Thu, Dec 18, 2008 at 2:52 PM, Andre Masse wrote:
> Let me explain a bit more. This is an in house application for only 3 people
> (me, my wife and my son) that was originally built with 4th Dimension. I
> agree that this is not the expected behavior for mac users but it is for
> mine, as this
Thanks for your reply.
Why do you need the button's enabled state to depend on which
control has focus? This is *not* usual Mac OS X UI behavior and is in
fact counterintuitive. As a user, I would never think to click inside
a table to enable an associated button. I would assume that - for
reaso
On Thu, Dec 18, 2008 at 1:57 PM, Andre Masse wrote:
> I'm using a classic master/detail view. The detail view has a bunch of
> fields, a table view and a button (with a shortcut) for adding rows to it.
> The table view is bound to an NSArrayController. Now, I want to enable the
> button only when
Hi,
I'm using a classic master/detail view. The detail view has a bunch of
fields, a table view and a button (with a shortcut) for adding rows to
it. The table view is bound to an NSArrayController. Now, I want to
enable the button only when the table view (in the detail view) has
the foc
13 matches
Mail list logo
