If you double-click on an IntegerUpDown when it is disabled, it will throw an InvalidOperationException stating: 'EditItem' is not allowed for this view.
Steps:
1. On an IntegerUpDown control in XAML, set IsEnabled="False" on the control.
2. Run your application in debug mode.
3. In the window that contains the control, double-click on the control. Observe the exception that is thrown.
I was using both IsEnable=false and IsReadOnly=true when I stumbled upon this bug. IsReadOnly=true allows the control to not be edited, and IsEnabled=false grays out the control. You only need to set IsEnabled=false to reproduce this bug. I believe it is a valid configuration to want the control set to read only AND have it grayed out. If it is grayed out, it tells the user it cannot be edited.
Comments: ** Comment from web user: michael_yanni **
Steps:
1. On an IntegerUpDown control in XAML, set IsEnabled="False" on the control.
2. Run your application in debug mode.
3. In the window that contains the control, double-click on the control. Observe the exception that is thrown.
I was using both IsEnable=false and IsReadOnly=true when I stumbled upon this bug. IsReadOnly=true allows the control to not be edited, and IsEnabled=false grays out the control. You only need to set IsEnabled=false to reproduce this bug. I believe it is a valid configuration to want the control set to read only AND have it grayed out. If it is grayed out, it tells the user it cannot be edited.
Comments: ** Comment from web user: michael_yanni **
Hmm. It seems I may be mistaken. I continued to test this after I submitted this bug, and found that inbetween my controls if I double click, or double click on any disabled controls, this exception occurs.
Further investigation reveals that the problem is caused because I have the controls on a DataGrid. My bad. You can delete this bug. Some more information can be found here: http://stackoverflow.com/a/5183104/1824821