Replied 3 August 2017, 3:52 pm EST
Andrew - Thanks for your work around. I have a similar workaround but (like yours) it requires a lot of ugly code and I have many subtle glitches here and there.
Amit - Thanks for your suggestions as well. I'm downloading the new build and will try your sample to see if I can get ideas on what my problem might be.
My current problem with my work around is that the panels inside the PivotView are moved where they need to be, but the hosting container (inside the PivotView) is not sizing correctly. It's a bug that I need to fix, but is proving to be very tricky for me.
This leads me to my next question: I would like to ask if GrapeCity plans to allow the PivotView to accept percentages or pixels for width and height on the client? The DD.PivotView.SetSize() has it's own set of problems (as I've described above). It requires hooking into jQuery events to size the control and then requires a certain level of expertise. It is a very complex, but necessary process for anybody that needs the control to size with the window. In my particular work around, I've added a lot of (what I feel is) unnecessary code that navigates through hard coded class names and div id's within the PivotView to do a simple thing (ie. resize).
This is very important to my application, as my solution uses multiple PivotView instances on a single dashboard. I'm currently using James' approach with iFrame to get around the problem. However, this too presents it's own problems since the PivotView is now moved to another page and I don't have direct access to it and it's properties. I'm now forced to set connections and load layouts on the PivotView using url parameters. All of this extra work I'm doing is simply to get around a resize issue.
Thanks for your great support!