If I were you, the first thing I’d do is put what you have (your pre-work and
any backups) in a repository so you can track your history. Xcode has made
integration with Git so easy. There are definitely some shortcomings with more
esoteric needs, but for the most part, you’d be fine sticking
On 14.02.2017 at 23:15 Graham Cox wrote:
> It’s usually easier to float downstream.
+1 for nice metaphor.
On the good news side: I've fixed it now. The trick was to first fix the
spurious menu
trees directly in the XML, then to delete keyedobjects.nib, then to make a
dummy change
directly in
On 14 Feb 2017, at 22:15, Graham Cox wrote:
>
>> On 15 Feb 2017, at 12:39 AM, Andreas Falkenhahn
>> wrote:
>>
>> I knew how to use IB on the old PowerPC Mac,
>> but that was 10 years ago.
>
> Well, it hasn’t changed that much in principle. In
> On 15 Feb 2017, at 12:39 AM, Andreas Falkenhahn
> wrote:
>
> I knew how to use IB on the old PowerPC Mac,
> but that was 10 years ago.
Well, it hasn’t changed that much in principle. In fact it’s got a lot better
in most respects because it stays in sync with your
On 14.02.2017 at 15:02 じょいすじょん wrote:
>> On Feb 14, 2017, at 1:58, Andreas Falkenhahn wrote:
>> On 13.02.2017 at 17:33 じょいすじょん wrote:
>>> Yeah, my first suggestion didn't work, but points out the problem overall
>>> in you nib.
>>> Looks like somebody did try to edit
> On Feb 14, 2017, at 1:58, Andreas Falkenhahn wrote:
>
> On 13.02.2017 at 17:33 じょいすじょん wrote:
>
>> Yeah, my first suggestion didn't work, but points out the problem overall in
>> you nib.
>> Looks like somebody did try to edit the xml before and munged it.
>
> I
On 13.02.2017 at 23:13 Graham Cox wrote:
> The problem here is that you seem unwilling to take a little time
> to learn the basics of Interface Builder.
No, that's not the problem here. I knew how to use IB on the old PowerPC Mac,
but that was 10 years ago. Now I'm trying to compile this old
> On 14 Feb 2017, at 3:58 AM, Andreas Falkenhahn wrote:
>
> This annoying issue is just another reason why I prefer doing things in code.
> This has already cost me hours over hours and it's still not solved.
> True, I can see that. But how do I rewire my nib? I don't
Well, you may have a valid bug to report to Apple. You probably would want to
use a tech support incident, which will get feedback faster, and in the past,
when the issue turned out to be Apple’s bug, they’ve credited it back to me.
Otherwise, definitely mark this as a serious bug.
--
Gary L.
On 13.02.2017 at 19:49 Gary L. Wade wrote:
> Your assignments for the File’s Owner and Application objects are
> messed up. First, clear the custom class values for these two
> objects. After that, connect the delegate outlet in the Application
> object to your embedded AppDelegate object.
Your assignments for the File’s Owner and Application objects are messed up.
First, clear the custom class values for these two objects. After that,
connect the delegate outlet in the Application object to your embedded
AppDelegate object.
--
Gary L. Wade
http://www.garywade.com/
On 13.02.2017 at 18:16 Gary L. Wade wrote:
> I haven't looked at your NIB, but I've seen something of what's
> described with errant choices of diff tools and source code merging,
That certainly can't be the case since I'm not using any diff or
merging tools. It's also just a single developer
I haven't looked at your NIB, but I've seen something of what's described with
errant choices of diff tools and source code merging, usually when a user just
accepts a merge without eyeballing it. If you've got a history of your
revisions, you should find where things changed badly. Also, if
On 13.02.2017 at 17:33 じょいすじょん wrote:
> Yeah, my first suggestion didn't work, but points out the problem overall in
> you nib.
> Looks like somebody did try to edit the xml before and munged it.
I certainly did not mess with the XML! Xcode must have messed this up when
converting
the nib file
Consider getting an old PowerPC Mac, run your app as a blueprint and
rebuild a new interface in the current Xcode. That will likely be
faster than hacking away at your current nib, and a bit of fun as
well. Take it one window at a time so you understand what is happening.
That is how we
Yeah, my first suggestion didn't work, but points out the problem overall in
you nib.
Looks like somebody did try to edit the xml before and munged it.
You also have nested menu duplicates inside your menus in the nib file itself!
MainMenu
Hollywood
Menu
On 13.02.2017 at 16:40 じょいすじょん wrote:
> You have a lot of dupes in your nib file connections.
> For example, select the AppDelegate in the nib in IB, and look at the
> Connections Inspector.
> You'll see it has 2 Main Menu referencing outlets.
> So it's hitting a random one of the two.
> You
On 13.02.2017 at 16:34 Steve Mills wrote:
> I've dinked around with it a bit more and ended up replacing
> MainMenu.nib with a new MainMenu.xib. That fixes it. I'm on an older
> Xcode now, so I can't open your MainMenu.nib, so I opened its
> designable.nib with a text editor to see if there's
You have a lot of dupes in your nib file connections.
For example, select the AppDelegate in the nib in IB, and look at the
Connections Inspector.
You'll see it has 2 Main Menu referencing outlets.
So it's hitting a random one of the two.
You have this kind of duplication in lots of places in
On Feb 13, 2017, at 08:50 AM, Steve Mills wrote:
On Feb 13, 2017, at 08:12:59, Andreas Falkenhahn wrote:
Unfortunately, I don't know where to look because I remember nothing about
Interface Builder. That's why I have uploaded a VERY SMALL test project
On Feb 13, 2017, at 08:12:59, Andreas Falkenhahn wrote:
>
> Unfortunately, I don't know where to look because I remember nothing about
> Interface Builder. That's why I have uploaded a VERY SMALL test project
> here: http://www.falkenhahn.com/tmp/guitest.tar.gz
Same
On 12.02.2017 at 21:49 Kyle Sluder wrote:
> There are plenty of ways to write refcounting bugs. But the
> refcounting bug is just a theory. All we know for sure is that
> something is disabling the menu items. I assume you have not turned
> off the default autoenablesItems property on the menu,
Have you tried printing the responder chain when this happens? But as others
have said, funnelling all menu choices through a menuClick: method sounds
backwards.
On 12 Feb 2017, at 18:01, Andreas Falkenhahn wrote:
> I'm experiencing a strange issue with my app.
Another possibility is that the target (app delegate) overrides
-validateMenuItem: and isn’t doing the right thing.
—Graham
> On 13 Feb 2017, at 7:55 AM, Kyle Sluder wrote:
>
>>>
>>> On Feb 12, 2017, at 12:36 PM, Andreas Falkenhahn
>>> wrote:
>> On Feb 12, 2017, at 12:36 PM, Andreas Falkenhahn
>> wrote:
>
>
>> On 12.02.2017 at 21:29 Kyle Sluder wrote:
>>
>> You’ve wired up every single menu item to a single action in your app
>> delegate? That’s certainly non-standard.
>
> It's really old code. It's an
On 12.02.2017 at 21:29 Kyle Sluder wrote:
> You’ve wired up every single menu item to a single action in your app
> delegate? That’s certainly non-standard.
It's really old code. It's an Xcode project I originally created on a
PowerPC Mac some 10 years ago, so I don't really remember how I used
On 12.02.2017 at 20:44 Alexander Reichstadt wrote:
> Do you subclass NSApplication or alter the responder chain?
No, not doing any of that.
--
Best regards,
Andreas Falkenhahnmailto:andr...@falkenhahn.com
___
Cocoa-dev
On Sun, Feb 12, 2017, at 11:01 AM, Andreas Falkenhahn wrote:
> I'm experiencing a strange issue with my app. Sometimes, maybe in 1 out
> of 10
> programs starts, all menus of my app are grayed out, including standard
> menus
> like "Services", "Hide XXX", "Hide Others", "Show All", "Minimize",
>
On 12.02.2017 at 19:21 Ken Thomases wrote:
> On Feb 12, 2017, at 11:01 AM, Andreas Falkenhahn
> wrote:
>> I'm experiencing a strange issue with my app. Sometimes, maybe in 1 out of 10
>> programs starts, all menus of my app are grayed out, including standard menus
>>
On Feb 12, 2017, at 11:01 AM, Andreas Falkenhahn wrote:
>
> I'm experiencing a strange issue with my app. Sometimes, maybe in 1 out of 10
> programs starts, all menus of my app are grayed out, including standard menus
> like "Services", "Hide XXX", "Hide Others", "Show
I'm experiencing a strange issue with my app. Sometimes, maybe in 1 out of 10
programs starts, all menus of my app are grayed out, including standard menus
like "Services", "Hide XXX", "Hide Others", "Show All", "Minimize", "Zoom",
"Bring All To Front", really everything is grayed out right after
31 matches
Mail list logo