Hyperion Entertainment Message Boards

@Trixie

What options would you want there to be?

At least those options:

1. 100% necessary: user defined keys for swith-combo (1button or combos, like in FKEY with those "begin capture mode" for easy set)
2. ability to provide +x -x so indicator can be placed where user wish, maybe even +y -y also can be good , if user want to put it not in topbar, but somewhere else.
3. ability to switch it for just a single window
4. ability to switch it for new screens
5. arexx port good to have too

And so on

The commodity should just cycle-switch between a set of keymaps and display the currently selected one in the screen bar, that's all.

If we want to make it fast, and limit to primitive then yes, sure. No features options need it, just in tooltypes 3 settings: combo for swith, and 2 languages to switch between. But its pretty primitive imho. There can be a lot of nice stuff done like how that ELF was done, check plz those screens:

http://www.amirus.org.ru/elf_doc/pics/elfprefs.png
http://www.amirus.org.ru/elf_doc/pics/e ... otkeys.png
http://www.amirus.org.ru/elf_doc/pics/e ... mmands.png
http://www.amirus.org.ru/elf_doc/pics/e ... creens.png

©kas1e

100% necessary: user defined keys for swith-combo

That is a sure thing. This is what the standard CX_POPKEY commodity tooltype is for.

3. ability to switch it for just a single window
4. ability to switch it for new screens

Can system keymaps be set just for single windows or screens? Another question is: are they supposed to? And: if you have a handy hotkey to switch between keymaps, why complicate things with individual window- and screen- keymap settings? I'd really prefer a simple solution, much like the Windows language switching (Alt-Shift) works.

trixie wrote:Can system keymaps be set just for single windows or screens?

No. And I think that's unnecessarily complicating things - you could do it by monitoring window activations and switching the keymap dynamically, but it's much simpler and less confusing to have a hotkey/notification that the system keymap is being changed and have it set globally.

btw, the answer to the question "how does the Input prefs editor set the default keymap?" is here.

chris wrote:

trixie wrote:Can system keymaps be set just for single windows or screens?

No. And I think that's unnecessarily complicating things - you could do it by monitoring window activations and switching the keymap dynamically, but it's much simpler and less confusing to have a hotkey/notification that the system keymap is being changed and have it set globally.

+1

btw, the answer to the question "how does the Input prefs editor set the default keymap?" is here.

Thanks, I'll dive into it.

@kas1e

and how to put stuff in the WB title bar

The best example sources by AlexC is here: /.../ Here is clock placed on top of WB

OK, I had a look. The program just opens a borderless window over the Workbench screen title bar and draws the clock into it. Well, unless there's another way (looks like there isn't, as OS4 has nothing like MorphOS .sbar modules), I'm much more inclined to implement the keymap indicator/switcher as a docky.

trixie wrote:©kas1e

100% necessary: user defined keys for swith-combo

That is a sure thing. This is what the standard CX_POPKEY commodity tooltype is for.

No, that is for opening the GUI of the commodity (isn't it?).

I read kas1e as wanting to be able to define one key (combo) for each language, so you can just press that to change the keymap, without having to open the GUI of the commodity.

Best regards,

Niels

nbache wrote:

trixie wrote:©kas1e

100% necessary: user defined keys for swith-combo

That is a sure thing. This is what the standard CX_POPKEY commodity tooltype is for.

No, that is for opening the GUI of the commodity (isn't it?).

I read kas1e as wanting to be able to define one key (combo) for each language, so you can just press that to change the keymap, without having to open the GUI of the commodity.

Best regards,

Niels

Ah, I see. But I do prefer a single (but user-defined of course) key combination acting as a switcher between a set of pre-defined keymaps. Much like Alt-Shift works on Windows. Less work, less user setup, less likehood of hotkey conflict.

trixie wrote:Ah, I see. But I do prefer a single (but user-defined of course) key combination acting as a switcher between a set of pre-defined keymaps. Much like Alt-Shift works on Windows. Less work, less user setup, less likehood of hotkey conflict.

That is of course also a way to do it. But this would still be different from what CX_POPKEY is normally expected to do, as the name implies: Pop up the GUI.

Best regards,

Niels

@trixie,nbache

What i mean is just user defined key-combo for switch between languages. I.e. just like alt+shift in winxp, but have ability to set any combo (via GUI of commodity, just like it done in FKEY, with that "begin capture mode", so user will no need to know how to choice shift+shift or anything+anything). Have that, and what Nbache says (also ability to set 2 more combos for each language, also good, but for beginning we can do just one single combo for switch between 2 langs). GUI there is must imho (which will popup by that CX_POPUP or when user will dbl-click on indicator).

@trixie

From my pov, imho docky is way to _not_ go. That my reasons:

1. All dockys are "flashy". All that stuff with amidock always feels not smooth, and not like ultra-fast commodities which just stay in background. Sure, maybe all can be done well, i do not know, but till now, i see no dockys at all which i want to use, as they just slow, flashy, all that amidocks problems when you need click some more times when it need it.

2. all that dockys mean AmiDock to be run. That pretty hi-level, and i for example (and some other users) may not want amidocks at all. I personally was in hope to have someday new version of amidock, with some visual modern stuff, with much better visual input and response (i remember those confusing dbl-clicks).

And there is others, i just do not want no to bring all the problems, but i can if you need it

But commoditie with "just a simple border less background on top-bar" is a way to go , and thats why:

1. It will looks very stylish and not ugly-flashy like all the stuff in amidock all the time (some may not agree, but that imho)
2. it will works _without_ amidock, and will works just as it should be when we want small, efficient, fast resident stuff in amigaos
3. user can run it from shell just as binary, and can run it as commoditie with all that "exchange" and stuff = > everything will feels very intuitive and "amigaos"
4. later, maybe we will get that we need something like "top-bar-modules". They sure can be done different as in morphos, but concept show to be good. Maybe top-bar commodities will directly and indirectly make us think about.

and so on, can add more pluses.

So my bet: commoditie + borderless indicator at top bar of wb (basically, idicators can be expanded later, via the same gui in the commodities, like "indicator as top bar ? yes/no, " indicator as docky ? yes/ no" , "indicator as flashing screen ? yes/no", and so on. But for first, just small fancy commodities (non docky) are cool to have. It will be just more or less how all the cool ad-dons done. Imagine our commodities to be a dockys .. pretty sucky.

kas1e wrote:Some of our languages have different type of input (like Cyrillic for Russian, Serbian, Poland and if i remember right Greek and some others too ? and i am sure not only those ones), so in most of cases we want to have system in one language but have ability to type in different (our) languages. For that we need inbuild keymap switcher which should do:

1. be commodity and placed on top bar of WB, with very simple and small trignale where only 3 letters in upper case can be placed. For example it can be ENG by default, and when anyone press some magic combo on keyboard , it switch to RUS (and so you can type in Russian), or to GRK (for greek), or to PLD (for poland) and so on.
.

Completely agreed and hope it will get priority.
Many users are at least bi-lingual, or simply have a need to type in more then one language.