*** reinhard has joined #gnuenterprise
*** btami has joined #gnuenterprise
<reinhard> good morning all
<btami> good morning
*** johannesV has joined #gnuenterprise
<ajmitch> hi
<johannesV> hi
<ajmitch> well we're into upstream version freeze in ubuntu, so any new gnue releases have to have good reasons to get in :)
*** derek has quit IRC
<reinhard> ajmitch: if you have latest versions from download page, that's all what we need
<ajmitch> the versions released months ago?
<ajmitch> I'm fairly sure I'm up to date there
<ajmitch> I'm up to date with all my packages apart from one (need newer gtk# for f-spot :) 0
*** johannesV has quit IRC
*** johannesV has joined #gnuenterprise
*** yure has joined #gnuenterprise
*** btami has quit IRC
*** btami has joined #gnuenterprise
*** jamest has joined #gnuenterprise
<reinhard> hi jamest
<reinhard> is it possible that you committed a few things that have nothing to do with te
<reinhard> err
<reinhard> with the key trigger stuff?
<reinhard> e.g. stuff concerning user parameters
<jamest> ah crap
<jamest> crap
<jamest> crap
<jamest> i mean............maybe
<jamest> please tell me I didn't commit input mask stuff
<reinhard> no AFAICT
<reinhard> didn't you get the commit mail?
<jamest> i'm currently unable to read mail
<jamest> and I didn't read it last night
<jamest> problem is I don't recall why i had changed the parameter stuff
<reinhard> there was something with these parameters...
<jamest> I thought i'd done a revert before I started my stuff
<reinhard> but I thought we've sorted it out before
<jamest> yeah, they broke something
<jamest> but i too thought it was fixed
<reinhard> hmmm
<reinhard> looking more closely, the stuff you changed with this commit seems right
<reinhard> maybe you fixed it and we discussed your solution, but you forgot to commit?
<jamest> it's quite possible
<jamest> i really don't recall
<jamest> we could wait and see what breaks
<jamest> that'd tell us :)
<jamest> but while you're looking at code
<jamest> in the getEvent() function in input/GFKeyMapper.py
<jamest> whenever a ctrl key is held down on my system the keycode changes from A==65 to a=1
<jamest> and I have no clue these values are effected internationally
<jamest> looking at the wx ui's common.py  I see the key bindings for things like ctrl-c don't use ord('c') but an int of 3
<jamest> so i worked on the assumption that if I implement something broken I can at least stay consistant w/ the original breakage
<jamest> however before I started mapping out the F1 style keys in there I was hoping I could get feedback on any proper ways to deal with the keycodes so I know they work for everyone
<reinhard> I think that makes sense
<reinhard> ctrl-a = 1
<reinhard> ctrl-i = 8 (= tab)
<reinhard> ctrl-m = 13 (= cr)
<reinhard> ctrl-l = 12 (= ff)
<reinhard> but that might be different in various uis
<reinhard> bbl
*** yure has quit IRC
*** jcater has joined #gnuenterprise
*** klasstek has joined #gnuenterprise
*** kilo has joined #gnuenterprise
*** erkkie has quit IRC
*** kilo has quit IRC
*** johannesV_ has joined #gnuenterprise
*** johannesV has quit IRC
*** docelic_ has joined #gnuenterprise
<johannesV_> jamest, changing the key-code from 65 to 1 when you press ctrl+A is called "key-code translation" in wx
<johannesV_> usually the key-events (EVT_KEY_*) are untranslated, which means the key-code is always 65, no matter wheter you pressed a or A
<johannesV_> the char-event is translated, having a key-code of 97 for a or 65 for A, but also having 1 for ctrl-a
<johannesV_> have to run now ...
<johannesV_> have a nice day !
*** johannesV_ has quit IRC
*** docelic_ has quit IRC
*** erkkie has joined #gnuenterprise
*** btami has quit IRC
*** reinhard has quit IRC
*** jcater has quit IRC
*** klasstek has quit IRC
*** jamest has left #gnuenterprise
*** sjc has joined #gnuenterprise
*** sjc has quit IRC
*** jcater has joined #gnuenterprise