Bradley Smith Bradley Smith Easy editing in Form Designer Put any control that you want into the content region Apply different styles and sizes.
Community Bot 1 1 1 silver badge. Alexander Makarov Alexander Makarov 2 2 silver badges 4 4 bronze badges. Olivier Jacot-Descombes Jack Jack 1 1 silver badge 3 3 bronze badges. Location; loc. Hi-Angel Hi-Angel 4, 8 8 gold badges 54 54 silver badges 80 80 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. Context-menu control with nested, sub-menu support.
We also included UniformStackPanel control which you might find useful. We are constantly working on adding more controls based on your requests.
Please let us know what you need. We offer professional set of Windows 8 controls for developing great looking and lightning-fast professional applications. DotNetBar for WinRT controls are designed for excellent performance because we use uncluttered themes and templates, leverage the underlining platform and replace it where it is not fast enough.
When you hover your cursor over a taskbar icon, a preview will be shown , thereby enabling you to choose the correct window to navigate to. By default, the context menu will expand when your cursor hovers over it, after a short delay. Applying this tweak will enable Windows to show an expandable context menu faster or almost instantly whenever your cursor hovers over it. This allows users to view all their open windows swiftly without the need for clicking the mouse. A simple Regedit hack can also increase or shorten the delay when activating windows.
In the screenshots above, windows security has an expander for the antivirus section as well as the left navigation menu. This shows a very realistic use of the expander in more than one direction that a lot of apps would need to support.
My vote is for supporting multiple directions in V1. Could you elaborate with a screenshot or specific app where this happens so I can understand the scenario more? I'll edit the open question to have this additional context This is why I'm hoping to understand if there are specific use cases developers have for non-downward Expander!
Thanks for explaining this, it totally makes sense that disabling the state change is a desired feature for this kind of control! Would love to know any specific use cases you have for non-downward Expander! Pretty sure that expands up. JustABearOz thanks so much for bringing up these examples! For 1: I think this is an interesting edge case - the expansion is 'downwards' from the 'header' the expand button , but the control itself is positioned at the bottom of the surface so the header and the expanded content has to 'shift' upwards otherwise it would run off the screen!
Seems like a good way to handle having an expanding item at the 'bottom' of an app, do you agree? I agree with you, this is a scenario where the header is at the bottom of the area and expands up! In this case the calendar's expander and the popup as a whole is tied to the taskbar - have you encountered scenarios in apps where expanders have a similar tied positioning that necessitates upward expansion?
I don't understand why you are asking us to give examples of expand direction in real-world usage. I expect internally you have to take this to spec review and defend it to management. You are copying over an existing API in this area and need to maintain app compatiblity. Again, if this was a new idea I would understand more why we have to defend it -- it's good to make sure features are useful before investing the time in them.
Aside from the header there are literally two properties in this control and if it was C I could write it in a few hours using the WCT base. I would like to see a consistent approach to animating icons, which right now appears to be the Animated Icon proposal. I would not remove any animation from the NavigationView, as it is an entirely self contained new paradigm for WinUI - and it seems as though the intention is to add animations to all these similar controls - so maybe once it is ready, the control could be added to the NavigationView.
I understand what you meant for the expanding and collapsing animations. I believe that accordion behavior will be achieved through list-level logic rather than a new Accordion control with IsExpanded for developers to customize this to different scenarios Ex: where some Expanders close each other and others can simultaneously be expanded.
Felix-Dev - I've added the Telerik Expander to the proposal, thanks for sharing it! Glyph appearance : lightweight styling seems to be the preferred route to switch out glyphs and icon font, through having ExpanderExpandGlyph and ExpanderCollapseGlyph. Is this level of customization needed in v1 Expander? Glyph animation : including change to a different glyph upon expansion - which is partially solved with AnimatedIcon Sounds like this level of customization is not necessary for v1 Expander.
Glyph position : Is this level of customization needed in v1 Expander? This is further complicated if v1 includes ExpandDirection and the option to change glyph position.
Felix-Dev described. Hope I've correctly understood the great discussion from this weekend - let me know if I'm mistaken somewhere! Thank you all so much for your insightful thoughts on this. These could be given a lower priority if Prioritisation is needed and the core behaviour and functionality is taking too long. Thanks for the priority order mdtauk! I would imagine it would replace the content, but I think those designing the information bar should provide a design spec for a collapsible bar, which the expander designers can look at.
0コメント