@raven-worx
Thanks bro,
very helpfull.

Edit: I have checked that if coordinates are [0.3 0.5 0.3 0.9] and I set pen.widthf bigger, then I can select much better the lines, but if the coordinates are [30 50 30 90] that does not work...

Thank you. It worked.

Thanks for your reply.

Using setText will avoid useless delete/allocation of items.

When you set the item, The table takes ownership of the item. So just deleting the tableWidget should satisfy. If you want to selectively delete, what you are doing should be good enough.

@kylecorver Can you post the complete program? The original isn't a a valid Qml document, leading to guessing about which errors will or will not occur. The OS and Qt version used might also be relevant.

@Lorence said:

Hi when you add "xxxx" to a qlistwidget
you are adding a QListWidgetItem.

While you can subclass QListWidgetItem and make your own
that has signals, it would not do you so much good as

it would never never emit such signal unless you also made it do
so when something happen to it. (overriding some of its functions)

So It all depends what you are trying to do.
If you just want to know its no 1,2,3 etc, even if moved
then
you can insert that info into the QListWidgetItem using the
void QListWidgetItem::setData(int role, const QVariant & value)

something like
QListWidgetItem * item=new QListWidgetItem("item1") ;
item->setData(Qt::UserRole, 1); // or 2 for item 2 etc
list->addItem(item)

then you can always know which is which even if rearranged.
see here for how to take index out also
http://stackoverflow.com/questions/7136818/can-i-store-some-user-data-in-every-item-of-a-qlistwidget

@SGaist Thank you dude, setCurrentRow is what I want!

Hi,

You are looking for QTreeWidget::setCurrentItem

Yeah, according to QComboBox code should work:

QVariant QComboBox::itemData(int index, int role) const { Q_D(const QComboBox); QModelIndex mi = d->model->index(index, d->modelColumn, d->root); return d->model->data(mi, role); }

Will implement this.

I do not understand last question. I do not see any problem with mapping which rely on the item bounding rectangle.

You can have an infinite number of visually the same graphics items if you use different combination of position and bounding box parameters.

For example if you create QGraphicsEllipseItem using following rectangle/position pairs you will get the same result on the screen?
pair 1:
QRectF rect1( 0, 0, 1., 2 );
QPointF pos1(10.,20.);
pair 2:
QRectF rect1( 10,20, 1., 2 );
QPointF pos1(0.,0.);

Which way to define depends on your needs.

@p3c0 Thanks!

@guidupas You're Welcome :)
Use ``` (3 backticks) instead of [Code] when posting code here. It follows markdown language syntax. I'll edit it for now.

Hi @Jean,

yes, you're right. But in my case this is unfortunately not possible. What I am doing is developing a Toolkit with a bunch of Controls for displaying data. These controls are not used by me (even not used by really developers) but used by people who are configuring the UI pages via drag and drop in the Quick Designer. This is why the logic should be encapsulated within the control...

Thanks again!

Cheers,
Frime

Hi,

I think you can do something using SharedEffect::vertexShader. I'm not an expert but you can find some information and examples here