Yup, that's right
Now it's perfect
Thanks a lot for your help!
A problem occurred in a Python script. Here is the sequence of function calls leading up to the error, in the order they occurred.
/home/www/www.mcdee.net/elite/scripts/bindings.py in () 2102 # Obtain the bindings from the configuration file
2103 parser = etree.XMLParser(encoding='utf-8')
=> 2104 tree = etree.fromstring(bytes(xml, 'utf-8'), parser=parser)
2105 (items, modifiers, devices) = parseBindings(runId, tree, displayGroups)
2106
tree undefined, etree = <module 'lxml.etree' from '/usr/lib/python3/dist...ages/lxml/etree.cpython-34m-x86_64-linux-gnu.so'>, etree.fromstring = <built-in function fromstring>, builtin bytes = <class 'bytes'>, xml = 'SaitekX56', parser = <lxml.etree.XMLParser object>
/home/www/www.mcdee.net/elite/scripts/lxml.etree.pyx in lxml.etree.fromstring (src/lxml/lxml.etree.c:68106)()
/home/www/www.mcdee.net/elite/scripts/parser.pxi in lxml.etree._parseMemoryDocument (src/lxml/lxml.etree.c:102455)()
/home/www/www.mcdee.net/elite/scripts/parser.pxi in lxml.etree._parseDoc (src/lxml/lxml.etree.c:101284)()
/home/www/www.mcdee.net/elite/scripts/parser.pxi in lxml.etree._BaseParser._parseDoc (src/lxml/lxml.etree.c:96466)()
/home/www/www.mcdee.net/elite/scripts/parser.pxi in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:91275)()
/home/www/www.mcdee.net/elite/scripts/parser.pxi in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:92461)() XMLSyntaxError: Start tag expected, '<' not found, line 1, column 1
/home/www/www.mcdee.net/elite/scripts/parser.pxi in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:91757)()
args = ("Start tag expected, '<' not found, line 1, column 1",)
code = 4
error_log = <string>:1:1:FATALARSER:ERR_DOCUMENT_EMPTY: Start tag expected, '<' not found
filename = None
lineno = None
msg = "Start tag expected, '<' not found, line 1, column 1"
offset = None
position = (1, 1)
print_file_and_line = None
text = None
with_traceback = <built-in method with_traceback of XMLSyntaxError object>
Tried the mapping tool for my x56 and received a python error. Is the x56 not yet supported? Python debug:
Thank you,
Pauley
Hi, here are my binds: http://www.mcdee.net/elite/binds/qokxwn
Your tool's output is technically correct, but it would be much easier to understand if you would make it recognise diagonal hat switch presses. Right now it turns one of the components of a diagonal press into a modifier. I am also using other modifiers, so the result is a bit of a mess! If the diagonals problem would be sorted out, I think it would just leave some modifiers on multiple buttons, but that's not so confusing.
So in my binds, there are nine modifiers; five of them (5,6,7,8 & 9) are hat switch diagonal mess. Yellow no.4 is a modifier for throttle buttons. Green 2 and blue 3 are modifiers for stick buttons/hat, and both together are red 1.
It would be super cool if you could lay out the hat switch binds in an octagon according to their position around the hat switch.
Oh also, could there a be an option to skip the keyboard bindings? I don't really use the keyboard. I guess I could go and unbind all the keys, but it might be nice to just skip displaying that stuff.
I have a request for the layout. First, when printing, the colors don't show up that well for me being red/green color blind. It's fine on display, but I have yet to get a printer to print something the way it is on screen. What would help a lot is if instead of using a single box for input and the 3 entries in a row, use 3 stacked boxes with the top for ship, the second for buggy and the 3rd for UI. If a type is not bound, then that sub box is empty. Makes it a lot easier to check at a glance, you would know if you are in the buggy, you want the middle boxes and if you are in the ship, you want the top boxes.
Unfortunately there just isn't space to separate out the boxes in to multiple items, and it would result in a lot of empty space and small text in many configurations.
Have you tried using the advanced options to reduce the clutter of items you don't need, and to use numbers rather than colours for the commands with modifiers?
Unfortunately there just isn't space to separate out the boxes in to multiple items, and it would result in a lot of empty space and small text in many configurations.
I have a feeling the answer will be a no no, but will try anyway. Been using the reference sheet generator quite a bit on two PC's. Fantastic app. I installed ED on an Xbox One just after Christmas but didn't do much with it. Anyway I decided to give it another try and was pleasantly surprised to find that the controller can be configured now similar to the PC version. I know naff all about Xbox's but, would it be possible to run an Xbox binds file on the reference sheet generator. I am presuming the binds file will be the same format as the PC version. No idea how to get at it or even if it's possible.
Unfortunately I have no idea where the binds file is stored on the Xbox or how to access it. Perhaps someone else has managed to do this and will be able to provide information on how to do this.
Hi jgm,
Buttons on the back on the X56 Rhino are reversed
Greetz,
FLYNN317
Which buttons in particular? Could you provide an example image from the generator showing exactly which buttons are the wrong way round? Thanks.