- edited description
Default color settings based on first opened file are retained for second opened file
USE CASE: WHAT DO YOU WANT TO DO?
Open a second file with its own default color settings
STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)
- Open Treeview
- Reset preferences
- Open Treeview
- Open John Matese's 11.cdt file
- Open the large_6kx6k.txt file
CURRENT BEHAVIOR
The values of the default color handles specific to 11.cdt (-3.85Red, -0.735Black, 2.38Green) are retained for the second opened file (large_6kx6k.txt) so that the matrix appears completely in shades of green. There is no way to determine the default colors & values of the file to correct the problem so that the colors appear the way you had previously viewed them unless you reset the preferences.
EXPECTED BEHAVIOR
The default colors and values should be re-determined with the new file's data instead of using the values that were determined from the previous file.
DEVELOPERS ONLY SECTION
SUGGESTED CHANGE (Pseudocode optional)
Not sure.
FILES AFFECTED (where the changes will be implemented) - developers only
Not sure.
LEVEL OF EFFORT - developers only
Not sure: major
COMMENTS
Comments (14)
-
reporter -
repo owner This really relates to the problem of #308. Loading a new file right now doesn't reliably reset all associated objects' state, evidently including Color classes.
-
- changed version to alpha04
-
reporter Hey @TreeView3Dev, is this still an issue with the changes to the preferences that came about from issue
#213? -
reporter - edited description
-
reporter Should we mark this issue as a duplicate of #308?
-
repo owner Due to
#213and pull request #62 this is all a bit tricky. I am currently working on color stuff for#414... might be about how some Preferences stuff works as well. #308 was, out of necessity, more or less addressed in the process of#213but I am not certain anymore how much it affects colors. -
reporter -
assigned issue to
I believe this will be addressed by another issue Chris is working on, and in looking for an issue to take, I figured I would mark such issues which are somewhat like duplicates as being worked on. It will make it easier for others to select an issue to take.
-
assigned issue to
-
reporter - changed component to Color settings
-
reporter - removed milestone
Removing milestone: Color settings (automated comment)
-
reporter - changed milestone to C - 01
-
repo owner - changed status to open
-
repo owner - changed status to resolved
-
reporter - changed version to beta2
- Log in to comment