RadConfirm Accept/Cancel buttons disabled since 2013 Q1 SP1

[Daní]

Hi,

I recently upgrade from 2012 Q2 SP1 version to current version (2013 Q1 SP1). After the upgrade, RadConfirm Accept/Cancel buttons appear disabled whenever a dialog is shown.

Does anybody faced this same issue and can share a workaround? It's a bit urgent as Test Team may not perform their tasks...

Thanks

[Daní]

Hi,

It seems that this behavior is extended to other controls. RadDataPager is also affected: forward buttons are disabled.

[George]

Hello Daní,

 
We are not aware of such problem with RadControls. Can you give us some more information about which assemblies are used? Do you use xamlless or xamlful assemblies?

All the best,
George
the Telerik team

[Daní]

I'm using xamlful? (classic way) controls. Current dlls version is 2013.1.103.1050. I'm using Windows 7 Theme

Thnks

[Daní]

Hi,

Any progress in this issue? It's a bit urgent as I have to decide to downgrade (once more, we already rollback an upgrade due to a weird issue with screen tips image sizes) to 2012 Q2 SP1 in short.

[George]

Hi Daní,

As I noted in the previous post, we are not aware of such issue with RadControls. Can you reproduce the issue in a sample project? This will definitely help us in pinpointing the problem. Please, note that if the RadButton.Command property is bound to a command, and the command cannot be executed, the buttons will be disabled. 

I am glad to assist you further.

All the best,
George
the Telerik team

[Daní]

Hi George,

I think I know what's happening with RadAlert, RadConfirm,... buttons in my app.

You can find the origin at this forum thread: Command.CanExecute() on RadButton inside RadBusyIndicator causes unexpected (wrong) behavior on RadButton.IsEnabled property

So, sometime ago, one of telerik's modification caused, sometimes, unexpected behavior in button's IsEnabled property. Sometimes, buttons with Command property set were enabled although the CanExecute command method returns false.

As you can observe in the thread, I created a custom behavior that was applied by default to all RadButtons and RadRibbonButtons in the application.

I think this behavior is causing that RadConfirm, RadAlert,... buttons appears disable. Probably you have modified the behavior of the IsEnabled property for buttons and now my behavior is invalidated.

So, can you confirm that actually IsEnabled property behaves as expected and that I can safely remove my custom behavior?

Thanks

[George]

Hi Dani,

We can confirm that this problem is fixed. Could you please give it a try and let us know if you continue experience any issues with RadControls.

Greetings,
George
the Telerik team