dbbd wrote:The only options are initial repeat delay and continuous repeat delay.
Both deal with repeats. I played with both, and did not notice any effect on
the first response delay.
Anyway, thanks; I'll play with this some more.
mcowher wrote:dbbd wrote:The only options are initial repeat delay and continuous repeat delay.
Both deal with repeats. I played with both, and did not notice any effect on
the first response delay.
Anyway, thanks; I'll play with this some more.
Dbbd,
Did you ever solve this problem, because I'm having the same issue with laggy and missing response within XBMC?
class PacketBUTTON (Packet):
"""A BUTTON packet
A button packet send a key press or release event to XBMC
"""
def __init__(self, code=0, repeat=1, down=1, queue=0,
map_name="", button_name="", amount=0, axis=0):
"""
Keyword arguments:
code -- raw button code (default: 0)
repeat -- this key press should repeat until released (default: 1)
Note that queued pressed cannot repeat.
down -- if this is 1, it implies a press event, 0 implies a release
event. (default: 1)
queue -- a queued key press means that the button event is
executed just once after which the next key press is
processed. It can be used for macros. Currently there
is no support for time delays between queued presses.
(default: 0)
map_name -- a combination of map_name and button_name refers to a
mapping in the user's Keymap.xml or Lircmap.xml.
map_name can be one of the following:
"KB" => standard keyboard map ( <keyboard> section )
"XG" => xbox gamepad map ( <gamepad> section )
"R1" => xbox remote map ( <remote> section )
"R2" => xbox universal remote map ( <universalremote>
section )
"LI:devicename" => LIRC remote map where 'devicename' is the
actual device's name
button_name -- a button name defined in the map specified in map_name.
For example, if map_name is "KB" refering to the
<keyboard> section in Keymap.xml then, valid
button_names include "printscreen", "minus", "x", etc.
amount -- unimplemented for now; in the future it will be used for
specifying magnitude of analog key press eventskricker wrote:I am a bit confused as to what your are trying to do. Using this plugin you should be able to map all your buttons to whatever function you want them to do. You can also edit your keymap.xml in XBMC to change what those functions do in XBMC if you need to. That should be all you need, unless I missed something.
ryguycmt wrote:I'm sorry in advance! I'm totally new to the HTPC remote thing.
....
My specs are as follows:
XBMC 8.10
SVN unknown (compiled: Nov 13 2008)
Event Ghost 0.3.6.1487
SVN 626
Python Version 2.5.2 final
WxPython Version 1.1.6
Platform Win-XP-5.1.2600-SP3
CPU Intel Pentium 4 2.66GHz
GPU Radeon x600 x86/SSE2
Res 800X600 (hand-me-down VGA in TV)
OpenGL ATI Version 1.5
Thank you for any feed back!
first thing first: when you press any button on the remote does it show up in EG's log window (left side). If you get anything (actually events) then it means your just a few steps away. If not, you need to make sure you're loading the appropriate "stuff" for your remote to work.
So if your button presses show up on the left side you just need to drag them to the right side where your XBMC macros stand! Just make sure those macros are active.
Users browsing this forum: No registered users and 1 guest