Re: Menu validation in Panther
Re: Menu validation in Panther
- Subject: Re: Menu validation in Panther
- From: Christopher Holland <email@hidden>
- Date: Sat, 4 Oct 2003 01:19:57 -0500
I realize this. I certainly wasn't talking about ANYthing that could be
giving away any sort of "trade secrets." If I thought it did then I
would not have posted. I tried to make the description as vague as
possible without losing my meaning. But, I stated quite clearly that I
thought it was probably a misunderstanding that I had with the previous
or current documentation.
I don't think it is a bug, I am just wanting to learn if there was a
reason that the API was changed (if it even was) because I personally
am interested in things like API design. There are plenty of people on
this list, you included, that could probably guess as to why an API
would be altered to include the change listed and I wanted the input
.... which apparently is not as much fun as what I got.
It was a question meant to learn something from. Nothing else.
Like I said, my code is working and I don't feel like it is a bug ...
just interested in the thoughts behind the change for my own curiosity
and future knowledge. Was I misinterpreting the docs before? Or was I
using a bug to my advantage without knowing it (which would be nice to
know so that I can NOT do that in the future)? Should I have known
better? Additionally, how am I to know that it IS a bug and not just a
"fix" from the previous API? Others may be more knowledgeable and be
able to tell. Etc. etc. etc.
I would love to have been able to ask this question somewhere where
somebody wouldn't freak out...but there is no place like that. I didn't
see it as a bug...but something that was probably a "fix" from the
previous API. This happened to break something that I had done and
others may want to look for the same thing in their code.
Even people who pay for the seeds (which I do) have questions that the
group can answer...and I don't want to waste one of my tech calls on
something so inane when I may need it for something more important
later. It was a basic question that had only the slightest bit to do
with Panther, per se, and more to do with API design.
CH
On Oct 3, 2003, at 6:38 PM, j o a r wrote:
How did you come to the conclusion that the fact that there isn't a
private mailing list list for those seeded with Panther gives you the
right to talk about Panther on this list?
If you're seeded and find something that you find weird, file a bug.
One of the reasons that Apple doesn't want us to talk about Panther
before it's done is that they don't want people running around like
headless chicken, worrying about the things that doesn't work yet,
creating negative expectations and negative press - it's not released
yet, because it's not done yet! If everything worked perfectly you
would be able to buy Panther by now...
j o a r
On 2003-10-04, at 00.13, Christopher Holland wrote:
Sorry if I am talking about Panther but I don't really know of a
better list to do it (there isn't an NDA list that I know of).
Anyway, I have noticed a change in the way that Panther handles
menu/submenu validation as compared to previous releases of the
system. I wouldn't call this a bug....just a change.
Previously, if you had an NSMenuItem that had a submenu attached to
it then it didn't have to have an action. 'nil' would suffice. In
Panther, you must give the "parent" menuItem a valid action before it
will validate....regardless of what your validator object tells it.
Shouldn't this be considered wrong? Isn't that the whole idea behind
validators is that they are the ones that do the validation. I
haven't found a spot in the docs that says that an item has to have a
valid action...just that the validator must exist and answer calls to
it.
I'm probably missing something here, of course...that's usually the
case.
This isn't a big deal for me, I've already fixed the code, but it
could be a problem in someone else's case.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.