Problem with upgrade from 2.5.1 to 4.1.6

[ChrisChambers]

Hi chaps,

I recently upgraded from 2.5.1 to 4.1.6 but since then I'm able to select the disabled tabs in my navigators. How is that possible? Are these bugs with 4.1.6 or am I dong something wrong? Is it just too big a leap from 2.5.1 to 4.1.6? Perhaps I should just cut my losses and redraw the navigator?

Cheers,

Chris Chambers.

[Chris Porter]

It has been a while since I've worked with the Navigator but I don't believe disabling a KryptonPage is how you prevent it from being selected. You need to capture the KryptonNavigator.SelectedIndexChanging event (or something like that), determine if the user should be able to see the page they clicked and return Cancel = true if you don't want them to be able to see it.

[ChrisChambers]

Hi Chris,

Thanks for your response.

That seems pretty bizarre to me. Why would that be required? If I set a page to be disabled then surely nobody should be able to click on it? All I'll end up doing in the SelectedIndexChanged event handler would be setting e.Cancel = !page.Enabled. Pointless.

Is there anybody that can elaborate on this?

Cheers,

Chris Chambers.

[Chris Porter]

My guess is that Phil saw a difference between the page being disabled (shadowed out and in read only mode) and not being able to select it. I could also make a case for wanting my code to check the true state of an external condition before allowing/preventing a user from selecting a tab.

[ChrisChambers]

OK Chris, thanks for your time and input.

Regards,

Chris Chambers.