Skip to content
GitLab
Projects Groups Snippets
  • /
  • 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 49
    • Merge requests 49
  • 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
  • #686
Closed
Open
Issue created Sep 23, 2020 by Ivica Bukvic@icoDeveloper

text object, message, and comment, when edited are reinstantiated and thrown on top of the glist stack

text object, message, and comment, when edited, are reinstantiated and thrown on top of the glist stack which messes with the preset hub instances that rely on externally saved presets and which rely on prerecorded node locations. This renders saved presets useless. May also need to warn users that to front/to back commands may exacerbate this problem for all objects. May need to be addressed through both retaining the existing object position and improving the hub logic.

Assignee
Assign to
Time tracking