LabVIEW Idea Exchange

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

Add the property "Enable auto-scrolling" to indicators which have a scroll option

Status: New

It would be nice if controls/indicators that had a scroll option (most useful for vertical scroll) would have the ability to support automatic scrolling. This is useful for trace windows or long tables which are continually getting updates. At present we need to set the scroll position ourselves for every update.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
8 Comments
Ray.R
Knight of NI

This would be great.  It's a pain to wait for the properties window to pop up just because we want a scrollbar.

 

If it's not automatic, at least have it in the right click menu.  As a matter of fact, the choice for automatic should be in the Options.  But the right click menu selection should always be available.

AristosQueue (NI)
NI Employee (retired)

Ray: I think Mark is asking for a run-time feature, not an edit-time feature, such that if you have the scrollbar already visible and new text is written to the indicator that the text would automatically scroll to some position within the string.

 

Myself, I'm a strong fan of the behavior that I see in Visual Studio compiler log windows -- if the user has positioned the scroll thumb at the very bottom, when new text is added, the scroll thumb continues to stick to the bottom (thus always showing the tail of the log). But if I scroll up in the log, then new text is added keeping the scroll thumb in the same relative position so that I can actually read an interesting part of the log while the log continues to be updated. It's occassionally tricky to get the thumb back to the bottom of the log if the log is being updated very quickly, but overall, it's a system that works very well.

Mark_Yedinak
Trusted Enthusiast

Yes Steven, that is basically the type of behavior I would like to see. It is possible to do this today however it requires quite a bit of code on our end to accomplish it. This basic functionality should be part of the control/indicator freeing us to focus our coding efforts on solving the problem, not controlling minor but useful II functionality.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Ray.R
Knight of NI

Oops Sorry..

 

Maybe I should lookup to see if someone suggested what I was referring to 😉

 

And yes!!  Definitely kudos for this idea.  I agree that it's a lot of coding to accomplish what yor descibe at run-time..

X.
Trusted Enthusiast
Trusted Enthusiast

Kudo to Aristos' suggestion. The default suggested by Mark would be a pain for log (as in long log) strings, which indeed users may want to browse at their own pace (not necessarily concerned by what JUST happened).

 

Mark_Yedinak
Trusted Enthusiast

Actually what Stephen had suggested was what I had in mind all along. I just didn't capture the idea when I posted the idea. Fortunately he clarified the behavior that I am looking for.

 

BTW, X, why haven't you kudoed the idea yet?



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
eximo
Active Participant

Version 2011.11 🙂

-Regards

eximo
_______________________________________________
UofL Bioengineering M.S.
Neuronetrix

"I had rather be right than be president" -Henry Clay
Al1234
Member
Eximo - do you mean this can be done in Version 2011? Am I missing something? Thanks Al