This topic contains 8 replies, has 4 voices, and was last updated by 
nerobot 2 years, 4 months ago.
-
Posts
-
I have just pulled and updated the latest git repo… and Ted2go no longer responds to keypresses. Ctrl-c and ctrl-v for copy and paste seem to work but not ctrl-S, f5, f7… etc. Anybody else experiencing this or is it peculiar to my system (gnome3 and archlinux)? It is possible I haven’t updated ted2go properly due to the slightly odd git submodule system which still confuses me.
I just updated to latest ted2go and all seems fine here on windows – f5, f7, Ctrl-S work anyway. Will test soon on linux.
Don’t know… Only wrong thing I know is sending numlock-converted key into core mojox.TextView.
Well, if you two don’t know, what chance have the rest of us! I’ll try rebuilding everything in a clean folder this evening. Hopefully that will fix it.
Okay, I’ve rebuilt from scratch and get the same issue… but it does seem to be related to nerobot’s numlock issue.
With numlock on (this is the default setting for me) :
– the only function key that has any effect is F11, which opens a ‘parseinfo’ popup.
– Ctrl-Z, Ctrl-X, Ctrl-C and Ctrl-V work for undo, cut, copy and paste.
– Ctrl-A works for select all.
– Ctrl-O, Ctrl-S, Ctrl-N have no effect. All other key combinations I tried have no effect (I didn’t test them all).With numlock off, all keys appear to function as expected.
In all other software, these keyboard shortcuts and function keys are unaffected by the numlock state. And as far as I understand, this is the way it should be. Numlock should only affect numpad keys, shouldn’t it?
I didn’t have this problem before pulling the latest git commits a few days ago. Previous versions of Ted2Go/Monkey worked as expected with numlock on (I never turn it off so can’t say if there was the opposite issue before). What has changed?
I’m on a laptop (is that relevant?). I will try to replicate it on my desktop tomorrow (exactly the same OS etc).
Is there any useful testing I can do to help solve this? Not that it needs an urgent fix; I can live with having to toggle numlock, now that I know!
For those interested, Mark just fixed this bug in the ‘develop’ branch. To fix the problem, pull the latest changes, update your modules, then build Ted2/Ted2Go again.
Nice to hear!
(I checked, there is no ‘numlock-bug’ in ted2go code.)
@immutableoctet thanks for the heads-up. How did you spot that commit so fast? I can’t see a way to get github to notify me of commits so either you were watching the repo like a hawk or you have Mark’s mobile number…?
@nerobot if we do find any bugs in ted2go (I’m sure there aren’t any!) or have feature requests, where should we post them?
Better via ted2go github repo issues.
Or here on forum if dislike issues.
You must be logged in to reply to this topic.