Philip Brown <[EMAIL PROTECTED]> writes:

> On Wed, Jun 05, 2002 at 11:23:02AM +0200, Michael Natterer wrote:
> > 
> > this seems related to
> > 
> > Did you try to remove just the GDK_POINTER_MOTION_HINT_MASK?
> > XInput drivers are known to send wrong motion hints so this
> > may well be the reason for your problem.
> Hmm. I read the bugid, but it didnt really tell me what gimp is expecting
> in this case. Can you enlighten me?

GIMP just expects that the motion events' "is_hint" boolean is set correctly.
Motion hints are used to reduce the number of motion events X delivers.

> I didnt see anything about 'motion hint' in the xinput 'port' document.

Which is probably the reason why at least the wacom driver sets them
wrongly and thus breaks software which request hints.

It should just choose to not send hints at all end everything would
be fine (at least on the motion hint front :-)

> > (Checking "Perfect but slow Pointer Tracking" in preferences does the
> > same without patching the source, but will work only for the paint tools)
> It was already checked, under Interface->Image Windows.
> I unchecked it in a vanilla gimp1.2.3, with no difference.
> The grab still stops anything getting drawn except a single dot.

Then, unfortunately, the bug you see seems not to be related to
the hints.

> Also - you seem to imply that it is possible to use a non-core xinput
> device for things other than plain drawing. I'd like to know how.

Nope, I just wanted to make clear that only the paint tools have
the builtin possibility to switch hints on/off. Other tools like
the rect_select tool don't have this.

> I find it somewhat irritating, for example, that a button3 on my pen will
> bring up a menu, that I can do nothing with , with the pen.
> Not only can I do nothing with it: I have to grab the core mouse to get rid
> of it.

Yes, i have the same effect. We could check if the device which sent
button3 is the core pointer...

> It seems like there has been too much of an assumption that the user will
> run their xinput device with the 'AlwaysCore' hack.

There is no such assumption.

> I think it should be quite possible to have a very usable interface,even
> when the pen is non-core. 
> Making that menu traversable would be a great start.

I don't understand what you mean by this.

BTW, would you try gimp 1.3.7 (or CVS) and try if the problem still
persists there? If they behave different we'd have a hint how to
fix 1.2. If 1.3.7 has the effect too, we have a bug on both branches :(

Gimp-developer mailing list

Reply via email to