LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
komorbela

Project explorer should remember expanded and selected Items

Status: Declined

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.

When I work with well structured and big projects, I usually have to expand numerous folders/items to get to the point I am interested in. Usually it is close to the item I was interested in last time I opened the project.

I propose to have an option for the Project Explorer to remember the expanded/collapsed statuses of the items and also the selected items.

 

 

Proposed functionality:

 

before closing: before close ->> after opening: after open

 

 

Current status:

 

before closing: before close ->> after opening: after open

 

8 Comments
jcarmody
Trusted Enthusiast

I like the idea, except for the "option" part.  Either make it the default behavior or leave it out, IMO.

Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

RavensFan
Knight of NI

I don't see any reason for the idea to remember the "selections".  Selections are a temporary thing that are designed to allow you to take actions on specific items.  I don't see why they need to be remembered between programming sessions.

Intaris
Proven Zealot

Especially when multiple developers work on a project and the .lvproj needs to be committed at times.... I don't want other people's selections slapping me in the face.

TurboPhil
Active Participant

Agree with Intaris. Seems like it would result in a lot of "changes" to the lvproj file (unless somehow it got saved elsewhere, like in some local LV preferences file...).

X.
Trusted Enthusiast
Trusted Enthusiast

Doesn't this bug you first and foremost though? I just can't stand it anymore...

komorbela
Member

Thanks for all the comments! I have to admit I didn't think about the use case of multiple developers working on the same project.

 

I already have some ideas how the refine this idea, but I wait some more comments and will try to suggest a system that fits most of us.

Norbert_B
Proven Zealot

It's not with multiple developers on the same project. It starts with a single developer already...if the settings are stored in the lvproj-file.

If not, settings are not "recalled" when using different PCs from time to time.

 

Also, storing that info always blows up memory usage of files, hence increased loading times (most often negligible though...).


I think source code control is the first and foremost point for declining this idea.

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.