In Visual Studio there seem to be two types of groups of panes:
1. one set that are inside a permanent panel set unchangeably to Group, and
2. one outer set that behave pretty much like netadvantage DockManager set to LayeredWindowWithIndicators.
How can I get that inner group behavior?
Hello Kenneth,
To be honest, I do not understand your requirement. Could you please explain more deeply your final goals and if it is possible please give us concrete example with VisualStudio and / or screenshot.
Let me know if you have any questions.
Regards
OK, here comes the full explanation :)
This is what Visual Studio looks like. Note the docked panes surround an empty area.
This area is not just empty, it is a "permanent" area. (01_visualstudio_permanant_area.png)
...but when I now try to drag the pane within this area, I get the standard ugly pulsing frame and you never know where to put your mouse to get it to dock where you need it.
Also, sometimes when you drop, you get a popup menu. My client will not accept one type of behavior when dragging in, and a totally different behavior when dragging out.
I tried setting DragWindowStyle.LayeredWindowWithIndicators, but the MDI manager does not have one.
So there it is. I need some way of creating a permanent area for the docking manager, which also behaves like it is part of the docking manager.
Oh, forgot: we are using version 10.2
Thanks for attached screenshots. Please take a look on attached sample and video file with one possible solution. If you have any questions, feel free to write me
Here is the sample
Haha! That video is funny!
Yes, if you right-click and select FLOAT and you do it quickly, then nobody notices.
But if the entire paradigm is already based on DRAG 'N' DROP, suddenly having to resort to pop-up menus is not cool.
Try this: Drag a second pane into the middle area.
Now try drag that pane. See what happens? You get a weird wobbly frame instead of the docking rose.
I hope you will agree with me that this is a conceptual break and is not acceptable.
Isn't it a priority at Infragistics to insure consistent behavior over all components?
I have found some freeware components that do this correctly. I have decided to use those.
You can suggest new product ideas for future versions (or vote for existing ones) at <http://ideas.infragistics.com>.
There are many benefits to submitting an product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
1. Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
2. Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
3. Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
Yes I looked at the source code, compiled and ran it and it behaves just as in the video. Why should it be any different?
I have spent over a week on this, so I know these two controls reasonably well.
As I have been trying to point out throughout this thread:
UltraDockManager supports DragWindowStyle.LayeredWindowWithIndicators,
UltraTabbedMdiManager does ***NOT*** support LayeredWindowWithIndicators.
And this seems to still be the case in version 13 (otherwise your supplied source code would have implemented it?)
I do not intend implementing the LayeredWindowWithIndicators behavior in UltraTabbedMdiManager.
I think the decision makers at Infragistics must sit down and discuss this. Components should have the same look and feel. That is the least we as a purchaser of this components library should expect.
Thank you very much for your feedback. Did you have a time to take a look in the source code of attached sample ? There are two different controls - UltraDockManager and UltraTabbedMdiManager that implement required behavior and if you don`t like "FLOAT" approach from context menu, please feel free to modify it per your requirement. Also please note that product lifecycle of your version 10.2 is expired. More details you could find at: http://es.infragistics.com/help/product-lifecycle/
Feel free to write me if you have any further questions.