Mailing-List: contact user-help@pivot.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@pivot.apache.org
Received-SPF: pass (athena.apache.org: domain of cbartlett.x@gmail.com
 designates 209.85.161.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAaiUA5rh9L_iweBLgYx2BiwwZKt-rDoRqCWsz2kdCKDBDh6QA@mail.gmail.com>
References: 
 <CAAaiUA6si-RO3V3HDHZ_rmtJJTZRq+xup5FVX7-DTLBccQUGdg@mail.gmail.com>
	<4E29275F.3000104@gmail.com>
	<CAAaiUA43raWyKvA2VYYpPVjrfNKj=ZRBj7m=ZFBG3rWfcBJpqg@mail.gmail.com>
	<CAFeFZ4seo3pMPfr2vU8M5bO2DFRGJeKOk+mxMhT7pzaLB9gmiA@mail.gmail.com>
	<CAAaiUA4L6piqNQKrRrD3AAgtVdmYXUrvpF-zzNOvzrkxg6eALA@mail.gmail.com>
	<CAAaiUA59nABG=PfDBmi_rvGsh4mv537edQENcrdaWymDfMSXSQ@mail.gmail.com>
	<CAAaiUA5-=jrcK5NWZm4VoSM4f71zk=J8YKTNZLiOPOJdDgvBHw@mail.gmail.com>
	<CAFeFZ4v4Q7YguBNGO0g7TDBVkoZgVF06izKUwgDwWrL6R0cing@mail.gmail.com>
	<CAAaiUA4-7TqJqW=AJCvZXFFVjU8VR0Q2beYjoKVSR_tSAByLiQ@mail.gmail.com>
	<CAFeFZ4vgN8mhwbo36LJ1wW1gyZBhYX2UdjMjUOoFnXpN2bkaJw@mail.gmail.com>
	<CAAaiUA5rh9L_iweBLgYx2BiwwZKt-rDoRqCWsz2kdCKDBDh6QA@mail.gmail.com>
Date: Sun, 24 Jul 2011 10:16:59 +0700
Message-ID: 
 <CAFeFZ4scJ-hT5nT96mYTTJ3HYrqm84y3RK+AbsG_8ROXjmm44Q@mail.gmail.com>
Subject: Re: Hard to implement ScalePane
From: Chris Bartlett <cbartlett.x@gmail.com>
To: user@pivot.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <bill.van.melle@gmail.com> wrote:
> Okay, I'll have a look.
>
> On Sat, Jul 23, 2011 at 7:15 PM, Chris Bartlett <cbartlett.x@gmail.com>
> wrote:
>>
>> Yes, I understand that you are just trying to place the tooltips in
>> the correct location. =A0That 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
>> =A0core Pivot classes.