SquireBum

pwalpwal
 
just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)

When the thread is related to Early Release posts in the Problem Reports forum, I think Jim Lima locks the report to indicate that he has either reported the problem to the developers or the user has solved the problem.  Locking indicates that Jim or someone else from Cakewalk no longer has to review that problem when reviewing the list of Early Release issues in the forum.
 
-- Ron

fair enough, seems like a reasonable thing to do
 
took a quick browse of that forum: has he only just (the last few days) started doing this, or are all the not-locked threads still "not seen yet"?

pwalpwal

SquireBum

pwalpwal
 
just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)

When the thread is related to Early Release posts in the Problem Reports forum, I think Jim Lima locks the report to indicate that he has either reported the problem to the developers or the user has solved the problem.  Locking indicates that Jim or someone else from Cakewalk no longer has to review that problem when reviewing the list of Early Release issues in the forum.
 
-- Ron

fair enough, seems like a reasonable thing to do
 
took a quick browse of that forum: has he only just (the last few days) started doing this, or are all the not-locked threads still "not seen yet"?

If you go back far enough in the Problem Reports forum to view Early Release problems for the last few months, you can see that Jim has been locking posts for Early Release problems as he addresses them.  These issues seem to always be addressed in the next release.  I can't answer for the "not-locked" posts, because I find that sometimes the problem may be fixed in the next release or it may not be fixed.
 
--Ron