[mythtv] [mythtv-commits] Ticket #1381: Slow keyboard response over network
Michael T. Dean
mtdean at thirdcontact.com
Sun Feb 26 01:27:41 UTC 2006
On 02/25/06 19:15, MythTV wrote:
>#1381: Slow keyboard response over network
>------------------------+---------------------------------------------------
> Reporter: anonymouse | Owner: ijr
> Type: defect | Status: reopened
> Priority: major | Milestone:
>Component: mythtv | Version:
> Severity: medium | Resolution:
>------------------------+---------------------------------------------------
>Changes (by mythtv at zacglen.com.au):
>
> * resolution: invalid =>
> * status: closed => reopened
>
>Comment:
>
> But isn't is quite possible that there is some flakey code which is
> causing keystroke events to only be processed after the select() times
> out? I very much think so.
>
>
While it's possible, the mere possibility of this does not warrant the
creation of a ticket in Trac. Until you *find* the "flakey code" (or at
least prove the existence of bad code in Myth), it's just
conjecture--not a bug.
> I also think it is a bit rich to close a valid ticket
>
Excuse me if I misinterpreted, but I think the point Chris was trying to
make by closing the ticket as "invalid" was that this is *not* a valid
ticket.
> without properly
> considering the validity of the complaint - and to just say it is
> unsupported. There are plenty of other users with similar problems.
>
And these users should discuss the issue on the mailing list until one
of you can find the bad code or at least prove that there is bad code in
Myth.
> And
> you cannot really just write-off the X-protocol - it was designed
> specifically to work in the way I am using it.
>
> No wonder MythTV is so bug-ridden.
>
<sarcasm>Yeah. If only the Myth devs could produce code of the same
quality as all that proprietary commercial code out there...</sarcasm>
Mike
More information about the mythtv-dev
mailing list