(2019-04-25, 08:34)DarrenHill Wrote: @bsoriano - as you wish I'm pondering looking to add that line to the default keymap anyway, as I think it would be generally useful. Plus in any case I'll be keeping it in my set-up as the 2 finger right-swipe seems quite natural to bring that menu out anyway.

But having thought about it, if you do use it, it would be better to call it Amber.xml or something like that to be clear where it's come from for anyone who does use it.

(2019-04-24, 19:56)bsoriano Wrote:

(2019-04-24, 19:33)Raitsa Wrote: I like keeping things simple so I wish to not see the search option on my screen.
I tried enabling global search too but that did not remove the search from the main menu either, the search seems stuck on the main menu.

Any tips how to remove it?

Of course, go to Amber Settings, Home Layout and disable the Search main menu option. Did you try this and it did not work? Please let me know. Thanks.

Regards,

Bart  

(2019-04-25, 16:23)DarrenHill Wrote: @bsoriano - Something like that should work yes, as long as the python script can support both enable and disable (ie can both move the keymap xml file into the keymaps folder on enable and also remove it if disabled). But again there the file naming should be very specific to Amber to prevent any problems of overwriting or accidentally deleting something else (and the script being able to cope with files already existing or not being there if delete is requested).

I must admit I'm not sure if the blade menu is accessible with just a mouse (as of course most times you have the keyboard as well to just press left arrow to get it) - I'm planning to check that tonight under Windows. Just to see if button and right-swipe are both needed, although I guess having both options will do no harm if adding the button isn't too difficult, especially if they're both switchable.

If you're considering mouse-only support it might also be worth thinking about a back button as well? (two-finger left-swipe is already defined as back in the default touchscreen keymap). And maybe a home button two?

Perhaps have two toggles, one to enable/disable touchscreen blade support (the keymap change) and a second to enable/disable mouse support (show/hide mouse buttons for blade/view, back and maybe home)?

(2019-04-23, 18:58)Cyberdom Wrote: Hello everyone.

It's been years since I used Amber under Kodi Krypton.
I'm happy to see that this skin is compatible with Kodi Leia.
Congratulations on your work Bsoriano.

I installed it and it works properly apart from 2 or 3 things.

1) Would it be possible to decrease the scrolling speed for the summary of movies, series or music albums ? I find this speed is too fast on some pages.

2) I am French and there are still words or terms that are not translated into French.

3) It would be nice also to add an option to move down or up the shelf on the menus Movies, Series or Music instead it remains fixed in the middle of the screen.

4) I also use the add-on Tvheadend HTSP Client to watch TV and TV recordings. When I watch a TV recording, the logo of the recorded channel is not displayed (it is displayed with the Estuary skin). It would be nice if the channel logos are displayed while we watch a recording like watching live TV.
For the program guide, the information bar does not display the end time.

Thank you in advance for your answer.

(2019-04-25, 17:09)DarrenHill Wrote: @bsoriano - to be honest for the keymap I'd probably just follow the xonfluence route and silently add it at first run. My keymap version using the global level has the advantage that any other keymap which does use lower level tags (for specific windows, like your one) will override it. That said I couldn't see any definition using two-finger right swipe in the touchscreen.xml (wiki) file, which is the only one for touchscreen swipes anyway. Also if it's called Amber.xml it's towards the start of the alphabet, and keymaps are loaded in alphabetical order (with the last one overwriting any previously loaded ones).

Of course for most devices that don't have a touchscreen the whole thing is irrelevant anyway

Concerning buttons, I would perhaps use Estouchy or one of the other touchscreen-optimised skins (Retouched perhaps) as a guideline? There is also the Mousetuary variant of Estuary as another example.

I'd probably just group them together somewhere out of the way - probably towards one of the screen corners.

(2019-04-25, 23:08)Cyberdom Wrote: Thank you for the fix for issue 1.

For Tvheadend HTSP Client, here are the screenshots :

Screenshot with the playback of a recording under Estuary with the logo of the TV channel that appears and the end time :


Screenshot with Amber recording with the TV channel logo not showing :


Screenshot of a live TV channel with the TV channel logo displayed. The end time is not displayed but there is just the current time :

• They are maybe a little small for touch?
  
• The placement doesn't seem very obvious or natural in the centre of the top window bar, but I'm not sure what would be better without a free-floating set or something.
  
• It's very weird to only have back and home buttons on specific windows (the ones where the blade menu is available). If the buttons are enabled, I would perhaps show back and home on all windows (except the main top level one) and add the menu/settings button as now only when the menu is there to call up (although from the swipe testing trying to call the menu on other screens doesn't seem to do anything weird, at least where I tried).
  

(2019-04-26, 20:32)DarrenHill Wrote: @bsoriano - tried the touch buttons. They generally seem to be working, but there are a few comments:
 

• They are maybe a little small for touch?
  
• The placement doesn't seem very obvious or natural in the centre of the top window bar, but I'm not sure what would be better without a free-floating set or something.
  
• It's very weird to only have back and home buttons on specific windows (the ones where the blade menu is available). If the buttons are enabled, I would perhaps show back and home on all windows (except the main top level one) and add the menu/settings button as now only when the menu is there to call up (although from the swipe testing trying to call the menu on other screens doesn't seem to do anything weird, at least where I tried).
  

 

(2019-04-26, 21:00)DarrenHill Wrote: I tried with just mouse only, and there currently is no way to bring the blade menu up that way that I can see (right click does back).

I'll have a look later and see if I can come up with any suitable keymapping for a mouse that would be the equivalent of the two finger swipe right on touchscreen. If there is then perhaps going that route could be an option, but if not it's a question of how many people actually exclusively use mice for controlling Kodi. I know it's not an unknown scenario, but it's a rare one.

xml:
<?xml version="1.0" encoding="UTF-8"?>

<keymap>

    <addonbrowser>

        <touch>

            <swipe direction="right" pointers="2">Menu</swipe>

        </touch>

        <mouse>

			<middleclick>Menu</middleclick>

        </mouse>

    </addonbrowser>

	<music>

        <touch>

            <swipe direction="right" pointers="2">Menu</swipe>

        </touch>

        <mouse>

			<middleclick>Menu</middleclick>

        </mouse>

    </music>

    <videos>

        <touch>

            <swipe direction="right" pointers="2">Menu</swipe>

        </touch>

        <mouse>

			<middleclick>Menu</middleclick>

        </mouse>

    </videos>	

    <pictures>

        <touch>

            <swipe direction="right" pointers="2">Menu</swipe>

        </touch>

        <mouse>

			<middleclick>Menu</middleclick>

        </mouse>

    </pictures>	

    <games>

        <touch>

            <swipe direction="right" pointers="2">Menu</swipe>

        </touch>

        <mouse>

			<middleclick>Menu</middleclick>

        </mouse>

    </games>

	<weather>

        <touch>

            <swipe direction="right" pointers="2">Menu</swipe>

        </touch>

        <mouse>

			<middleclick>Menu</middleclick>

        </mouse>

    </weather>

	<programs>

        <touch>

            <swipe direction="right" pointers="2">Menu</swipe>

        </touch>

        <mouse>

			<middleclick>Menu</middleclick>

        </mouse>

    </programs>

    <contextmenu>

        <mouse>

            <rightclick>back</rightclick>

        </mouse>

    </contextmenu>

</keymap>