Reply to thread

Message

<blockquote data-quote="dir" data-source="post: 374408" data-attributes="member: 24485">No problem.&nbsp; I won't perservere after this message.&nbsp; But I think there's a different perspective here that's causing the disagreement.&nbsp; You said:But that's totally irrelevant for these reasons:-&nbsp; &quot;The title changes&quot;, yes - but you have to know that the title changed.&nbsp; If you're not frequently reading (i.e. a new user, or a user that hasn't used this plug-in before and thus hasn't paid attention to the fact that it used to be called something else), then you won't know the title's simply updated.&nbsp; You'll have to assume it's new, since it includes things like &quot;New!&nbsp; Version x Released&quot; or similar.- &quot;The thread is marked as having unread messages&quot; - I don't see how this improves things at all.&nbsp; Any threads listed in the New Posts view has unread messages, and there's no way to know how many unread messages there are.&nbsp; There could be 350 out of the 356 listed that are unread, indicating a really HOT subject.&nbsp; Or there could just be one unread. - &quot;The last message gives you all the details&quot; - no, it doesn't, once another message has been posted.&nbsp; Normally, you have to go back several messages, if not several pages, to find the post that says a new version has been released.&nbsp; &quot;For The Record has it's own forum&quot; - yeah, well, ok, true.&nbsp; But it's pretty unlikely that a user will use yet another forum just to track one MediaPortal plugin.&nbsp; I certainly won't, unless I can't find a solution to my problem here and there's no other choice.And I know that the console will inform of a new version.&nbsp; I'm not arguing that it's difficult to know when a new version is released, I'm arguing that as a forum reader, it's frustrating to have threads that are hundreds of posts long, with 99% of the posts related to previous versions and thus not useful and possibly harmful.&nbsp; It's EXTREMELY frustrating as a user to find a new plugin to try out, install it, have problems, then go to the forum to look for answers, only to find a single post with 300+ messages in it.&nbsp; You start at the beginning of the thread and start reading, hoping to find tidbits that might provide insights into what you're doing wrong.&nbsp; You see a few suggestions, try them out, and keep reading and trying.&nbsp;&nbsp; Since you're trying to be a &quot;good&quot; forum user, you don't immediately post a question asking for help, since it's usually safe to assume that someone has already had the problem already and the answer lies within thread (and you don't want the wrath of the regulars' scorn when they tell you to read the forum; &quot;that questions' been answered 20 times already&quot;.Eventually, you've tried 3 or 4 suggestions/fixes, including installing (old) .dlls, scripts, skins, versions, etc. and get your system so screwed up there's no way to know what's causing what problems.&nbsp; Eventually you work out that all those suggestions were dated 18 months ago and related to an old version that has been updated 3 times already.I've been there heaps of times, and I've been working on these things for 5 years, so I'm no n00b.I just don't see the point of keeping a single thread to track numerous versions of something.&nbsp; BUT:&nbsp; this statement kills my argument completely, which is why I'll shut up now:Fair 'nuff!</blockquote>

[QUOTE="dir, post: 374408, member: 24485"] No problem. I won't perservere after this message. But I think there's a different perspective here that's causing the disagreement. You said: But that's totally irrelevant for these reasons: - "The title changes", yes - but you have to know that the title changed. If you're not frequently reading (i.e. a new user, or a user that hasn't used this plug-in before and thus hasn't paid attention to the fact that it used to be called something else), then you won't know the title's simply updated. You'll have to assume it's new, since it includes things like "New! Version x Released" or similar. - "The thread is marked as having unread messages" - I don't see how this improves things at all. Any threads listed in the New Posts view has unread messages, and there's no way to know how many unread messages there are. There could be 350 out of the 356 listed that are unread, indicating a really HOT subject. Or there could just be one unread. - "The last message gives you all the details" - no, it doesn't, once another message has been posted. Normally, you have to go back several messages, if not several pages, to find the post that says a new version has been released. "For The Record has it's own forum" - yeah, well, ok, true. But it's pretty unlikely that a user will use yet another forum just to track one MediaPortal plugin. I certainly won't, unless I can't find a solution to my problem here and there's no other choice. And I know that the console will inform of a new version. I'm not arguing that it's difficult to know when a new version is released, I'm arguing that as a forum reader, it's frustrating to have threads that are hundreds of posts long, with 99% of the posts related to previous versions and thus not useful and possibly harmful. It's EXTREMELY frustrating as a user to find a new plugin to try out, install it, have problems, then go to the forum to look for answers, only to find a single post with 300+ messages in it. You start at the beginning of the thread and start reading, hoping to find tidbits that might provide insights into what you're doing wrong. You see a few suggestions, try them out, and keep reading and trying. Since you're trying to be a "good" forum user, you don't immediately post a question asking for help, since it's usually safe to assume that someone has already had the problem already and the answer lies within thread (and you don't want the wrath of the regulars' scorn when they tell you to read the forum; "that questions' been answered 20 times already". Eventually, you've tried 3 or 4 suggestions/fixes, including installing (old) .dlls, scripts, skins, versions, etc. and get your system so screwed up there's no way to know what's causing what problems. Eventually you work out that all those suggestions were dated 18 months ago and related to an old version that has been updated 3 times already. I've been there heaps of times, and I've been working on these things for 5 years, so I'm no n00b. I just don't see the point of keeping a single thread to track numerous versions of something. BUT: this statement kills my argument completely, which is why I'll shut up now: Fair 'nuff! [/QUOTE]

Verification