Active cell property should have a "Select all except header" option

[Mads]

In MultiColumn listboxes there is a very useful (but slightly hidden, I'm sure a lot of people do not know about it) option that allows you to set the properties of entire rows or columns in one go by setting the active row or column to -2. Similarily you can set the properties of the headers by setting the row to -1.

However, if you want to set the properties of all rows or columns *except* the header, there is no such shortcut available; you have to first use the -2 option, then use -1 to undo the action on the header...

Idea: Add a third shortcut (-3 ?) to select all except the header.

[GregSands]

Yes, I've needed that before.

[A-T-R]

Oh yes, please!!!!!!

[V_T_S]

Yes, it will be very useful.

[MGiacomet]

PLEEEASE, NI!!!

Wow! 5 years and nothing done by NI on such a simple yet powerful feature!

[dadreamer]

Almost 6 years, 52 kudos and still not implemented How does this Idea Exchange system work at all!?

[wiebe@CARYA]

> How does this Idea Exchange system work at all!?

It's not a democracy, but we can vote. Aka better then nothing.

[crossrulz]

If it were a democracy, this one would actually be pretty far down the list.  Of the new ideas, there are ~14 that have over 300 kudos.  Plus, let's just look at the shear number of ideas: of the "New" ideas there are ~284.

NI does not have unlimited resources.  NXG is a ground up new IDE that is taking up a bunch of those resources.  But it is an effort required in order to get to a bunch of these ideas.  There are some cool things coming down the pipe, and many of these ideas are looked at for each release.  But there are many reasons ideas are not implemented yet (limits in IDE, technically unfeasible, would break way too many other things, would suck up more resources than allowed to keep other more important things going, etc).  All we can do is put in our kudos to state our desire for a feature.  From there it is up to NI marketing and R&D to decide what goes into a release.

[dadreamer]

---

@crossrulz@crossrulz wrote:
If it were a democracy, this one would actually be pretty far down the list.

Then it would be more precise for NI to mark those unreleased ideas as "Low Priority", not "New" as it lasts from the very start. And it would be then more understandable for the rest of users, that NI staff saw the ideas and they are going to or planning to work on those (or just thinking of it sometimes).

---

@crossrulzcrossrulz wrote:

But there are many reasons ideas are not implemented yet (limits in IDE, technically unfeasible, would break way too many other things, would suck up more resources than allowed to keep other more important things going, etc). 

None of these reasons refers to why this concrete idea wasn't implemented. It's easy to put it into effect technically, it won't take a lot of a work time, won't break the existent functionality, won't waste LV resources too much and doesn't touch any IDE limits. Moreover it has two pieces of working code, that are just waiting to be combined into one feature.

Maybe there's a more prosaic reason - these MCL nodes are used rarely and the workaround is known, so no point to worry about. But it still would be good to see a more correct status for the ideas and some notice stating that 50 (100?) kudos don't provide a straight way for realization.

[wiebe@CARYA]

>Maybe there's a more prosaic reason - these MCL nodes are used rarely and the workaround is known, so no point to worry about.

I think the code of the MCL is 20 years old, and messing with it is probably avoided, especially since NXG will render them completely obsolete. 

There's usually not one reason why an idea is not implemented. The logic is fuzzy... How easy can we live without it? How much time to implement? How many people need this? Will there me negative side affects? Can they be predicted? How many other things are being developed? The list goes on for a while. If only a few of these answers lean towards the negative, it will have to wait until everything else is done/

It works the other way around to. Some ideas got <10 kudo's and did get implemented.

[crossrulz]

Adding to the list: Is anybody working in that code base this cycle?  I have been told the R&D groups like to rotate about the different sections of the LabVIEW code base based on bugs, desired features, and/or general optimization.  When those parts are being touched, R&D will look at the IE a little closer for any other things to fix/improve while they are already looking at that section of code.