To reproduce:
In the preview the PageTitle of the wizard page is visible. Run the project and the PageTitle isn't visible anymore. The color of the PageTitle background is also not correct. I think there is a problem with the resources.
Create a .NET 5 project and add a RadWizard. You can't navigate the pages to place controls on any page other than page 1.
Workaround: in the Designer.cs InitializeComponents method you can set the Selected page and rebuild the project:
this.radWizard1.SelectedPage = wizardPage1;
If you focus the first text box and press Tab key, the expected behavior is that the second text box is focused. However, pressing Tab key will navigate through the next/previous buttons. If you add a second control on the form along with the UserControl that hosts the wizard, the Tab key will behave as expected and you can navigate through the controls in the wizard page.
Steps to reproduce: 1.Create new WinForms project. 2.Place a RadWizard on Form1. 3.Select the WelcomePage and assign a WelcomeImage 4.Save the changes and close Form1. 5.Reopen Form1, you get an exception, see attached screen shot
To reproduce: 1. Add a RadWizard to an empty form 2. Add the Windows 8 Theme 3. Change the RadWizard component to Aero 4. Apply the Windows 8 Theme to the wizard control. 5. Run the project. Workaround: this.radWizard1.WelcomeImageElement.Margin = new Padding(0, 0, 0, -5);
Add ability to localize the page header and title in RadWizard`s localization provider. Currently you can localize only the text of the buttons. The Title and the Header properties of wizard pages don't have the Localizable attribute.
To reproduce: - Add RadWizard to a form. - Set the AcceptButton property like this: this.AcceptButton = this.radWizard1.NextButton; - You will notice that nothing happens when the enter key is pressed. Workaround: - Use the following PreviewKeyDown event handler: void radWizard1_PreviewKeyDown(object sender, PreviewKeyDownEventArgs e) { if (e.KeyCode == Keys.Enter) { this.radWizard1.NextButton.PerformClick(); } }
To reproduce: Add a RadWizard to a form, add a coded ui project, add a test, try to access the buttons.
FIX. RadWizard - the hover and pressed styles for the focused button in the Windows7 theme are missing
A state for RadWizard should be added to its styling mechanism that tells whether the form on which the RadWizard instance is place is active or inactive. This will allow for changing the colors of the top area of RadWizard, so that it behaves the same way as a standard wizard dialog.
RadWizard cannot show a second completion page at design-time.
The RadWizard control should handle the Tab key to navigate through all controls on its page and its command buttons.
The layout of the control's CommandArea is not correct when RadWizard is use in a MDI child form.
The layout of RadWizard CommandArea is incorrect after minimizing and restoring the form containing the control.
The RadWizard control should handle the Tab key to navigate through its command buttons.
IMPROVE. RadWizard - setting the Visibility property for the CancelButton on the control should affect all pages, not just the current one