QToolBox change cursor on hover

[mrjj]

@Mecanik

Hi
Sounds like you should also put a filter on the actual toolbox then?

[Mecanik]

@mrjj said in QToolBox change cursor on hover:

@Mecanik

Hi
Sounds like you should also put a filter on the actual toolbox then?

Sorry, but I don't know how to do this. I`m just learning the QT framework, and this is the reason I came here asking.

[mrjj]

@Mecanik

well just like before but instead of the pointer you get from QToolBox::widget
then just use
ui->toolbox instead. (if toolbox is made in the designer )

If it still dont work over the title, we need to find out which object that is then :)

[Mecanik]

@mrjj said in QToolBox change cursor on hover:

@Mecanik

well just like before but instead of the pointer you get from QToolBox::widget
then just use
ui->toolbox instead. (if toolbox is made in the designer )

If it still dont work over the title, we need to find out which object that is then :)

Thanks, I have already tried this. I even tried this method: https://stackoverflow.com/questions/411823/how-do-i-implement-qhoverevent-in-qt#answer-26392025

No success...

[mrjj]

@Mecanik

Well, the main issue with such hover is that events are delivered to the widget under the mouse.
So we must put the filter on the right widget to be able to catch it.

if we do

ui->toolBox->dumpObjectTree();

we get how its made up

QToolBox::toolBox
QVBoxLayout::
QToolBoxButton::qt_toolbox_toolboxbutton
QScrollArea::
QWidget::qt_scrollarea_viewport
QWidget::page
QWidget::qt_scrollarea_hcontainer
QScrollBar::
QBoxLayout::
QWidget::qt_scrollarea_vcontainer
QScrollBar::
QBoxLayout::
QToolBoxButton::qt_toolbox_toolboxbutton
QScrollArea::
QWidget::qt_scrollarea_viewport
QWidget::page_2
QWidget::qt_scrollarea_hcontainer
QScrollBar::
QBoxLayout::
QWidget::qt_scrollarea_vcontainer
QScrollBar::
QBoxLayout::
**

so it seems the title is the QToolBoxButton called qt_toolbox_toolboxbutton

so we can do

// find all childred with the name 
auto list = ui->toolBox->findChildren<QWidget*>("qt_toolbox_toolboxbutton");

  for (QWidget *title : list) {
   title->hide(); // this was just to test :)  Remove
  you should install filter here
  }

[Mecanik]

@mrjj said in QToolBox change cursor on hover:

@Mecanik

Well, the main issue with such hover is that events are delivered to the widget under the mouse.
So we must put the filter on the right widget to be able to catch it.

if we do

ui->toolBox->dumpObjectTree();

we get how its made up

QToolBox::toolBox
QVBoxLayout::
QToolBoxButton::qt_toolbox_toolboxbutton
QScrollArea::
QWidget::qt_scrollarea_viewport
QWidget::page
QWidget::qt_scrollarea_hcontainer
QScrollBar::
QBoxLayout::
QWidget::qt_scrollarea_vcontainer
QScrollBar::
QBoxLayout::
QToolBoxButton::qt_toolbox_toolboxbutton
QScrollArea::
QWidget::qt_scrollarea_viewport
QWidget::page_2
QWidget::qt_scrollarea_hcontainer
QScrollBar::
QBoxLayout::
QWidget::qt_scrollarea_vcontainer
QScrollBar::
QBoxLayout::
**

so it seems the title is the QToolBoxButton called qt_toolbox_toolboxbutton

so we can do

// find all childred with the name 
auto list = ui->toolBox->findChildren<QWidget*>("qt_toolbox_toolboxbutton");

  for (QWidget *title : list) {
   title->hide(); // this was just to test :)  Remove
  you should install filter here
  }

Thank you, this is VERY helpful. I`m still being a bit dumb, please see what I did:

auto list = ui.MenuToolBox->findChildren<QWidget*>("qt_toolbox_toolboxbutton");

for (QWidget* title : list) 
{
   title->installEventFilter(this);
}

bool app::eventFilter(QObject* obj, QEvent* e)
{
  qDebug() << Q_FUNC_INFO << obj->objectName();
  qDebug() << Q_FUNC_INFO << e->type();

  if (e->type() == QEvent::HoverEnter)
  {
     setCursor(Qt::PointingHandCursor);
  }
}

I suppose setCursor is called wrong here? Please advise.

There is also the question of sub classing this "eventFilter"? Just because in the main app most likely I will need the evenFilter for something else :/

[mrjj]

@Mecanik

Hi
It looks ok but does it change the Cursor ?

Also, this way it will be set and never reset again, is that what you want ?

• There is also the question of sub classing this "eventFilter"?

Well you can just use a QObject based handler and not tie it to MainWindow.

the ui.xxx->installEventFilter(this);
The "this" part is the object that has the event filter method /the handler.

so you can do like

#include <QObject>
#include <QMouseEvent>
#include <QDebug>
#include <QCursor>

class myEventFilter: public QObject {
  Q_OBJECT
public:
  myEventFilter() {}
  ~myEventFilter() {
  }
protected:
  bool eventFilter(QObject* object, QEvent* event) {
    if(event->type() == QEvent::MouseMove) {
      int x = QCursor::pos().x();
      int y = QCursor::pos().y();
      qDebug() << "MP -> (" + QString::number(x) + "," + QString::number(y) + ")";
      return false; // make it unhandled and sent to other filters.
    } else
      return false;
  }
};

https://forum.qt.io/topic/83995/eventfilter-anywhere-in-the-program/2

To have a standalone class to handle it. If that is what you mean by subclassing ?

thewatched->installEventFilter(new myEventFilter());

[Mecanik]

@mrjj said in QToolBox change cursor on hover:

@Mecanik

Hi
It looks ok but does it change the Cursor ?

Also, this way it will be set and never reset again, is that what you want ?

• There is also the question of sub classing this "eventFilter"?

Well you can just use a QObject based handler and not tie it to MainWindow.

the ui.xxx->installEventFilter(this);
The "this" part is the object that has the event filter method /the handler.

so you can do like

#include <QObject>
#include <QMouseEvent>
#include <QDebug>
#include <QCursor>

class myEventFilter: public QObject {
  Q_OBJECT
public:
  myEventFilter() {}
  ~myEventFilter() {
  }
protected:
  bool eventFilter(QObject* object, QEvent* event) {
    if(event->type() == QEvent::MouseMove) {
      int x = QCursor::pos().x();
      int y = QCursor::pos().y();
      qDebug() << "MP -> (" + QString::number(x) + "," + QString::number(y) + ")";
      return false; // make it unhandled and sent to other filters.
    } else
      return false;
  }
};

https://forum.qt.io/topic/83995/eventfilter-anywhere-in-the-program/2

To have a standalone class to handle it. If that is what you mean by subclassing ?

thewatched->installEventFilter(new myEventFilter());

It changes the cursor for the whole main window, but not the items on the toolbox.

Thank you for the myEventFilter example, that's exactly what I meant.

[mrjj]

@Mecanik said in QToolBox change cursor on hover:

It changes the cursor for the whole main window, but not the items on the toolbox.

Ah. i though that was the goal sorry.

So you mean
obj->setCursor(Qt::PointingHandCursor);

Do note setCursor is from QWidget, I think, so It might complain
and you have to cast obj to qwidget via q_objectcast

[Mecanik]

@mrjj said in QToolBox change cursor on hover:

@Mecanik said in QToolBox change cursor on hover:

It changes the cursor for the whole main window, but not the items on the toolbox.

Ah. i though that was the goal sorry.

So you mean
obj->setCursor(Qt::PointingHandCursor);

Do note setCursor is from QWidget, I think, so It might complain
and you have to cast obj to qwidget via q_objectcast

Job done... I cannot thank you enough. This was really frustrating. With WinApi it was hard as well, but at least I knew what I was looking for / doing. There is much to learn about QT.

I managed to create a separate class for this purpose and a proper even filter:

bool windoweventfilter::eventFilter(QObject* object, QEvent* event)
{
    if (event->type() == QEvent::HoverEnter)
    {
        QWidget* qObj = qobject_cast<QWidget*>(object);

        if (qObj)
        {
            qObj->setCursor(Qt::PointingHandCursor);
        }
    }
    
   return QObject::eventFilter(object, event);
}

Thanks again :)

[mrjj]

@Mecanik

+10 for checking the cast before use :)

Yes Qt is quite huge. I actually learned alot of the classed by helping people do stuff
here . It sticks better when used for something and not just reading the docs.

However, good questions here often give good answers so you can always return
and ask if you get stuck.