Re: Stopping actions mid stream

2008-07-07 Thread Jeff Brown
Thanks everyone.
I ended up just disabling the option in the end.

Cheers
Jeff


Thanks Andy and Jean-Daniel.

Peter


On 07/07/2008, at 3:34 AM, Andy Lee wrote:

Yes:

http://ignorethecode.net/blog/2008/07/01/disabling-inactive-menu-items/ 

(by way of DaringFireball)

--Andy

On Jul 6, 2008, at 11:57 AM, Jean-Daniel Dupas wrote:

I haven't test but -[NSMenuItem setToolTip:] look fine to do this.
Now, just chek if this methods works even when the item is disabled.

Le 6 juil. 08 à 16:31, Peter Zegelin a écrit :

Some of the commenters suggest a tool tip over the disabled menu explaining why 
it is disabled, which sounds reasonable. As a newby here would this be easy to 
implement in Cocoa?


snip

___




  Start at the new Yahoo!7 for a better online experience. www.yahoo7.com.au
___

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 [EMAIL PROTECTED]


Stopping actions mid stream

2008-07-06 Thread Jeff Brown
Hi Guys

I've set up matrix with 2 radio buttons (1 and 2) with a delegate method that 
gets run when the matrix gets clicked. Lets say radio button 1 is highlighted 
and someone clicks on radio button 2. The delegate method has some code that 
checks whether the radio buttons are allowed to be changed from 1 to 2 and if 
not, sends an alert to the user. 
My problem is how can I stop the radio buttons themselves changing from 1 to 2. 
When programming in Visual Basic there was a method that stopped the action 
from completing. Is there something similar I can do here or some other way.

Thanks in advance.
Jeff


  Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/mail
___

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 [EMAIL PROTECTED]


Re: Stopping actions mid stream

2008-07-06 Thread Jaime Magiera


On Jul 6, 2008, at 3:04 AM, Jeff Brown wrote:

 The delegate method has some code that checks whether the radio  
buttons are allowed to be changed from 1 to 2 and if not, sends an  
alert to the user.
My problem is how can I stop the radio buttons themselves changing  
from 1 to 2. When programming in Visual Basic there was a method  
that stopped the action from completing. Is there something similar  
I can do here or some other way.



Hi,

I don't have an answer to your question, but an observation: Giving a  
user the option to click something, then telling them they cannot,  
seems kind of weird. Radio buttons are generally for options a user  
has. If the functionality denoted by an item is unavailable, generally  
it is hidden or at the very least inactive. In other words, using  
logic to determine availability of an interface item before it is  
clicked. Such a thing can be done with bindings.


anyway, good luck finding the answer to your question.

Jaime


Jaime Magiera

Sensory Research
http://www.sensoryresearch.net

___

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 [EMAIL PROTECTED]


Re: Stopping actions mid stream

2008-07-06 Thread Graham Cox
The preferred way to do this is to prevent the user clicking the  
button if it's not appropriate by greying it out.


This is far more user-friendly than rebuking a user for having the  
audacity to click your button when they shouldn't have, even though  
they had no visual cue that they shouldn't. The permit then rebuke  
form of input validation is the hallmark of bad UI design. Sadly, it's  
all too common.



G.


On 6 Jul 2008, at 5:04 pm, Jeff Brown wrote:

I've set up matrix with 2 radio buttons (1 and 2) with a delegate  
method that gets run when the matrix gets clicked. Lets say radio  
button 1 is highlighted and someone clicks on radio button 2. The  
delegate method has some code that checks whether the radio buttons  
are allowed to be changed from 1 to 2 and if not, sends an alert to  
the user.
My problem is how can I stop the radio buttons themselves changing  
from 1 to 2. When programming in Visual Basic there was a method  
that stopped the action from completing. Is there something similar  
I can do here or some other way.


___

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 [EMAIL PROTECTED]


Re: Stopping actions mid stream

2008-07-06 Thread Peter Zegelin
I agree with you but here is JoelOnSoftware saying virtually the  
complete opposite. http://www.joelonsoftware.com/items/ 
2008/07/01.html. Fortunately most of his commenters disagree.



On 06/07/2008, at 10:21 PM, Graham Cox wrote:

The preferred way to do this is to prevent the user clicking the  
button if it's not appropriate by greying it out.


This is far more user-friendly than rebuking a user for having the  
audacity to click your button when they shouldn't have, even though  
they had no visual cue that they shouldn't. The permit then rebuke  
form of input validation is the hallmark of bad UI design. Sadly,  
it's all too common.



G.


On 6 Jul 2008, at 5:04 pm, Jeff Brown wrote:

I've set up matrix with 2 radio buttons (1 and 2) with a delegate  
method that gets run when the matrix gets clicked. Lets say radio  
button 1 is highlighted and someone clicks on radio button 2. The  
delegate method has some code that checks whether the radio buttons  
are allowed to be changed from 1 to 2 and if not, sends an alert to  
the user.
My problem is how can I stop the radio buttons themselves changing  
from 1 to 2. When programming in Visual Basic there was a method  
that stopped the action from completing. Is there something similar  
I can do here or some other way.


___

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/peter%40fracturedsoftware.com

This email sent to [EMAIL PROTECTED]


___

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 [EMAIL PROTECTED]


Re: Stopping actions mid stream

2008-07-06 Thread Jean-Daniel Dupas

Not only his commenters disagree.

http://daringfireball.net/linked/2008/07/01/spolsky-menu-items
http://www.red-sweater.com/blog/515/disabled-menus-are-usable

And I disagree too.


Le 6 juil. 08 à 15:41, Peter Zegelin a écrit :

I agree with you but here is JoelOnSoftware saying virtually the  
complete opposite. http://www.joelonsoftware.com/items/ 
2008/07/01.html. Fortunately most of his commenters disagree.



On 06/07/2008, at 10:21 PM, Graham Cox wrote:

The preferred way to do this is to prevent the user clicking the  
button if it's not appropriate by greying it out.


This is far more user-friendly than rebuking a user for having the  
audacity to click your button when they shouldn't have, even though  
they had no visual cue that they shouldn't. The permit then  
rebuke form of input validation is the hallmark of bad UI design.  
Sadly, it's all too common.



G.


On 6 Jul 2008, at 5:04 pm, Jeff Brown wrote:

I've set up matrix with 2 radio buttons (1 and 2) with a delegate  
method that gets run when the matrix gets clicked. Lets say radio  
button 1 is highlighted and someone clicks on radio button 2. The  
delegate method has some code that checks whether the radio  
buttons are allowed to be changed from 1 to 2 and if not, sends an  
alert to the user.
My problem is how can I stop the radio buttons themselves changing  
from 1 to 2. When programming in Visual Basic there was a method  
that stopped the action from completing. Is there something  
similar I can do here or some other way.


___

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/peter%40fracturedsoftware.com

This email sent to [EMAIL PROTECTED]


___

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/devlists%40shadowlab.org

This email sent to [EMAIL PROTECTED]





smime.p7s
Description: S/MIME cryptographic signature
___

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 [EMAIL PROTECTED]

Re: Stopping actions mid stream

2008-07-06 Thread Graham Cox
Wow, I'm really surprised that Joel Spolsky of all people would say  
this - and so recently too.


I used to like System 7's Balloon Help approach - grey out the menu  
but the help balloon would explain why it wasn't available (at least  
in an app that took the trouble to implement this). Sadly, as with  
many things since hen, in some ways we've gone backwards.


G.


On 6 Jul 2008, at 11:41 pm, Peter Zegelin wrote:

I agree with you but here is JoelOnSoftware saying virtually the  
complete opposite. http://www.joelonsoftware.com/items/ 
2008/07/01.html. Fortunately most of his commenters disagree.



On 06/07/2008, at 10:21 PM, Graham Cox wrote:

The preferred way to do this is to prevent the user clicking the  
button if it's not appropriate by greying it out.


This is far more user-friendly than rebuking a user for having the  
audacity to click your button when they shouldn't have, even though  
they had no visual cue that they shouldn't. The permit then  
rebuke form of input validation is the hallmark of bad UI design.  
Sadly, it's all too common.



G.


On 6 Jul 2008, at 5:04 pm, Jeff Brown wrote:

I've set up matrix with 2 radio buttons (1 and 2) with a delegate  
method that gets run when the matrix gets clicked. Lets say radio  
button 1 is highlighted and someone clicks on radio button 2. The  
delegate method has some code that checks whether the radio  
buttons are allowed to be changed from 1 to 2 and if not, sends an  
alert to the user.
My problem is how can I stop the radio buttons themselves changing  
from 1 to 2. When programming in Visual Basic there was a method  
that stopped the action from completing. Is there something  
similar I can do here or some other way.


___

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/peter%40fracturedsoftware.com

This email sent to [EMAIL PROTECTED]


___

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/graham.cox%40bigpond.com

This email sent to [EMAIL PROTECTED]


___

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 [EMAIL PROTECTED]


Re: Stopping actions mid stream

2008-07-06 Thread Peter Zegelin
Some of the commenters suggest a tool tip over the disabled menu  
explaining why it is disabled, which sounds reasonable. As a newby  
here would this be easy to implement in Cocoa?



On 07/07/2008, at 12:02 AM, Graham Cox wrote:

Wow, I'm really surprised that Joel Spolsky of all people would say  
this - and so recently too.


I used to like System 7's Balloon Help approach - grey out the menu  
but the help balloon would explain why it wasn't available (at least  
in an app that took the trouble to implement this). Sadly, as with  
many things since hen, in some ways we've gone backwards.


G.


On 6 Jul 2008, at 11:41 pm, Peter Zegelin wrote:

I agree with you but here is JoelOnSoftware saying virtually the  
complete opposite. http://www.joelonsoftware.com/items/2008/07/01.html 
. Fortunately most of his commenters disagree.



On 06/07/2008, at 10:21 PM, Graham Cox wrote:

The preferred way to do this is to prevent the user clicking the  
button if it's not appropriate by greying it out.


This is far more user-friendly than rebuking a user for having the  
audacity to click your button when they shouldn't have, even  
though they had no visual cue that they shouldn't. The permit  
then rebuke form of input validation is the hallmark of bad UI  
design. Sadly, it's all too common.



___

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 [EMAIL PROTECTED]


Re: Stopping actions mid stream

2008-07-06 Thread Jean-Daniel Dupas

I haven't test but -[NSMenuItem setToolTip:] look fine to do this.
Now, just chek if this methods works even when the item is disabled.

Le 6 juil. 08 à 16:31, Peter Zegelin a écrit :

Some of the commenters suggest a tool tip over the disabled menu  
explaining why it is disabled, which sounds reasonable. As a newby  
here would this be easy to implement in Cocoa?



On 07/07/2008, at 12:02 AM, Graham Cox wrote:

Wow, I'm really surprised that Joel Spolsky of all people would say  
this - and so recently too.


I used to like System 7's Balloon Help approach - grey out the menu  
but the help balloon would explain why it wasn't available (at  
least in an app that took the trouble to implement this). Sadly, as  
with many things since hen, in some ways we've gone backwards.


G.


On 6 Jul 2008, at 11:41 pm, Peter Zegelin wrote:

I agree with you but here is JoelOnSoftware saying virtually the  
complete opposite. http://www.joelonsoftware.com/items/2008/07/01.html 
. Fortunately most of his commenters disagree.



On 06/07/2008, at 10:21 PM, Graham Cox wrote:

The preferred way to do this is to prevent the user clicking the  
button if it's not appropriate by greying it out.


This is far more user-friendly than rebuking a user for having  
the audacity to click your button when they shouldn't have, even  
though they had no visual cue that they shouldn't. The permit  
then rebuke form of input validation is the hallmark of bad UI  
design. Sadly, it's all too common.



___

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/devlists%40shadowlab.org

This email sent to [EMAIL PROTECTED]





smime.p7s
Description: S/MIME cryptographic signature
___

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 [EMAIL PROTECTED]

Re: Stopping actions mid stream

2008-07-06 Thread Andy Lee

Yes:

http://ignorethecode.net/blog/2008/07/01/disabling-inactive-menu- 
items/


(by way of DaringFireball)

--Andy

On Jul 6, 2008, at 11:57 AM, Jean-Daniel Dupas wrote:


I haven't test but -[NSMenuItem setToolTip:] look fine to do this.
Now, just chek if this methods works even when the item is disabled.

Le 6 juil. 08 à 16:31, Peter Zegelin a écrit :

Some of the commenters suggest a tool tip over the disabled menu  
explaining why it is disabled, which sounds reasonable. As a newby  
here would this be easy to implement in Cocoa?



On 07/07/2008, at 12:02 AM, Graham Cox wrote:

Wow, I'm really surprised that Joel Spolsky of all people would  
say this - and so recently too.


I used to like System 7's Balloon Help approach - grey out the  
menu but the help balloon would explain why it wasn't available  
(at least in an app that took the trouble to implement this).  
Sadly, as with many things since hen, in some ways we've gone  
backwards.


G.


On 6 Jul 2008, at 11:41 pm, Peter Zegelin wrote:

I agree with you but here is JoelOnSoftware saying virtually the  
complete opposite. http://www.joelonsoftware.com/items/2008/07/01.html 
. Fortunately most of his commenters disagree.



On 06/07/2008, at 10:21 PM, Graham Cox wrote:

The preferred way to do this is to prevent the user clicking the  
button if it's not appropriate by greying it out.


This is far more user-friendly than rebuking a user for having  
the audacity to click your button when they shouldn't have, even  
though they had no visual cue that they shouldn't. The permit  
then rebuke form of input validation is the hallmark of bad UI  
design. Sadly, it's all too common.



___

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 [EMAIL PROTECTED]


Re: Stopping actions mid stream

2008-07-06 Thread Peter Zegelin

Thanks Andy and Jean-Daniel.

Peter


On 07/07/2008, at 3:34 AM, Andy Lee wrote:


Yes:

http://ignorethecode.net/blog/2008/07/01/disabling-inactive-menu-items/ 



(by way of DaringFireball)

--Andy

On Jul 6, 2008, at 11:57 AM, Jean-Daniel Dupas wrote:


I haven't test but -[NSMenuItem setToolTip:] look fine to do this.
Now, just chek if this methods works even when the item is disabled.

Le 6 juil. 08 à 16:31, Peter Zegelin a écrit :

Some of the commenters suggest a tool tip over the disabled menu  
explaining why it is disabled, which sounds reasonable. As a newby  
here would this be easy to implement in Cocoa?




snip

___

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 [EMAIL PROTECTED]