how to link library in Qt( like gcc -l command)

[wysota]

Can we see the relevant code of yours? Please also say what you need the native event for. One more thing - the docs say the events will only be delivered to the widget when it is native (meaning it's not an alien) - did you disable alien support for it?

[dzh1121]

Goal is to capture the XI2 event for multiple cursor( for different mouse/keyboard)
Here's some relevant code. (I've check the has_xi2 for my display, and set the event mask in the MainWindow's constructor.

bool MainWindow::x11Event(XEvent * e)
{
	XEvent ev = *e;
	XGenericEventCookie *cookie = &ev.xcookie; //&e->xcookie;
	if(cookie->type != GenericEvent || cookie->extension != xi_opcode || !XGetEventData(dpy, cookie) ){
		printf("No GenericEvent  Type is found in X11Event,   return   ******************* \n");
		return false;
	}
	printf("EVENT TYPE %d \n", cookie->evtype);
	switch(cookie->evtype){
	case XI_RawMotion:
		print_rawmotion((XIRawEvent *)cookie->data);
		break;
	case XI_Enter:
	case XI_Leave:
		print_enterleaveevent((XIEnterEvent *)cookie->data);
		break;
	default:
		print_deviceEvent((XIDeviceEvent *)cookie->data);
		break;
	}
	return false;
}

bool MainWindow::x11Event(XEvent * e)
{
	XEvent ev = *e;
	XGenericEventCookie *cookie = &ev.xcookie; //&e->xcookie;
	if(cookie->type != GenericEvent || cookie->extension != xi_opcode || !XGetEventData(dpy, cookie) ){
		printf("No GenericEvent  Type is found in X11Event,   return   ******************* \n");
		return false;
	}
	printf("EVENT TYPE %d \n", cookie->evtype);
	switch(cookie->evtype){
	case XI_RawMotion:
		print_rawmotion((XIRawEvent *)cookie->data);
		break;
	case XI_Enter:
	case XI_Leave:
		print_enterleaveevent((XIEnterEvent *)cookie->data);
		break;
	default:
		print_deviceEvent((XIDeviceEvent *)cookie->data);
		break;
	}
	return false;
}

To copy to clipboard, switch view to plain text mode 

If needed, I can send more code to your email.

BTW, what do you mean that the event is native. would you please show me the document you've seen?

Thanks

[wysota]

Goal is to capture the XI2 event for multiple cursor( for different mouse/keyboard)
Here's some relevant code. (I've check the has_xi2 for my display, and set the event mask in the MainWindow's constructor.

So what's the problem exactly? It seems Qt has nothing to do with your situation. For instance I don't think it supports more than one input focus at the same time.

BTW, what do you mean that the event is native. would you please show me the document you've seen?

By native event I mean an event generated by the native API (X11 in this case) and not Qt.

How do you intend to use the extra information provided by XInput2?

[dzh1121]

Thanks for your reply.
On Ubuntu 10.04, I've already have 2 cursor, each for one mouse.
My problem is that, I expect GenericEvent( in X.h file), so I can transfer them to XI2( in XI2.h file) defined event.
But now, all event type is the the ones defined in X.h, like KeyPress, ButtonRelease, but never GenericEvent.

in the simpliest command line program, I can get the XI2 event.
But for the program in Qt, only the X2 event could be received. (see my sample code of X11Event() )
but I've check XI2 ,and my Qt program tells me that

XI2 supported. Server provides version 2.0.

For everything related to event capture is the same.
So as the beginning, I thought it maybe the link file problem.(but now, it seems not.)

For your second question, all my event is native, from X11 Event, for sure. [just they are not the extention case(XI2)]

[wysota]

For your second question, all my event is native, from X11 Event, for sure. [just they are not the extention case(XI2)]

That's of course not true If that were the case, Qt wouldn't be working as everything in it is driven by Qt originating events. Only what goes to x11event() is a native event. I think your problem might be that Qt simply doesn't forward these kinds of events to the widget. I think you should be reimplementing QApplication::x11EventFilter() instead.

[dzh1121]

wow, really??
You know, I had thought that since X11Event is virtual, we do not need to reimplement them.
And QWidget::x11Event() would have all the event type.
Seems you are right.
I'll test it now.

BTW, should I inherit QApplication for my QMainWindow?(currently, it inherits from QWidget).

[wysota]

You know, I had thought that since X11Event is virtual, we do not need to reimplement them.

Hmm... when some method is virtual it usually means it is meant to be reimplemented...

And QWidget::x11Event() would have all the event type.

Only events that are meant for this particular widget will be forwarded to it. Of course unless the widget is alien, then it won't get any native events.

BTW, should I inherit QApplication for my QMainWindow?(currently, it inherits from QWidget).

I will not answer this question but instead send you back to the docs to compare QApplication and QWidget classes and think whether one can substitute the other as a super class of QMainWindow.

[dzh1121]

wysota,

Thanks for all your replies.

As I still did not figure how to receive the original Xlib event in Qt. ( It should be able to, but I just cann't work it out.)
As you said, x11EventFilter() maybe the reason.
Although I still did not make it.

Now, my current solution is using a C program to receive XEvent and send that event into a java client.( still stuck by a problem to find the WindowID of java GUI.)
But, anyway, thank again.

Thanks for all your effor, all your instruction and etc.

With regards.

Tiger