#59 Shift key handling on non US keyboard 1 year, 4 months ago

on ~mil/mepo-tickets

Hmm - thanks for reporting. I think there may be some strangeness based on the SDL TextInput API. Essentially if the TextInput is present, raw text key events are dropped, however this may not be the correct action to take / design. This was done to prevent double event registering.

Thanks ~kml for the investigation work, this will be helpful spot to pick up on when I jump back into this.

#60 Overpass lookup ignores nodes without name tag 1 year, 5 months ago

Ticket created by ~kml on ~mil/mepo-tickets

The Overpass search script uses a jq filter to read the name tag of nodes returned by the API in order to give the pins their names. However, if no name tag is present, e.g. a simple public bench or similar, it is just dropped by the filter.

I'd much rather have it use the node id or just a placeholder than to silently fail.

#59 Shift key handling on non US keyboard 1 year, 5 months ago

Comment by ~kml on ~mil/mepo-tickets

I also have this issue with a German keyboard. The debug output says

Got keybindings table function via textinput with run expression: <move_relative 0 100>
Executing statment: { move_relative, 0, 100 }
Running API function for: move_relative requested by mepolang input statement: { move_relative, 0, 100 }
Processing key in keyup: J

I found the following code in Mepo.zig:

fn event_keyup(mepo: *@This(), e: sdl.SDL_Event) types.Pending {
    if (sdl.SDL_TRUE == sdl.SDL_IsTextInputActive() and
        e.key.keysym.mod == 0) return .None;

My guess is that the e.key.keysym.mod == 0 causes this behaviour. It would also explain your Num key. I do not know what the purpose of the condition was, but removing it seemed to fix the problem for me.