On Thu, Apr 16, 2015, at 09:46 AM, Roland King wrote:
>
> > On 16 Apr 2015, at 22:20, Gerriet M. Denkmann wrote:
> >
> >>
> >> On 16 Apr 2015, at 13:41, Roland King wrote:
> >>
> >>
> >>>
> >>> 5. Run
> >>>
> >>> iPhone- tapping on "Do & Back" prints:
> >>> 2015-04-16 12:16:52.799 Dum
> On 16 Apr 2015, at 21:42, Kyle Sluder wrote:
>
> On Apr 15, 2015, at 10:49 PM, Gerriet M. Denkmann
> wrote:
>>
>>
>>
>>
>> 3.Run
>>
>> Run on iPhone:
>> Back Button is called "Master"
>>
>> Run on iPad:
>> Back Button is called "Master iPad"
>>
>> Strange, but not very important.
> On 16 Apr 2015, at 22:20, Gerriet M. Denkmann wrote:
>
>>
>> On 16 Apr 2015, at 13:41, Roland King wrote:
>>
>>
>>>
>>> 5. Run
>>>
>>> iPhone - tapping on "Do & Back" prints:
>>> 2015-04-16 12:16:52.799 Dummi[28069:20737983] -[MasterViewController
>>> doSomethingAndBackToMaster:]
On Apr 15, 2015, at 10:49 PM, Gerriet M. Denkmann wrote:
>
>
>>> Can this be done? Or is there a better way to make my button work both
>>> for iPhone and iPad?
>>
>> Well, my first question is: can you just put your work in the
>> implementation of the unwind selector?
>
> That is the way the
> On 16 Apr 2015, at 13:41, Roland King wrote:
>
>
>>
>> 5. Run
>>
>> iPhone - tapping on "Do & Back" prints:
>> 2015-04-16 12:16:52.799 Dummi[28069:20737983] -[MasterViewController
>> doSomethingAndBackToMaster:] did something with "2015-04-16 05:16:49 +",
>> will do: [ perform]
>
> 5. Run
>
> iPhone- tapping on "Do & Back" prints:
> 2015-04-16 12:16:52.799 Dummi[28069:20737983] -[MasterViewController
> doSomethingAndBackToMaster:] did something with "2015-04-16 05:16:49 +",
> will do: [ perform]
>
> iPad - tapping on "Do & Back" prints:
> nothing.
>
>> Can this be done? Or is there a better way to make my button work both
>> for iPhone and iPad?
>
> Well, my first question is: can you just put your work in the
> implementation of the unwind selector?
That is the way the work is done.
> The unwind itself will be a no-op
> if the split view
On Wed, Apr 15, 2015, at 07:18 AM, Gerriet M. Denkmann wrote:
>
> While my iPhone can use the “DoSomethingAndGoBackToMasterView” button
> fine,
> the same button does nothing for iPad.
>
> Of course iPad does not need an unwinding segue - both master and detail
> view are always visible (at least
While my iPhone can use the “DoSomethingAndGoBackToMasterView” button fine,
the same button does nothing for iPad.
Of course iPad does not need an unwinding segue - both master and detail view
are always visible (at least in landscape orientation). But the “DoSomething”
part is still needed.
C
> On 15 Apr 2015, at 15:37, Quincey Morris
> wrote:
>
> On Apr 15, 2015, at 01:18 , Gerriet M. Denkmann wrote:
>>
>> In DetailViewController I added:
>>
>> - (IBAction)unwindToMainMenu:(UIStoryboardSegue*)sender
>
> I dunno offhand, but you originally said you’re trying to go back to the
>
On Apr 15, 2015, at 01:18 , Gerriet M. Denkmann wrote:
>
> In DetailViewController I added:
>
> - (IBAction)unwindToMainMenu:(UIStoryboardSegue*)sender
I dunno offhand, but you originally said you’re trying to go back to the master
view controller, and the tech note says that the destination n
> On 15 Apr 2015, at 14:51, Quincey Morris
> wrote:
>
> On Apr 14, 2015, at 23:47 , Gerriet M. Denkmann wrote:
>>
>> Using the Xcode template: iOS - Master-Detail, the Detail view has (in the
>> top left corner) a Back-Button, which works fine.
>>
>> Now I added another UIBarButtonItem call
On Apr 14, 2015, at 23:47 , Gerriet M. Denkmann wrote:
>
> Using the Xcode template: iOS - Master-Detail, the Detail view has (in the
> top left corner) a Back-Button, which works fine.
>
> Now I added another UIBarButtonItem called: “Do something and go back”
> connected to some IBAction in D
We've had a lot of success with this:
https://github.com/mattgemmell/MGSplitViewController
though we've customized the heck out of it too...
On Mar 26, 2013, at 10:34 AM, Fritz Anderson wrote:
> On 25 Mar 2013, at 7:13 PM, koko wrote:
>
>> The Master - Detail template for an iOS app is a good
On 25 Mar 2013, at 7:13 PM, koko wrote:
> The Master - Detail template for an iOS app is a good place to start but, ….
>
> … how does one size the split view to proportions dictated by the new app
> being developed?
You don't. UISplitViewController is hard-coded to make the master view 320
po
Thanks Graham, that has 90% of my issue addressed. The system seems to swallow
a couple of keystrokes entering each table, but at least it does get there. I
suspect a few judiciously placed refusesFirstRespnder's and I'm home free.
Cheers,
Erik
On 2012-08-05, at 6:47 PM, Graham Cox wrote:
>
On 06/08/2012, at 11:38 AM, Erik Stainsby wrote:
> My first higher-level question then is how I ought to be going about
> establishing the tab-key behaviour sequence I want to achieve?
Have you investigated whether -[NSWindow recalculateKeyViewLoop] would do the
job? I've used this after in
No, I meant the detail view changes the value according to the switch. And in
my case it is actually a array in the person class and the switch determines if
it is the first, the second or the third value to display.
in the TableView I can do that with the datasource methods.
Thanks
g
On 16.0
On Mar 16, 2011, at 09:57, Georg Seifert wrote:
> If I have a master detail interface bound to a array controller.
>
> To explain my problem (the actual structure is different but as an
> explanation):
> The list shows a some persons. Then I have a switch that selects if the
> detail view shows
On Wed, Apr 15, 2009 at 4:42 PM, Sean McBride wrote:
> Correct. But as you say, it seems that it should do that. So I created
> a test app and it behaves as expected there. I added a 2nd checkbox in
> my real app and bound it identically. That one works, and the other
> does not. I compared e
On 4/15/09 2:58 PM, I. Savant said:
>> The problem is that clicking the checkbox, as per documentation, "cycles
>> through [the 3 states] in this order: on, off, mixed, on, and so
>> forth." But I don't want the user to be able to choose 'mixed state'.
>> I want this transition:
>
> Google "NSBu
On Wed, Apr 15, 2009 at 2:36 PM, Sean McBride wrote:
> I have a master-detail interface. NSTableView is the master; a checkbox
> is the detail. The checkbox corresponds to a boolean property of my
> model object, and is so bound. In the case of multiple selection in the
> tableview, I'd like t
On Oct 6, 2008, at 11:59 AM, I. Savant wrote:
On Mon, Oct 6, 2008 at 8:54 AM, Jamie Phelps
<[EMAIL PROTECTED]> wrote:
I'm looking for examples of well-designed Master-Detail interfaces.
I have
tried several different layouts for the details and haven't been
satisfied
with any of them.
Th
On Oct 6, 2008, at 08:54, Jamie Phelps wrote:
I was considering a "double-click for details" approach, but I'm
not sure if there's a design precedent for such a setup. I'm not
averse to doing something new, but I don't want to do something the
user is totally not expecting.
I'm not sayin
On Mon, Oct 6, 2008 at 8:54 AM, Jamie Phelps
<[EMAIL PROTECTED]> wrote:
> I'm looking for examples of well-designed Master-Detail interfaces. I have
> tried several different layouts for the details and haven't been satisfied
> with any of them.
This is almost impossible to answer usefully witho
On 23.7.2008, at 23:42, mmalc crawford wrote:
On Jul 23, 2008, at 11:51 AM, Izidor Jerebic wrote:
Hm, the docs say:
Typically, the content binding is created automatically when the
initial NSTableColumn binding is made, binding to the column's
NSArrayController.
I don't see what is inap
On Jul 23, 2008, at 11:51 AM, Izidor Jerebic wrote:
Hm, the docs say:
Typically, the content binding is created automatically when the
initial NSTableColumn binding is made, binding to the column's
NSArrayController.
I don't see what is inappropriate.
It should work, because I set it to th
On 23.7.2008, at 20:08, mmalc crawford wrote:
On Jul 23, 2008, at 9:40 AM, Izidor Jerebic wrote:
But it again confirmed that bindings are not quite what they should
be. This bug should never happen to me or should be resolved in 5
minutes: InterfaceBuilder should prevent illegal combinati
On Jul 23, 2008, at 9:40 AM, Izidor Jerebic wrote:
But it again confirmed that bindings are not quite what they should
be. This bug should never happen to me or should be resolved in 5
minutes: InterfaceBuilder should prevent illegal combinations or
there should be a debugging option that
Isn't this list great? After an hour of debugging, all you have to do
is send an email and few minutes later your problem is solved :-)
It turned out that the bug was this: I poked around master NSTableView
and it had a binding of 'content' to the same master array controller
that was als
30 matches
Mail list logo
