[mythtv-commits] Ticket #9537: MediaMonitor JumpTo plugin broken in commit ed4d961aed836fade236d006b2797f0c044970de
MythTV
noreply at mythtv.org
Mon Jan 31 18:27:08 UTC 2011
#9537: MediaMonitor JumpTo plugin broken in commit
ed4d961aed836fade236d006b2797f0c044970de
-------------------------------------------------+-------------------------
Reporter: Lawrence Rust <lvr@…> | Owner: stuartm
Type: Bug Report | Status:
Priority: minor | accepted
Component: MythTV - General | Milestone: 0.25
Severity: medium | Version: Trunk
Keywords: | Head
| Resolution:
| Ticket locked: 0
-------------------------------------------------+-------------------------
Comment (by Lawrence Rust <lvr@…>):
Having some kind of autoplay is, I believe, essential. Given that, then
the current implementation (with some minor tweaks) works but is clunky
and limiting. Allowing a plugin to install some kind of general event
handler/filter is more generic but could be a significant code change. One
has to look at the cost/benefit analysis. What are the benefits of
changing? How much code/time will this add?
The call to JumpTo?("MainMenu?") isn't so terrible. At that point the user
has enabled "Jump to plugin" and is expecting Myth to start a compatible
handler after inserting new media. Jumping to main menu unravels anything
going on, releasing memory and devices, and provides a clean exit point
for the new plugin. It's questionable though if one plugin should
interrupt another or whether autoplay should be disabled while watching
live TV.
I sense that you have an agenda to change this but I haven;t seen the
benefits yet. Can you explain?
--
Ticket URL: <http://code.mythtv.org/trac/ticket/9537#comment:3>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list