From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Feedback on NI Community

cancel
Showing results for 
Search instead for 
Did you mean: 

Lock old threads

Solved!
Go to solution

Threads should be automatically locked after a reasonable amount of inactivity. I would say 6 months to a year.

 

That would stop people from restarting a 7 year old thread when they have a similar problem.

 

Case in point http://forums.ni.com/t5/LabVIEW/Can-I-set-XonLimit-and-XoffLimit-for-serial-port-communication/td-p/... thread from 2007 brought back from the dead then manually splitt off to a new thread, http://forums.ni.com/t5/LabVIEW/Re-Can-I-set-XonLimit-and-XoffLimit-for-serial-port/td-p/3617453

 

 

========================
=== Engineer Ambiguously ===
========================
Message 1 of 98
(10,941 Views)

Hello RTSLVU,

 

Thank you for your input. We agree with you in regards to having topics locked down after a certain amount of time.

We are looking to implement this when priority allows it.

 

Thanks,

Karina Barles
NI Community Support

0 Kudos
Message 2 of 98
(10,897 Views)

It could also be a soft barrier that whenever somebody replies to an old thread, there should be a warning, alerting the poster to that fact and recommend to start a new thread.

0 Kudos
Message 3 of 98
(10,895 Views)

I agree with altenbach.  There are times when I would make a thread asking a question, and there would be work arounds at the time on how to do it, and I might even mark the post as a solution.  Then years later a new feature in LabVIEW may make that work around not necessary so I could see posting a reply stating that the new method works better.  I could make an entire new thread, linking to the locked one, but that feels disjointed especially if someone finds the old thread in a search, which wouldn't link to the new one.

Message 4 of 98
(10,889 Views)

Another reason to keep older threads unlocked:

 

http://forums.ni.com/t5/LabVIEW/Network-Stream-memory-leak-with-cluster-of-arrays/m-p/3617932#U36179...

 

It is nice when someone finds an older thread that really helped them and they take a moment to thank the contributors.

0 Kudos
Message 5 of 98
(10,885 Views)

Here's another instance where resurrection was beneficial.

 

I happened to find that one in a (Google) search, but I see the resurrection helped Hooovahh

--
Tim Elsey
Certified LabVIEW Architect
0 Kudos
Message 6 of 98
(10,879 Views)

This thread is a perfect example of why old threads should be locked 

http://forums.ni.com/t5/LabVIEW/keep-moving-a-text-like-marquee-display/m-p/3622393/highlight/false#...

 

@altenbach wrote:

Well you found a 15 year old thread (!!) and that old example seems overly complicated.

 

Here's probably all you need:

 

 

To speed it up further, multiply [i] by a small integer. To make it run right-to-left, just negate [i] (or multiply by a negative integer).

 

 

 

A new question on a similar issue can always reference the closed thread.

========================
=== Engineer Ambiguously ===
========================
Message 7 of 98
(10,812 Views)

Hello Team,


Thank you for providing examples! This is of much help.

 

Thanks,

Karina Barles
NI Community Support

0 Kudos
Message 8 of 98
(10,803 Views)

13 year old thread brought back from the dead.

 

Everyone's first response was "Why are you posting to a 13 year old thread?" 

 

Then it was split into a new thread by a moderator.

 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 9 of 98
(10,478 Views)

A pretty good contender, but the 15 years, 10 months, 1 week, and 5 days still is the winner.  With an honorable mention for 15 years, 3 months where NI replied.

Message 10 of 98
(10,474 Views)