Bill, I'd recommend first investigating which Components you are likely to want to embed in a ScalePane and seeing if they fail in some way. I am pretty sure that there are ways to work around the tooltip placement, but that won't count for much if the Components themselves aren't useable, so I don't want to waste your time digging into an example app from an old thread.
The idea I had (and which I have not yet had time to check out) would take advantage of the fact that Pivot can scale entire Displays independently without any mouse input issues. (CTRL+SHIFT+PLUS/MINUS) I was wondering if it would be possible to make the ScalePane a simple placeholder which would reserve space within a Display, and then overlay a scaled DisplayHost (an internal class of ApplicationContext/DesktopApplicationContext) in the right place. (The Pivot Components placed in the ScalePane would be painted to the DisplayHost) Alternatively it might be possible to somehow wrap the DisplayHost to effectively turn it into a Pivot Component. That might get messy though, as it is an AWT component in reality (if I understand correctly) I'm not 100% sure that any of this would work even for a simple scenario where the ScalePanes are not nested, and there would certainly be some logistical issues if there was a need to support nesting. Is that a realistic requirement? Chris On 24 July 2011 09:32, Bill van Melle <[email protected]> wrote: > Okay, I'll have a look. > > On Sat, Jul 23, 2011 at 7:15 PM, Chris Bartlett <[email protected]> > wrote: >> >> Yes, I understand that you are just trying to place the tooltips in >> the correct location. That app demonstrates positioning tooltips, but >> happens to take things further by creating them itself and place them >> in external windows. My intention was to show that it is possible to >> have some say over how a tooltip is displayed without having to modify >> core Pivot classes.
