Posts: 1,506
Joined: Nov 2013
you find completely untested attempts at two of these
https://github.com/notspiff/kodi-cmake/c...d372fde293
control.autoScroll(delay, time, repeat)
https://github.com/notspiff/kodi-cmake/c...bcc91573f5
list_of_selected_labels = dialog.select(stuff, multiselect=True)
Posts: 1,506
Joined: Nov 2013
second returns a list of the labels, not a list of indices.
yes, they are not in mainline, only my fork. and no, i won't do anything to get them into mainline. but if somebody else wants to that is their business..
Posts: 7
Joined: Sep 2014
Reputation:
0
2014-12-01, 15:52
(This post was last modified: 2014-12-01, 15:55 by sai7.)
I have one problem.
I want to focus control Textbox while doing navigation.
How to show that textbox is selected ?
I used Control edit, but its editable.
and I want to display non editable box.
So I used Enabled=false, but its not going to focus able.
So I am using textbox, but its not going to focus.
Posts: 4,058
Joined: Oct 2007
Reputation:
89
zag
Team-Kodi Member
Posts: 4,058
Cool, i'm currently writing some getting started guides for Kodi python programming.
I might look at including this as its really hard for the new developer to learn skinning as well as the add-on stuff.
Posts: 43
Joined: Jan 2014
Reputation:
0
pieman
Junior Member
Posts: 43
Hi Roman_V_M,
Read through the full thread and looked at your start up guide but I am getting dependency issues when trying to install the demo in Gotham 13.2 on RaspBMC.I added the module first from the official repositories. Your zip file doesn't look to be right so I unzipped it and then just zipped up the inner directory. Gotham then gives dependency issues. I have added your files manually to my system and have the demo up on screen now.
You might want to look at the zip structure and dependencies.
Posts: 19
Joined: Apr 2014
Reputation:
0
Dear Roman_V_M,
considering that only this afternoon I started with playing around with your demo application I managed to chenge it left and right and also add functions to it that controls my hardware. I think it is rightfully added to the official XBMC repo as it greatly simpifies creation of addons (which in turn will make Kodi even more popular).
Is I feel I have grasped the basics, when it comes to classes and the initialisation of them I have been able to create a second window that pops up, but controlling controls seem to be messed up.
Would it be possible to extend you demo addon code with a very simple second, child dialog window with a simple control (eg. close button)? I could take it from there. As I have seen another post in this thread also about a second window (although that is a mix-up of pyXBMCt and xbmcgui) I feel that there may be other users that would appreciate this. I certainly would!
Thanking you anyway for this great addition to the world of Kodi!
Regards, MGA.
Posts: 19
Joined: Apr 2014
Reputation:
0
Well that's a quick reply! Shouldn't you be enjoying the weekend? ;-)
I prefer your first proposal; only one window should be in focus anyway and since the window is not closed this sounds ok to me. Your second proposal sounds like a 'if I cannot do it properly I will do it anyway' which is not in line with my taste...I'd like to stick with one way of creating all my windows in an addon and it will be pyXBMt then!
Still my second question would remain -and will try myself in the meantime- to add this 'switching between two windows by toggling visibility' functionality to the demo addon?
What would be the main difference between the main MyAddon(AddonDialogWindow) class and the second one? I tried the same structure in an earlier attempt but suspect it crashing on the __init__ part super(MyAddon, self).__init__(title) that leads to a conflict with the first?
Thanks a ton for thinking along (hm rhimes, must be the time of year!)
Regards, MGA
Posts: 19
Joined: Apr 2014
Reputation:
0
Hi Roman,
you are right. I am the first person to admit that I am not an experienced programmer, but usually picks up quickly from other examples. I have now added a second window by copying the main window class (and renaming it ofcourse). In the second window I have added:
self.connect(ACTION_NAV_BACK, self.gobacktomain)
to the __init__ function whereas GoBackToMainWindow contains:
self.close()
window = MainWindow('Main Window')
window.doModal()
Selecting a button in the main window startt the second window like:
self.close()
childwindow = SecondWindow('Second Window')
childwindow.doModal()
This looks like what you mean and indeed works like a charm!
And on the way I get more experienced working with classes ;-) The more you know the more you know you do not know I believe is what they say...
Regards, MGA