How to send the QGraphicsItem to the background of QGraphicsView

[battena]

Thanks for your quick ans.

I could hide using "setVisible(false)", intention is to paint the item and make visible and disable events & actions
I tried with SetEnabled(false) but it did not work.

[wysota]

Why exactly do you want to do all that?

[battena]

good question.

I am doing as follows...

I have two applications..
In first application I have a QGraphicsView attached with QGraphicsScene, where I do some design like draw border based on vertical & harizantal values.
Also I placed some text graphics item at the top say 'Author "xxxx"'. Now I have to steam this info into a file using QDataStream.

In second application I need to load the stream and create the saved objects like QGraphcisRectItem & QGraphicsTextItem with values and display them in the background. what ever we create further items shall be on top of them.

I hope I answered to you question.

[wysota]

I do not see how this is related to wanting an item to ignore mouse events

[battena]

I am creating selection handles for the newly created graphic item there I have a constraint that I should not create a selection handle if I find a item below to it with the function itemAt(pos).
Since those items are not send to the background they are caught by the itemAt() function.

this is the use case.

[wysota]

Since those items are not send to the background they are caught by the itemAt() function.

Ok but WHAT items?

[battena]

sorry!

as I said in the first application I have saved some graphic items like rect, text.
In the second application I have loaded the saved items.
and then I draw a new rectangle graphic item above to them.

[wysota]

Yes, and so? Please do not focus your description on the itemAt() method but rather say what exact behaviour you want to achieve globally. I'm assuming you know about the z-order of items and you can determine which object is "above" and which is "below" but I totally fail to see WHAT item should have its mouse events ignored and WHY (especially that it won't affect what itemAt() returns).