Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linked Views: When unlinking a Range filter overridden view: Ask user: Keep master range filter ? #539

Closed
JacobStoren opened this issue Sep 23, 2015 · 0 comments
Assignees
Labels
Enhancement An addition that can be observed by the user
Milestone

Comments

@JacobStoren
Copy link
Member

And thereby overwrite the original rangefilter collection

@JacobStoren JacobStoren added the Enhancement An addition that can be observed by the user label Sep 23, 2015
@JacobStoren JacobStoren modified the milestones: Suggestions GM Sprint 7, Geom Sprint 7 Sep 23, 2015
magnesj added a commit that referenced this issue Oct 19, 2015
Propagate pointer to a range filter if only a single filter is modified
Moved lifetime management of range filter collection to RimView
magnesj added a commit that referenced this issue Oct 21, 2015
magnesj added a commit that referenced this issue Oct 21, 2015
When a context menu is created in the viewer is, and the action
triggered is displaying a dialog,
the context menu of QMainWindow is displayed after the action has
finished
Setting this policy will make sure the handling is not deferred to the
widget's parent,
which solves the problem - Qt::PreventContextMenu
magnesj added a commit that referenced this issue Oct 21, 2015
… collection to use

As the management of override range filter collection is handled
independenly from scheduleRedraw, we must check for a valid pointer when
trying to access the override range filter
@magnesj magnesj closed this as completed Oct 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An addition that can be observed by the user
Projects
None yet
Development

No branches or pull requests

2 participants