I just want to say, until the developer can get around figuring out how to expose more touch controls....
....the controls we DO have access to now can go a lot further than you'd think. I am going to attempt to get everyone reading this thread on the same page. Please forgive me if I am being too obvious. This is currently how XBMC on touch devices like iPhone and iPad works:
We currently have five "hacks" for touch enabled controls to use with iPhone and iPad.
up, down, left, right, tap and double-tap.
The file keyboard.xml controls the following swipe actions:
up, down, left, right
The file mouse.xml controls the following touch actions:
tap and double-tap
----------------
Each of those controls can be configured to do something different, depending on which XBMC window is active.
For the swipe actions, you can control the result of it by editing the pertinent section of your keyboard.xml file.
Here is the key piece of info:
By default, some of those actions are "
wasted" the way they are mapped.
(No fault of the developer if you understand the unlaying problems/reasons.)
To elaborate, at the XBMC home screen:
-
Swipe left is wasted because it issues the "backspace" command. However, you are already at the top level, so it essentially does nothing.
-Similarly,
Swipe right issues the "tab" command, which toggles between "fullscreen" mode
(Gets you out of and back to your currently playing video). If you do not have a video running, this Swipe action is useless.
IMHO, is probably not used much by iPhone and iPad users
-
Doubletapping is also wasted as it issues the mouse command of "rightclick"
Now, to create some customization to tailor XBMC to behave more to your liking, simply edit the <home> section of the keyboard.xml file. The <home> section defines what commands each of the swipe action sends to XBMC to execute while at the homescreen.
For example:
Swipe left can be remapped to "Left"
Swipe right can be remapped to "Right"
Swipe up and down can stay with it's default mapping of "Up" and "Down".
DoubleTapping can be remapped to bring up the "Favorites" window.
Making those changes above makes navigating the XBMC GUI on the iPhone and iPad much useable at the homescreen. Of course, feel free to have those actions mapped to something else if you'd like. Since you are only editing
(or adding in the case of mouse.xml) the <home> section, those actions will only go into affect when you are at the home screen of XBMC.
---------
Taking this concept further, you can edit the <MyVideoFiles> to affect the actions when XBMC is in the video file mode.
Some more example sections that I like to customize myself are:
<FullscreenVideo> affects the touch controls while a video is playing in fullscreen.
My customizations...
Swipe left: skip forward 30 seconds
Swipe right: skip backwards 30 seconds
Swipe up: brings up the <FullScreenInfo> overlay
Swipe down: brings up the <VideoOSD> overlay
Single Tap: Pause/Play
Double Tap: Brings up menu (VideoOSD)
<FullScreenInfo> affects the touch controls when the movie artwork and seekbar is shown.
My customizations...
Swipe left: skip backwards 10 mins
Swipe right: skip forward 10 mins
Swipe up: close/exit the information overlay
Swipe down:
<VideoOSD> affects the touch controls when the menu is shown while the video is playing.
My customizations...
Swipe left: moves cursor left
Swipe right: moves cursor right
Swipe up:
Swipe down: close/exit the menu
Double Tap: Stop and Exit video
I could go on and on, but I hope you understand how to make those few touch events equal to more than just the default 4 actions, based on what window is onscreen.
Also, to clear up your confusion about double-tapping being inconsistent.
Ned Scott Wrote:Also, looks like double tap is sometimes back and sometimes contextual menu.
In the video list view (I am assuming this is the view you were talking about):
Double-tap on a element that has a context menu will pop up the context menu. i.e. double-tap a video title will pop up the context menu.
Double-tapping on any other area by default takes you back to the home screen.
----------------
Anyways, I feel like I am beating a dead horse at this poing. Hopefully that points you into the right direction. Understanding these concept fully, you can make the current "hacky" implementation of touch control, much more useable that you think. Combine that with a custom skin that mimic's Apple's GUI guidelines, the "need" for additional touch events becomes less and less necessary.
Let me know if I managed to lose you. I don't want to throw too much out at once. I can give more examples if you'd like. However, let us know if this spark any ideas for you to customize your XBMC to your specific need.
Good luck customizing to your heart's content! The XBMC project really is amazing.
cheers,
-Dazex