Thread Locking

[DGSketcher]

I appreciate the intent of thread locking and I do support it in principle, but I think the 12 month inactive locking rule is a bit quick in the big scheme of AC development. Comments made on AC27's release could be locked when AC28 turns up, but I note from past comments some users actually delay deployment of AC by a year to avoid bugs. Those users may then connect with the old problem and not be able to discuss the related issue. Personally I would have thought a minimum two year lock window was more realistic.

I also think it is perhaps inappropriate to be locking the wishes threads. There are ideas in those threads that are still being requested and commented on after MANY years. Allowing further comments allows users to highlight how long the missing idea has been requested or how it could be adapted in more recent versions of AC. If a wish is solved (or implemented in an update) then lock them, but until then I feel we should be allowed to continue commenting. 

[Noemi Balogh]

Thank you for your feedback. The current 1-year period is something we agreed together with the Moderator team, but of course, we can revisit any time. Please note that the 1 year is counted from the last activity - if people keep posting on a thread - in your example, about Archicad 27 - then this thread won't be locked. In case you experience different behaviour, please let me know.

About the Wishes board, I understand your point, but in my personal opinion when a thread is abandoned for years, it is better to start a fresh one, so the topic gets its visibility. Previous threads will be available in the system and it can be tracked down anytime later.

What I would like to ask is that we give it a try - if in a couple of months we see this leads nowhere good, I can adjust the system.

Thank you again and I hope you can find some good improvements too in the recent changes.

[Lingwisyer]

Given the entire Developer Forum has been locked, where are GDL questions supposed to be asked? And I guess API questions get pushed over to the archicadAPI site, though I do not recall there being a place there either...

[Noemi Balogh]

@Lingwisyer good catch, I forgot to unlock it. Now you can use it again.

[furtonb]

I just want to echo @DGSketcher 's opinion, I wondered why all of the threads are locked regarding door/window glazed area calculation – I found threads going back 5 years which could be continued today as no visible improvement happened since then (using AC26). I though my e-mail address is not verified, or something like this.

I don't really see any reason to lock any threads apart from really long and chaotic ones, because it just scatters information for the occasional user and increases the barrier of entry: if I had to just make a comment, I would've, but starting from scratch with proper referencing to previous discussions takes more time, that one might not have at a current moment.

Can you please reconsider this decision and increase the time window before locking?

[thesleepofreason]

---

@DGSketcher wrote:

I also think it is perhaps inappropriate to be locking the wishes threads. There are ideas in those threads that are still being requested and commented on after MANY years. Allowing further comments allows users to highlight how long the missing idea has been requested or how it could be adapted in more recent versions of AC. If a wish is solved (or implemented in an update) then lock them, but until then I feel we should be allowed to continue commenting. 

---

To this it should be noted that locking also supresses the thumb functionality which however pathetic is the only way for individual users to on their own share their needs and wants due to GS inability to deliver on the long promised new wish functionality. I have a really hard time seeing the user benefit from locking wish threads.

[Eduardo Rolon]

Just to add an example of a 2016 thread that got a new question:

https://community.graphisoft.com/t5/Visualization/Exploded-axo-view/m-p/394492#M24375