You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two main hurdles to cross before this can happen.
Make an item clickable in multiple places
Implement the actual Perspective widget and fill it with data on click.
How to go about (1) is new territory to me. We can either handle this in the view, a QListView in this case, or in the delegate, a QStyledItemDelegate.
If handled in the view, then we could simply look up the position of the cursor to determine whether the click happened to the left, or to the right. The problem is communicating this information to the delegate such that it can highlight/animate it properly.
If handled in the delegate, then we can simply add widgets to the left and right sides and attach event handlers to each of them. The problem then is that we will have to find some method of still being able to select an item, and select multiple items, which is handled by the view.
So no matter how we go about it, there must be some form of information exchange between the view and the delegate, and I'm not sure which route is better.
The text was updated successfully, but these errors were encountered:
Goal
One should be able to dive into an item and be given a dedicated overview of information only relevant to this item.
Like in Pyblish QML.
Implementation
There are two main hurdles to cross before this can happen.
How to go about (1) is new territory to me. We can either handle this in the view, a
QListView
in this case, or in the delegate, aQStyledItemDelegate
.If handled in the view, then we could simply look up the position of the cursor to determine whether the click happened to the left, or to the right. The problem is communicating this information to the delegate such that it can highlight/animate it properly.
If handled in the delegate, then we can simply add widgets to the left and right sides and attach event handlers to each of them. The problem then is that we will have to find some method of still being able to select an item, and select multiple items, which is handled by the view.
So no matter how we go about it, there must be some form of information exchange between the view and the delegate, and I'm not sure which route is better.
The text was updated successfully, but these errors were encountered: