>
> I don't think that's the correct solution either. If the state-trackers
> notion of the drawable is just marked invalid, the first state tracker
> context using the drawable will go ahead and update it. Subsequent contexts
> will see the updated drawable, but might want to adjust their viewport
On 05/24/2011 12:13 PM, Jakob Bornecrantz wrote:
On Tue, May 24, 2011 at 11:53 AM, Thomas Hellstrom
wrote:
Hi,
I'm not sure when this use of drawable<-> context bindings started, but the
below commit uses an invalid assumption to fix a problem the root cause of
which is also an invalid a
- Original Message -
> On Tue, May 24, 2011 at 11:53 AM, Thomas Hellstrom
> wrote:
> > Hi,
> >
> > I'm not sure when this use of drawable <-> context bindings
> > started, but the
> > below commit uses an invalid assumption to fix a problem the root
> > cause of
> > which is also an inva
- Original Message -
> Hi,
>
> I'm not sure when this use of drawable <-> context bindings started,
> but
> the below commit uses an invalid assumption to fix a problem the root
> cause of which is also an invalid assumption.
>
> It's incorrect to associate a drawable with a context.
>
On Tue, May 24, 2011 at 11:53 AM, Thomas Hellstrom
wrote:
> Hi,
>
> I'm not sure when this use of drawable <-> context bindings started, but the
> below commit uses an invalid assumption to fix a problem the root cause of
> which is also an invalid assumption.
>
> It's incorrect to associate a dra
Hi,
I'm not sure when this use of drawable <-> context bindings started, but
the below commit uses an invalid assumption to fix a problem the root
cause of which is also an invalid assumption.
It's incorrect to associate a drawable with a context.
A drawable may have multiple contexts bound t
