Using custom events.

[hickscorp]

An Optimization? i'm not sure i understand... Now i've pointed it out, you know it's an optimization? Why not telling it in the doc then?... i really don't think it's an optimisation (When registering a new event type, it's based on it's type #ID, not it's class... If internally Qt does a type check based on the class, it makes no sense... i don't even think it's possible, since QEvent is not a subclass of QObject, and since my subclasses don't Q_OBJECT, it's not possible to get the superclass at runtime.

Explain me, i really hate to get vague guesses

Pierre.

[wysota]

An Optimization? i'm not sure i understand...

There is no point in tracking mouse position on the items (which requires coordinate transformations and collision detection) if you know the mouse is not in any of the views that hold the items. There is no point in tracking the mouse to detect hover events if you know the mouse is not over the item, etc. I'd assume it's exactly the same for widgets, although it might be a bit different as there is no scene equivalent for widgets so you'd post the event directly to the widget and this will probably just work (although Qt will not try to detect hover events by itself).

Now i've pointed it out, you know it's an optimization?

It's just logical to assume so. Qt is open source, you can easily verify my assumption by reading its source code.

Why not telling it in the doc then?...

If every detail was covered in the docs and every possible abuse of Qt was warned about in the docs, then the docs would have several gigabytes of volume and there would still be creative people who would invent new ways of abusing Qt.

[hickscorp]

There is no point in tracking mouse position on the items (which requires coordinate transformations and collision detection) if you know the mouse is not in any of the views that hold the items. There is no point in tracking the mouse to detect hover events if you know the mouse is not over the item, etc. I'd assume it's exactly the same for widgets, although it might be a bit different as there is no scene equivalent for widgets so you'd post the event directly to the widget and this will probably just work (although Qt will not try to detect hover events by itself).
It's just logical to assume so. Qt is open source, you can easily verify my assumption by reading its source code.
If every detail was covered in the docs and every possible abuse of Qt was warned about in the docs, then the docs would have several gigabytes of volume and there would still be creative people who would invent new ways of abusing Qt.

i'm not sure you see the problem.... The mouse is tracked, whatever if there is a point or not (QGraphicsItem has the hovering methods virtual, which allows subclassing + overriding). it's not a mouse tracking related problem. it's an custom event propagation problem. i could be trying to post ANY other kind of event (Even NOT hover-related), as long as they are custom, derived from a class itself derived from QEvent, it won't work.

Try it yourself. Make a class A, derived from QEvent. Make a class B, derived from A. Register a custome event type assigned to either A or B. Post a B. (You'll never receive it in your target, whatever you're using post or send). Try this outside any QGraphics context, again: i'm really not talking about any hover / mouse / move thingy stuff.

@high_flier: Sorry, i don't understand your answer. Are you misstaking me with me? You're saying i'm suggesting myself something? XD

[wysota]

Only GUI-related events are propagated. Custom events are not GUI related.

[high_flyer]

@high_flier: Sorry, i don't understand your answer. Are you misstaking me with me? You're saying i'm suggesting myself something? XD

I meant agathiyaa.

[agathiyaa]

Hi...

I have found the exact problem in your code.

Qt ( C++) allows / accepts subclasses of QEvent, Also sub-subclasses / throughout the inheritance hierarchy

It seems "HoverEnter" & "HoverLeave" is defined or used somewhere else. If you try different name or

class HoverEnterEvent : public AWBObject::Event {
	public:
		HoverEnterEvent	() : Event(AWBObject::HoverEnter) {};
	};

class HoverEnterEvent : public AWBObject::Event {
	public:
		HoverEnterEvent	() : Event(AWBObject::HoverEnter) {};
	};

To copy to clipboard, switch view to plain text mode 

it should work for you as is.(Note: AWBObject::HoverEnter)

Please give a try and let us know. It worked for me.