Reply to thread

Message

<blockquote data-quote="seco" data-source="post: 275585" data-attributes="member: 54595">My point being that the current behaviour is not what the &quot;normal&quot; user would expect.The normal user shouldn't have to know and understand what is the magic behind timeshifting and how it depends on users actions.For advanced users your explanation sounds reasonable enough, although hitting some button &quot;by accident&quot; and side effects caused by it imo shouldn't be a reason for this kind of behaviour. If losing the timeshift buffer should be prevented, a dialog box confirming the playback stop (and explaining that the timeshifting will be lost) should be sufficient. For those who know what they are doing, this confirm dialog could be disabled for good.As an advanced and normal user I feel that it is my duty to report this kind of misleading behaviour and suggest improvements&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="seco, post: 275585, member: 54595"] My point being that the current behaviour is not what the "normal" user would expect. The normal user shouldn't have to know and understand what is the magic behind timeshifting and how it depends on users actions. For advanced users your explanation sounds reasonable enough, although hitting some button "by accident" and side effects caused by it imo shouldn't be a reason for this kind of behaviour. If losing the timeshift buffer should be prevented, a dialog box confirming the playback stop (and explaining that the timeshifting will be lost) should be sufficient. For those who know what they are doing, this confirm dialog could be disabled for good. As an advanced and normal user I feel that it is my duty to report this kind of misleading behaviour and suggest improvements :) [/QUOTE]

Verification