jessyink-team team mailing list archive
-
jessyink-team team
-
Mailing list archive
-
Message #00046
Merge of keyboard branch...
Dear all,
just a quick update: I finally got around to merging Egor's keyboard
branch into the trunk. Thanks a lot again for the great work!
As Egor mentioned that he wanted to spend some time on the index mode
code, I thought I get started on the custom key bindings. I am planning
on using a similar technique as I employed in the 2.0 prototype. Meaning
that I'll have the python extension create a new script node with a
unique id. The script node is then assigned a function that provides the
key bindings. If no node is found, the default key bindings are used.
Oh, there was one thing I wanted to ask you: Do you think that we should
have a separate "drawing mode" (similar to index mode) and use a key for
toggling between the modes? The reason I am asking is that in this way
we would have more keys available (as they could be assigned per mode)
and it would move to code towards a modular design, which I think is
essential for future development.
Let me know what you think!
Cheers,
Hannes
Follow ups