zompist bboard

The glory! The worship!

...the burning feeling of jealousy that I didn't do it first!

What's wrong/sucks about the standard Windows Keyboard Layout Creator?

It's more tedious to set up and modify, and I'm not sure it can handle cases more complicated than dead key + key → character. Or can it? Can it do the equivalent of compose + six keys → tens of characters (I actually use this!)?

Aino Meilani wrote:It's more tedious to set up and modify, and I'm not sure it can handle cases more complicated than dead key + key → character. Or can it? Can it do the equivalent of compose + six keys → tens of characters (I actually use this!)?

It can't handle more than dead_key + key > character.

It's not entirely bad; I don't think I could ever completely give up a custom MSKLC layout in favour of a compose key. Being able to bind AltGr+E = é is a lot more efficient than, say, binding AltGr, E = é.

To make it clear: "the existing programs" refers to other compose key implementations. CKFW is not meant to replace keyboard layouts, which is where AltGr and dead keys belong, it's meant to complement them. I'm still a heavy user of AltGr despite having written this tool, but there's only so much characters you can assign to AltGr+key.

Yeah, absolutely. I'm definitely going to be in the same boat. Thanks for a great implementation!

Works great for me, except:

I put the executable in my Startup folder so it would auto-run at login (C:\Users\constantine\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\), but, IFF I run it from the start menu, it's not looking in that directory for the config file. Where should I put the config?

Fuck if I know. This is one of the reasons I prefer the task scheduler.

I think the correct way to deal with the start menu would be to put a shortcut to the executable in there and set the working directory in the shortcut properties.

If all else fails or you're really don't want shortcuts, you can use the environment variable:

Aino Meilani wrote:If the environment variable CKFWRC exists and its value is a path to a readable file, use that file

ObsequiousNewt wrote:Works great for me, except:

I put the executable in my Startup folder so it would auto-run at login (C:\Users\constantine\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\), but, IFF I run it from the start menu, it's not looking in that directory for the config file. Where should I put the config?

You should never put an executable in your Start Menu; Windows isn't really designed for that, unlike Mac OS. It's probably looking in your home directory (c:\users\constantine) or (at worst) the directory that Explorer itself is running from (c:\windows) when you click on it. (Also, if you're putting the config file in the Startup folder, shouldn't you be assaulted by a text editor or file association window every time you log in?)

Rhetorica wrote:You should never put an executable in your Start Menu; Windows isn't really designed for that, unlike Mac OS. It's probably looking in your home directory (c:\users\constantine) or (at worst) the directory that Explorer itself is running from (c:\windows) when you click on it. (Also, if you're putting the config file in the Startup folder, shouldn't you be assaulted by a text editor or file association window every time you log in?)

Tried the former, didn't try the latter. (Also, I don't know, I just did it yesterday, but it might )

EDIT: Yes, it did. Anyway, I've got it setup in Task Scheduler now, so no worries

What's this coded in?

In ugly C++.

Why do you ask?

Someone was asking in irc if one could be written in Python, so I figured it pertinent to ask what this one was in.

With enough ctypes, one certainly could be written in Python.