Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P purr-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 363
    • Issues 363
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #205

Closed
Open
Created Dec 20, 2016 by Jonathan Wilkes@jwilkesOwner

glist_doreload shouldn't trigger GUI window creation

When the user makes changes to an abstraction, Pd goes through the list of toplevel patches and reloads all instances of that abstraction. But it does this by opening the window for each abstraction, selecting the relevant abstraction, cutting it, and the undoing the cut. To achieve this, Pd has to make the subpatch visible, then make it invisible when it's finished.

This causes unnecessary messages to get sent to the GUI which temporarily flash new windows on the screen. Luckily the subcanvases themselves aren't mapped, so its just empty windows that show up. Still, these GUI messages should be suppressed.

Assignee
Assign to
Time tracking