Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
purr-data
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 268
    • Issues 268
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #496

Closed
Open
Opened Jan 06, 2019 by Jonathan Wilkes@jwilkesMaintainer

fix z-ordering on unaccelerated redraws

Some objects-- especially externals-- will do redraws by having two gobj_vis calls in a row to revis the object.

This on its own will put the redrawn object at the top of the z-order stack.

We should probably revisit these "unaccelerated redraws" and add a call there to re-order the newly drawn object in its proper z-order.

I think there are already some functions to do this which are currently used by the undo system. We just need to utilize them.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: jwilkes/purr-data#496