C1NavBar VisualStyle Broken

Originally Posted 10 November 2016, 8:49 pm EST

  • Originally Posted 10 November 2016, 8:49 pm EST

    Hello,

    Using version 4.0.20163.212 version of C1 controls.

    C1NavBar now has an issue with the VisualStyle settings. Drop C1NavBar on a Form as in the attached sample and set the VisualStyle to Office2003Olive. Then run the project and the VisualStyle is not Office2003Olive.

    I have to set the VisualStyle manually in the Forms constructor after the call to InitializeComponents in order for the VisualStyle to show as Office2003Olive.

    There is also a warning now being generated during the project build as well as follows:

    1>C:\Users\gregg.RRM\Documents\Visual Studio 2015\Projects\C1NavBarIssue\Form1.Designer.cs(44,4,44,38): warning CS0618: 'C1NavBar.SectionHeaderHeight' is obsolete: 'Use Style instead.'


    Can you please provide a fix?

    Thank you,

    Gregg
    2016/11/C1NavBarIssue.zip
  • Reply

    Thank you Nilay.

    Do you have a time frame for when the VisualStyle will become obsolete?

    We have many, many, many... forms that all have C1CommandHolder with VisualStyle set to Office2003Olive. That is how we currently control a consistent look and feel for our applications. Working with C1ThemeController will be a major change for us. Also I do not see a Theme for Office2003... they start with Office2007 and later. That is a problem.

    I would appreciate your further input as to my concerns about Themes and would request the Office2003 Themes be made available if that is the route we have to go.

    Thank you again,
    Gregg
  • Reply

    Hi Gregg,

    Thank you for reporting this.

    I have reported this to the developer (Internal ID: 220896)

    EDIT :
    [s]Please be advised that VisualStyle would be phased out from C1 WinForms controls soon.[/s] We consider VisualStyles as an old feature and have no specific plans about them


    C1Themes are the preferred and prescribed style provider for all the C1 WinForms control. It is very easy to setup and apply. C1Themes are highly customizable. You can get started:
    http://helpcentral.componentone.com/nethelp/c1themes/QSApplyingBuiltInThemetoApp.html

    Instead of using C1NavBar.SectionHeaderHeight, please use C1NavBar1.Style.Section.Header.Height
  • Reply

    Gregg,

    I am not sure if an old theme would be available.

    At this point recreating a custom theme using C1ThemeDesigner (C:\Program Files (x86)\ComponentOne\Apps\v4.0\C1ThemeDesigner.4.exe) would be the best alternative. Let me see what other alternatives we have.

    ~nilay
  • Reply

    Hi Gregg,

    This error is expected to be fixed by v3.5 (Jan-Feb 17).

    [s]Please be advised that VisualStyle would be phased out from C1 WinForms controls soon[/s].

    Sorry what I meant here was:

    We consider VisualStyles as an old feature and have no specific plans about them.

    As of now there is no fixed date as to when visual style would be phased out. I think this would be more gradual than any fixed date. C1Themes are highly customizable, creating a new theme should not be any difficult. I would follow up on this after some research on old visual styles.

    ~nilay
  • Reply

    Nilay,

    Thank you and yes please see if and when developers would provide Office2003 Visual Styles as built-in themes. We really don't have time to be creating custom themes especially when it is a currently available feature in VisualStyles. That is why we purchase your controls so we can focus on app development.

    Also I'm not sure why you would refer to the Office2003 VisualStyles as "old" when they are currently available as built-in styles. They are certainly not "old" for us since we've been using them and continue to use them. I wouldn't think they'd be difficult to provide as built-in themes since they are available as current styles.

    I appreciate your help in this matter and look forward to hearing back.

    Thank you,

    Gregg
  • Reply

    Nilay,

    Thank you for the updated information.

    I will do some testing to see what is needed to transition our applications to using the the C1ThemeController.

    We would need at a minimum a built-in theme style of Office2003Olive to move forward though. Please advise when such a built-in theme would be available.

    Thank you,

    Gregg
  • Reply

    Hi Nilay,

    The issue of setting the VisualStyle Office2003Olive on C1NavBar in designer and staying for run-time appears to be fixed in the 217 internal build.

    Thank you for your help.

    Any help with making the Office2003... themes available for the future would be greatly appreciated.

    Thank you,
    Gregg

    Edit: Also the issue of designer adding the C1NavBar.SectionHeaderHeight code and related warning is fixed in 217 internal build as well.
  • Reply

    Gregg,

    Since we have not marked this obsolete, you could use VisualStyles in your application. However, any enhancements/fixes regarding VisualStyles would not be given preference.

    Are you using Office2003Olive only? And for Navbar only?

    ~nilay
  • Reply

    Nilay,

    We only use the Office2003Olive for VisualStyle in our applications.

    We set the VisualStyle of C1CommandHolder to Office2003Olive and I believe that controls the VisualStyle for all other C1Command components.

    Below is a list of the most common C1Command components we use in our applications.

    C1CommandHolder
    C1CommandDock
    C1MainMenu
    C1ToolBar
    C1CommandMenu
    C1Command
    C1CommandLink
    C1Command
    C1NavBar
    C1NavBarPanel

    In the screen shot below you see one of our applications which makes use of all of these components in addition to extensive use of C1Input and C1FlexGrid controls and has the VisualStyle set to Office2003Olive.

    I hope that helps and please let me know if you have further questions.

    Thank you,
    Gregg

  • Reply

    Thank you very much Nilay!
  • Reply

    Hi Gregg,

    I would update this thread reagarding migrating/moving to Themes from visual style. Meanwhile let us know if there are any issues with VisualStyles.

    Thanks,
    ~nilay
  • Marked as Answer

    Reply

    Gregg,

    This issue is fixed in our internal build. If you need you can download our internal builds from : ftp://supportftp.componentone.com/supportftp/public/nilay/C1WinForms.4_4.0.20163.217.zip

    These are not production ready, but you may use this to verify the status of your issue.

    ~nilay
  • Reply

    Hi Gregg,

    This issue is now fixed in the latest builds of C1Winforms i.e; 2/4.0.20163.226. You can update to the latest version using C1Live or can also download the builds explicitly from the links given below:
    .Net Framework 2.0: http://prerelease.componentone.com/dotnet20/c1winforms/2016-t3/C1WinForms.2_2.0.20163.226.zip
    .Net Framework 4.0: http://prerelease.componentone.com/dotnet40/c1winforms/2016-t3/C1WinForms.4_4.0.20163.226.zip

    Thanks,
    Akshay
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels