2012-12-01, 19:45
Yeah there's no real naming rule. That's why you should always look at the actual definitions and not just guess based on the name
(2012-12-02, 18:46)claymic Wrote: - Container.NextViewMode and previous view modeAre those info labels or an action? If they are info labels you can use XBMC.GetInfoLabels.
(2012-12-02, 18:46)claymic Wrote: - simulate SendClick(14) to hide or show watched filesHm is 14 the ID of the show/hide watched button in the skin you are using? Because I don't know of any action that does this in XBMC. If it's skin specific JSON-RPC doesn't support it.
(2012-12-02, 18:46)claymic Wrote: Another question, where i can find the parameters for GUI.ActivateWindow ?
p.s maybe i understand now how to use the GUI.ActivateWindow , if i want to open the window movie sets i just have to use MovieSets like a parameter, i will test.
(2012-12-02, 20:44)Montellese Wrote: Are those info labels or an action? If they are info labels you can use XBMC.GetInfoLabels.I use this like a http command To change view modes in the skin.
Quote:CF.send("Xbmc", "/xbmcCmds/xbmcHttp?command=ExecBuiltIn(Container.NextViewMode)");
(2012-12-02, 20:44)Montellese Wrote: Hm is 14 the ID of the show/hide watched button in the skin you are using? Because I don't know of any action that does this in XBMC. If it's skin specific JSON-RPC doesn't support it.I just search in this page https://github.com/xbmc/xbmc/blob/master...ilib/Key.h , tried in my xbmc and works very well, hide or show the watched movies or tvshows in xbmc, but i send this like a http command too:
Quote:CF.send("Xbmc", "/xbmcCmds/xbmcHttp?command=ExecBuiltIn(SendClick(14))");maybe its specific for the skin, i will try to find another way to do this, there is anyway to simulate SendClick with JSON ?
(2012-12-02, 20:44)Montellese Wrote: Yeah those are not very well documented AFAIK. Basically you need to open the video window and e.g. pass in MovieSets or MovieGenres etc. The video-related parameters can be found in xbmc/video/windows/GUIWindowVideoNav.cpp.I found the windows here http://wiki.xbmc.org/index.php?title=Ope...nd_Dialogs, works nice for me.
(2012-12-02, 23:00)gertjanzwartjes Wrote: However, there are a quirks with the new SendText and OnInputRequested. First of all, you don't get an input requested when you move onto an input box, without actually pulling up the virtual keyboard in XBMC. For example try the username/password setting in the Webserver settings pane. You can edit this box without going into the virtual keyboard window, but there's no OnInputRequested notification when moving onto that input. Is there a way to get and OnInputRequested notification here too? Or is not getting the notification by design?Thanks for the report, I'll look into how feasible this is for normal controls (i.e. not keyboard dialogs).
(2012-12-02, 23:00)gertjanzwartjes Wrote: Also, when you do send a SendText method while in that particular screen, it will fill out _all_ text boxes (i.e. port, username and password). It works that way for all screens that have multiple input boxes. I guess that's a bug?Yup it is and it should be fixed with https://github.com/xbmc/xbmc/commit/2efa...872f531ab0. Thanks for mentioning it.
(2012-12-02, 23:00)gertjanzwartjes Wrote: However, there are a quirks with the new SendText and OnInputRequested. First of all, you don't get an input requested when you move onto an input box, without actually pulling up the virtual keyboard in XBMC. For example try the username/password setting in the Webserver settings pane. You can edit this box without going into the virtual keyboard window, but there's no OnInputRequested notification when moving onto that input. Is there a way to get and OnInputRequested notification here too? Or is not getting the notification by design?
(2012-12-03, 01:09)Montellese Wrote: Yup it is and it should be fixed with https://github.com/xbmc/xbmc/commit/2efa...872f531ab0. Thanks for mentioning it.No prob, and thanks for fixing it!
(2012-12-03, 09:36)Montellese Wrote: OK I've had a quick look at this and here is the problem: Let's say xbmc sends a OnInputRequested notification everytime a user focuses an edit control and an OnInputFinished notification when the user unfocuses the edit control. Here is what can happen:It's indeed not trivial. What about this flow:
IMO that's not very intuitive behaviour as you get two OnInputRequested notification and you get an OnInputFinished notification even though you are still in a control that accepts text input. I'm not sure what the best solution would be.
- User focuses edit control -> OnInputRequested notification
- User presses enter -> virtual keyboard dialog opens -> another OnInputRequested notification
- User enters some text and then closes the dialog -> OnInputFinished notification
- User is still focused on the edit control
- User leaves the edit control -> OnInputFinished notification