Opened 14 years ago

Closed 14 years ago

#1169 closed defect (fixed)

NetworkControl: query location doesnt work properly

Reported by: Webmaaschter - a t - gmx.de Owned by: cpinkham
Priority: minor Milestone: 0.20
Component: mythtv Version: head
Severity: low Keywords: NetworkControl query location
Cc: Ticket locked: no

Description

If you login via telnet, the command "query location" doesn't give always the right output. Even if you are in the vidoebrowser or listening to musik it gives back: "MainMenu?"

Just a litle example of what is happening:
# jump playmusic
OK
# query location
MainMenu?
# jump videobrowser
OK
# query location
MainMenu?

Infos:
Library API version: 0.19.20060121-2
Source code version: 8795M

Change History (4)

comment:1 Changed 14 years ago by cpinkham

Milestone: 0.20
Severity: mediumlow

Moving this to .20 milestone, it is a known issue and I think was documented in the commit log when NetworkControl? was added. The "query location" only works with mythfrontend, it does not currently report the location when using plugins. I may get to this before 0.19 is out, but it is not a showstopper so I'm marking this as 0.20.

comment:2 Changed 14 years ago by cpinkham

Resolution: fixed
Status: newclosed

(In [8852]) Fix NetworkControl?'s "guery location" command when the location is a plugin by setting the location to the plugin's name or the plugin's name plus "setup" when configuring a plugin. Closes #1169. Further patches may implement more detailed locations within the plugins, but this should suffice for now.

comment:3 Changed 14 years ago by anonymous

Resolution: fixed
Status: closedreopened

Sorry, but i've got the same problem with Revision 8908. I mailed to Webmaaschter and he still have the same problem.

# jump videogallery
OK
# query location
MainMenu?
# jump playmusic
OK
# query location
MainMenu?

Info:mythfrontend --version Library API version: 0.19.20060121-2 Source code version: 8908M

comment:4 Changed 14 years ago by cpinkham

Resolution: fixed
Status: reopenedclosed

This was fixed and should have been closed pre-0.19.

Note: See TracTickets for help on using tickets.