Hi, Can you provide a minimal compilable code that shows that behaviour ?

@sgaist Hmmmmmmmmm I wrote a little routine to use mouse press/release to see what has changed to determine my selection but it does not work as well as I wish. But I missed that focusItemChanged mhmhmhmh thanks! Will go over it again :- )

I have just figured it out. My first misunderstanding was that the boundingRect()'s coordinates must be (-0.5,-0.5) which means they are relative to the current item's position and not absolute on the Scene. and so this is the correct one: QRectF GIPoint::boundingRect() const { // return QRectF(pos().x(), pos().y(), 5, 5); return QRectF(-0.5, -0.5, 5, 5); } My second misunderstanding was in paint(). Do not use the pos() or scenePos() coordinates in order to draw the item. Instead draw it at (0,0). So the corrected paint() is this: void GIPoint::paint( QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget ){ (void )option; (void )widget; QRectF rect = boundingRect(); qWarning() << "painting: scenePos " << scenePos() << ", rect " << rect; QBrush brush = QBrush(Qt::black, Qt::SolidPattern); painter->fillRect(rect, brush); //painter->drawRect(rect); } The original program in my question still needs to be modified. Or shall I edit the changes in?

I've updated the question with gif/some updates... Still fighting with it o.o I think by using int vertOffset = horizontalScrollBar()->sliderPosition(); I can somehow calculate the "jump" value offset and offset position of line by that. Not sure how yet tho...

Call fitInView on the GraphicsView with the Image whenever the size of the GraphicsView changes. The rest should work automatically.

Hi, I got the expected output from grab(QRect) https://stackoverflow.com/questions/16362191/qt-grab-widget-and-save-image m_graphicsView->grab(rect).save("OUT.jpg"); Thanks all.

Thanks @SGaist and @raven-worx , I try both methods to see which one to use better in my program.

I found the problem. I was drawing the beats before the lines, so the lines took precedent over the beats since they are siblings. The solution was to either draw the beats last or set the Z value on the beat, not the note.

The idea is that you have your container widget getting resized and in its resize event, you change the size of the inner widgets with the ratio you want.

@Niagarer Good found. :)

@mrjj There are other obstacles that I need to overcome. But this way seems to be the solution that i am implementing. Thanks

@SGaist Hi Sam, Thank you for your hint, but my first problem was preventing the edit trigger on single click. For the posterity I have ended up with the following solution: Disable the textInteraction flags by default Override the QGraphicsTextItem::sceneEvent with the following: bool ValueAxisLabel::sceneEvent(QEvent *event) { if (event->type() == QEvent::GraphicsSceneMouseDoubleClick) { setTextInteractionFlags(Qt::TextEditorInteraction); bool ret = QGraphicsTextItem::sceneEvent(event); // QGraphicsTextItem::sceneevent needs to be processed before // the focus setFocus(Qt::MouseFocusReason); return ret; } return QGraphicsTextItem::sceneEvent(event); } The textInteractionFlags should be disabled in the overridden focusOutEvent.

In your MyView::paintEvent write QPainter painter(viewport()); instead of QPainter painter(this);.

@AdrianCruz hi Super :) just as a note To avoid getting possible NULLs in the list, i would suggest doing QGraphicsItem *item = qgraphicsitem_cast<QGraphicsItem*>(text); if (item) list.push_back(item);

Hi, You shouldn't use the size of a widget in its own constructor. The widget being not yet visible, the value won't make sense.

@raven-worx I tried the following but didn't work out.. QGraphicsPixmapItem* item = new QGraphicsPixmapItem(QPixmap::fromImage(qImage, Qt::AutoColor)); m_ViewerScene->addItem(item); QGraphicsRectItem* rect = new QGraphicsRectItem(m_BoundingBox); m_ViewerScene->addItem(rect); rect->setParentItem(item); m_ViewerScene->update(); //add the resized QGraphicsPixmapItem to the pixmap item->setPixmap( item->pixmap().scaled(QSize(128, 32),Qt::IgnoreAspectRatio, Qt::SmoothTransformation)); qInfo()<<"Rect resize props:::"<<item->childItems()[0]->boundingRect(); m_BoundingBox = item->childItems()[0]->boundingRect(); later I'm drawing box, on the image in an other viewer, with m_BoundingBox. The grey area within the blue rectangle will be resized to 128 * 32, and then the red rectangle would be added on the resized image. How to get the co-ordinates of red rect on the resized image?

Hi @wthung, I don't think this forum supports file uploads. Can you create a simple example that demonstrates the memory leak? Just post the code here, no need to upload an attachment.

@JEllery Glad you got it fixed. Sorry I disappeared mid helping you. I get really busy with work sometimes and don't have time to be on the forums here.

Hi I just keep a pointer to the "white lines" and adjust if i move yellow. class ColorItem : public QGraphicsItem { .. ConnectorLine* line = nullptr; .. protected: QVariant itemChange(GraphicsItemChange change, const QVariant& value) override { if (change == ItemPositionChange && scene()) { if (line) { line->adjust(); } } return QGraphicsItem::itemChange(change, value); } private: QColor color; }; line->Adjust() alters its endpoints. You could just adjust it directly here.

You're welcome ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)

What do you think about this? int length = this->boundingRect().width(); length = (int)(((double)length * (double)value) / 100.0); QPixmap pix(this->boundingRect().width() - length, this->boundingRect().height()); pix.fill(Qt::transparent); QPainter p; p.begin(&pix); p.fillRect(pix.rect(), QColor(0, 0, 0, 120)); p.end(); gauge->setPixmap(pix); gauge->setPos(pos().x()+length, pos().y()); It works fine and the effect is the same as on example pixtures above.

:D I haven't had much time to test if the bug exists in Qt5. I'll check it out and update the topic accordingly. If the bug is still there, of course, I will submit the fix. Thanks for your time.

Its not moving the pointer that is making it work. It is the QRect that I created to test. If I comment out the rect it all goes back to not moving and only being created at 0,0

@Wieland Wow you are just killing it today for me aren't you? Haha. I'll judge which is best for me a give it a roll. Thanks a bunch (again)! EDIT: I ended up going for the event filter route and it works beautifully. Other than the exact syntax the approach also feels pretty intuitive which I like.

I had the same problem with items moving rightward as I stretched the window/viewport beyond the scene rect. This fixed it: view->setAlignment( Qt::AlignLeft | Qt::AlignTop );

@Joel-Bodenmann That's the manual way i talked about uptop but thanks anyways :) It reassures me that i'm not "re-inventing" the wheel by applying this method .

Yep , fixed !! Biggest achievement of ma layf. Topic->setAsSolvedPolicy(Qt::AlwaysTrue);

I'd recommend reading this article which explains everything fairly well: Coordinate System As the article explains, each graphics item maintains it's own coordinate system. The methods you are referring to are used to translate coordinates between those items, between the items and the scene and so on. I hope that reading that article will help, otherwise feel free to ask if clarification is needed.

I had misconfigured ensureVisible's margins , and the view's size and the scene's rect . Now it works fine :)

ok will do

@LoPiTaL you could still combine both styles in one CSS. You just need to adapt your selectors. E.g. you could set an property to your widgets and only apply certain styles to them.

@cfdev said: I would like to know if Qtquick can doing the same thing as QGraphicsScene ? Yes.

Hi you could maybe use http://doc.qt.io/qt-5/qgraphicsitem.html#sceneBoundingRect and see if they are next to each other?

I implemented some kind of clipping done in the MainWindow's paintEvent(). This leads to a satisfying number of items. But the question: Is this the right place to remove and / or create scene items?