Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BornAgain BornAgain
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 170
    • Issues 170
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mlzmlz
  • BornAgainBornAgain
  • Merge requests
  • !957

GUI: fix for a simulation with specular data

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Mikhail Svechnikov requested to merge i311 into main Jun 15, 2022
  • Overview 0
  • Commits 5
  • Pipelines 1
  • Changes 20

This resolves #311 (closed).

Previously, JobListModel used QAbstractItemModel signals rowsAboutToBeInserted and rowsInserted for the notification on job addition. These signals were emitted implicitly.

It seems that these signals were emitted in some other unprovided situations and JobListModel tried to enable/disable notifications for the non-existing job. I couldn't localize the origin of this signal.

Now JobModel emits special unique signal on adding a new job.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: i311