Search Issue Tracker

By Design

By Design in 6000.6.X

Votes

0

Found in

6000.5.0a9

6000.6.0a1

Issue ID

UUM-136912

Regression

No

Lighting Search column layout is not persisted and Reset search result columns removes default editable Light columns

Search

-

Steps to reproduce:

  1. Create a new project using Universal 3D template
  2. Go to Windows > Rendering > Lighting Search
  3. Add any new columns or reorder the existing columns
  4. Close and reopen the Lighting Search window
  5. Observe that the columns are reset to their default layout
  6. Click on the spinning arrow/"Reset search results column." icon
  7. Observe the search window 

Actual results: Lighting Search resets the customised column layout on reopen, and using "Reset search result columns" removes the default Light columns

Expected results: Lighting Search preserves the customized column layout between sessions, and "Reset search result columns" restores the default editable columns for the current query without breaking their interactivity

 

Reproducible with versions: 6000.5.0a9

Can’t test with versions: 6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a7 (Lighting Search Window with such columns not available)

 

Tested on (OS): Windows 11

Notes:

  • Using the “+” button to add back a previously editable column (e.g. Light Type) after pressing Reset results in that column no longer behaving as it did before (interactivity is lost)
  • The Global Search does not reset columns once reopened; therefore, it seems inconsistent
  1. Resolution Note:

    - By default we do not save the state of SearchWindow opened through "custom means". We persist the state of the Global search window.
    Workaround:
    - If the Rendering team thinks the state should be persisted, it should be implemented directly in the Lighing Explorer tool.
    - Alternatively: if a user wants to persist some column layout changes, it is up to that user to start with a known query, tweak it and then save this tweaked query as a new Project query.

  2. Resolution Note (6000.6.X):

    - By default we do not save the state of SearchWindow opened through "custom means". We persist the state of the Global search window.
    Workaround:
    - If the Rendering team thinks the state should be persisted, it should be implemented directly in the Lighing Explorer tool.
    - Alternatively: if a user wants to persist some column layout changes, it is up to that user to start with a known query, tweak it and then save this tweaked query as a new Project query.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.