Feedback on NI Community

cancel
Showing results for 
Search instead for 
Did you mean: 

Edit box Timeout

It's fundamentally wrong for the edit box to timeout and not allow you to post edits when you have finished typing them if you are outside the timeframe for edits.

 

I accept I shouldn't be able to Start a new edit, but I was just ediiting, and lost a message beacuse at the end when I clicked post it said I was too slow to edit. wrong wrong WRONG Smiley Mad

 

If you need to edit a message, and you are able to start something, you should be allowed to finish it unless you close the edit window and navigate away from the page.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
Message 1 of 8
(6,909 Views)
But you have a full 10 minutes to do so..
0 Kudos
Message 2 of 8
(6,908 Views)

muks wrote:
But you have a full 10 minutes to do so..

 

And I editted once with text, them thought a VI BD should be used to back it up, The second edit failed when I went to post.

 

I'm not complaining about the time, I'm complaining about the behaviour! - It's wrong!

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 3 of 8
(6,903 Views)

I would support the idea of increasing the time span that one is allowed to use for working on text, or remove the time limitation at all.

 

In real life it happens that one might want to check the documentation, the dictionary, ..., or get interrupted by a phone call etc., just to find out that the session has timed out and the written text has been lost.

 

I have suffered from this behavior several times, and it is annoying. My way out so far: Before pushing the 'post' button, 'cut' all the text. In case of timeout at least I can 'paste' the text in a fresh reply. Still, it is not convenient, sometimes I forget to 'save' my text by cutting, and you all know Murphy...

 

Message 4 of 8
(6,901 Views)

Wolfgang wrote:

I would support the idea of increasing the time span that one is allowed to use for working on text, or remove the time limitation at all.

 

In real life it happens that one might want to check the documentation, the dictionary, ..., or get interrupted by a phone call etc., just to find out that the session has timed out and the written text has been lost.

 

I have suffered from this behavior several times, and it is annoying. My way out so far: Before pushing the 'post' button, 'cut' all the text. In case of timeout at least I can 'paste' the text in a fresh reply. Still, it is not convenient, sometimes I forget to 'save' my text by cutting, and you all know Murphy...

 


WHen I am posting a big one or editing long, I do the cut-n-paste to notepad just to make sure. THe leason really sunk in after getting the message tht my 10,000 characters was too long... Never did re-post that one.

 

Re: the edit limit

 

THe limit is there because the forums use a mirror site so to realize an edit both sites have to be coordinated. So 10 minute was used as a reasonable compromise. Prior to that we could not edit any posts.

 

Ben

Message Edited by Ben on 05-10-2010 07:35 AM
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 5 of 8
(6,894 Views)

Ok, so currently the workaround is to copy the data to the clipboard/a file and paste in a new reply if a timeout has occured....

 

Why can't this be an automated process implemented by Lithium?

 either :

1) Post the edit,

or if timed out,

2) Post as a new reply instead of destroying all of the data we have taken so long to create. (with the header EDIT...)

 

Surely everyone wins this way

(Granted you have the potential for large duplicate posts in the same thread which may take up some space, but if people are already doing that anyway.. if you've spent x mins writing an edit are you going to spend anothery mins to edit the edit to make it look like a new post?)

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 6 of 8
(6,818 Views)

James W wrote:

Ok, so currently the workaround is to copy the data to the clipboard/a file and paste in a new reply if a timeout has occured....

 

Why can't this be an automated process implemented by Lithium?

...

 

James


[Insert tongue in cheek] 

 

Becuase Lithium ignores all of our requests and thinks they know best about what we need and want.

 

[Remove tongue from cheek]

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 7 of 8
(6,815 Views)

muks wrote:
But you have a full 10 minutes to do so..

 

In the work environment, when you post during breaks, and someone walks up and needs some help.... 10 minutes goes by really fast.
Richard






Message 8 of 8
(6,811 Views)