IPKM/nmreval
14
2
Fork 1
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

Konsistenz in Reihenfolg der Liste aktiver Datensätze #111

New Issue
Closed
opened 2023-07-28 18:16:02 +00:00 by dominik · 0 comments
dominik commented 2023-07-28 18:16:02 +00:00
Member
Copy Link

Die Reihenfolge in der Liste der aktiven (angezeigten) Daten hängt von der Reihenfolge ab, in der sie angezeigt wurden, Aus- und Einblenden ändert Position in der Liste. Die Reihenfolge der Fitparameter (Issue #109) und in Shift/Scale ist deshalb ziemlich unvorhersehbar.

Die Reihenfolge sollte der Reihenfolge der im Baum angezeigten Reihenfolge entsprechen.

Die Reihenfolge in der Liste der aktiven (angezeigten) Daten hängt von der Reihenfolge ab, in der sie angezeigt wurden, Aus- und Einblenden ändert Position in der Liste. Die Reihenfolge der Fitparameter (Issue #109) und in Shift/Scale ist deshalb ziemlich unvorhersehbar. Die Reihenfolge sollte der Reihenfolge der im Baum angezeigten Reihenfolge entsprechen.
dominik added the
Kind/Bug
Priority
High
 labels 2023-07-28 18:16:02 +00:00
dominik self-assigned this 2023-07-28 18:16:02 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Crash

This issue describes unexpected shutdowns or non-responsive behaviors

  
Kind/Documentation

Improves documentation

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New feature

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Priority
Very low
The priority is very low

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid isssue

  
Reviewed/Won't Fix

This issue won't be fixed

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Status
On Hold
This issue or pull request is on hold

  
Status
Stale
Issues without activity for more than 6 months

  
Type/BDS

Issues connected to BDS

  
Type/DSC

Issues connected to DSC

  
Type/Fit

Issue is connected to fitting data

  
Type/General

issue connected to general functionality

  
Type/NMR

Issues connected to NMR

No Label
Kind/Breaking
Kind/Bug
Kind/Crash
Kind/Documentation
Kind/Enhancement
Kind/Feature
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Very low
Reviewed
Duplicate
Reviewed
Invalid
Reviewed/Won't Fix
Status
Need More Info
Status
On Hold
Status
Stale
Type/BDS
Type/DSC
Type/Fit
Type/General
Type/NMR
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
dominik
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: IPKM/nmreval#111
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?