Hey guys, and David.
This was my first time today playing with the iBus and Centrafuse (First time with iBus period).
I've found some interesting items that may help you (and possibly others) get over this hump of Ibus/Centrafuse integration.
First off, I made sure to do some testing outside of centrafuse, works well -- just like others have said.
Here's the fun part. Like others I tried to simplify the comand by using "U" for steeringwheel UP and "D" for Steeringwheel down.
I CAN CONFIRM CENTRAFUSE GETS THE COMMANDS!
When I got into hotkeys and record the buttons, it does indeed record (Shift+U) and (Shift+D) as the Up/Down buttons pressed. That's good.
Now, it still will NOT do volume up or down ... however it gets better.
To test if the buttons were getting into any type of interaction mode with Centrafuse, I opened up the Web app (I have no connection, I just wanted to get to a place in Centrafuse that would allow me to 'press' the buttons and see what's being exported -- such as the URL for a website).
AND IT WORKS! -- Kinda.
Example:
If I am in the keyboard mode for entering a URL, I press the Up button, and sure enough a U (Capital U) is displayed in the search bar.
However If I press it again, nothing displays.
If I press the Down button, nothing displays.
UNTIL I physically touch the screen somewhere. Then the button works again.
So, if I want to type UDUD in the URL bar, I have to do the following:
[Press U button], Touch Screen, [Press D button], Touch Screen, [Press U button], Touch Screen, [Press D button]
This brings up Few interesting issues...
1) If I were to 'hold' the U button, it should repeat the keystroke over and over according to the default .ini file with 11miliseconds inbetween. But it does not. It only takes the first press and almost seems as if it goes out of focus, not allowing other keys to be pressed
2) Centrafuse is showing signs that it can receive commands, both setting up the hotkeys for mapping, and in the mannor I showed above... so why will the volume up/down not partially receive anything?
3) I'm pretty certain CaSe is sensative, because when I specify "D" in the .ini, Centrafuse interprets that as (Shift+D) -- this may have some affect on interaction
I really didn't set up much else in the way of tweaking the .ini file, but the following are the only lines I modified, in the format "From" > "To"
Code:
SetMinimized=False > SetMinimized=True
ComPort=1 > ComPort=2
;AppCaptionSendEventTo="<* BeBoX Multimedia Player *>" > AppCaptionSendEventTo="Centrafuse"
AppForceForeGround=BUT_TAPEDOLBY_PRESS > AppForceForeGround=STW_PLUS_PRES
I'm not sure the last one has any affect, but wanted to try it to see if it would essentially 'tap' the screen for me -- but not luck.
Additional Items of interest: (Relating to the .ini)
I'm not sure if these items have any affect with Centrafuse... maybe if someone can help troubleshoot these with me?
It starts on line 121, labled:
"; Message definition syntax"
I wonder if these items, specified as buttons would help at all... Specifically these three:
PHP Code:
; ProcessEvents : If set to "Disable", then IBuscomm will stop to send ReplyMsg, & Events + keystrokes
; : to the application Until a message with ProcessEvents "Enable"s again (flip/flop).
; : When IBusComm is launched, initial state of ProcessEvents is can be set in the main section.
; ButtonState : If Set to true, the PRESSED state will be managed automatically.
; : The ReleaseID value must be set with a valid ID for this parameter.
;
; ButtonReleaseID : If set to a valid ID, will wait the msg ID before processing
; : This can be used especially when a button PRESS/HOLD state is needed.
Hope this helps, and I look forward to your response David, and any others stuck and testing !
:-)
Where art thou David
Linear Mode
