Re: About USE_META_KEYBINDING (Stephan?)
Am 18.10.2012 um 00:17 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 17/10/12 07:41, Stephan Witt a écrit : Why not just define USE_META_KEYBINDING in configure for the mac build? Yes, this can be done. Other options are 1) to remove the USE_META_KEYBINDING macro 2) to handle Alt and Meta separately on all platforms This is what I though afterwards. Is the problem that all M- bindings should become A-? It is a lesser problem now that we hav prefs2prefs which can update bind files. I remember this was a problem for some Mac users. The bindings are only on M- after the change to free the Option key for transposed characters. Like Option-l for @ or Option-d for ∂. The problem is that some users are accustomed to work with the Option key and they have to learn to use Command or Control instead. (This depends on the Qt-setting for swapped keys being on or off.) I don't know if this scenario is likewise on Linux or Windows. Stephan
Re: About USE_META_KEYBINDING (Stephan?)
Am 18.10.2012 um 00:17 schrieb Jean-Marc Lasgouttes: > Le 17/10/12 07:41, Stephan Witt a écrit : >>> Why not just define USE_META_KEYBINDING in configure for the mac build? >> >> Yes, this can be done. >> >> Other options are >> 1) to remove the USE_META_KEYBINDING macro >> 2) to handle Alt and Meta separately on all platforms > > This is what I though afterwards. Is the problem that all M- bindings should > become A-? It is a lesser problem now that we hav prefs2prefs which can > update bind files. I remember this was a problem for some Mac users. The bindings are only on M- after the change to free the Option key for transposed characters. Like Option-l for "@" or Option-d for "∂". The problem is that some users are accustomed to work with the Option key and they have to learn to use Command or Control instead. (This depends on the Qt-setting for swapped keys being on or off.) I don't know if this scenario is likewise on Linux or Windows. Stephan
Re: About USE_META_KEYBINDING (Stephan?)
Le 17/10/12 07:41, Stephan Witt a écrit : Why not just define USE_META_KEYBINDING in configure for the mac build? Yes, this can be done. Other options are 1) to remove the USE_META_KEYBINDING macro 2) to handle Alt and Meta separately on all platforms This is what I though afterwards. Is the problem that all M- bindings should become A-? It is a lesser problem now that we hav prefs2prefs which can update bind files. JMarc
Re: About USE_META_KEYBINDING (Stephan?)
Le 17/10/12 07:41, Stephan Witt a écrit : Why not just define USE_META_KEYBINDING in configure for the mac build? Yes, this can be done. Other options are 1) to remove the USE_META_KEYBINDING macro 2) to handle Alt and Meta separately on all platforms This is what I though afterwards. Is the problem that all M- bindings should become A-? It is a lesser problem now that we hav prefs2prefs which can update bind files. JMarc
About USE_META_KEYBINDING (Stephan?)
While investigating ticket #8364, I stumbled on commit e9d943ae, which does changes to KeySequence.cpp like: case 'm': case 'M': +#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING) + mod |= MetaModifier; + i += 2; + continue; +#endif It happens that this USE_META_KEYBINDING macro is not defined anywhere. What is the intent here? Only handle Alt and Meta separately? Is this documented somewhere? Why not just define USE_META_KEYBINDING in configure for the mac build? JMarc
Re: About USE_META_KEYBINDING (Stephan?)
Am 16.10.2012 um 23:39 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: While investigating ticket #8364, I stumbled on commit e9d943ae, which does changes to KeySequence.cpp like: case 'm': case 'M': +#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING) + mod |= MetaModifier; + i += 2; + continue; +#endif It happens that this USE_META_KEYBINDING macro is not defined anywhere. What is the intent here? Only handle Alt and Meta separately? Is this documented somewhere? I used USE_MACOSX_PACKAGING because of the low afford and it is a must for Mac OS X. I didn't understand why it is not needed on other platforms, therefor I introduced USE_META_KEYBINDING to play with it. But I didn't finish it… Why not just define USE_META_KEYBINDING in configure for the mac build? Yes, this can be done. Other options are 1) to remove the USE_META_KEYBINDING macro 2) to handle Alt and Meta separately on all platforms Stephan
About USE_META_KEYBINDING (Stephan?)
While investigating ticket #8364, I stumbled on commit e9d943ae, which does changes to KeySequence.cpp like: case 'm': case 'M': +#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING) + mod |= MetaModifier; + i += 2; + continue; +#endif It happens that this USE_META_KEYBINDING macro is not defined anywhere. What is the intent here? Only handle Alt and Meta separately? Is this documented somewhere? Why not just define USE_META_KEYBINDING in configure for the mac build? JMarc
Re: About USE_META_KEYBINDING (Stephan?)
Am 16.10.2012 um 23:39 schrieb Jean-Marc Lasgouttes: > While investigating ticket #8364, I stumbled on commit e9d943ae, which does > changes to KeySequence.cpp like: > >case 'm': case 'M': > +#if defined(USE_MACOSX_PACKAGING) || defined(USE_META_KEYBINDING) > + mod |= MetaModifier; > + i += 2; > + continue; > +#endif > > It happens that this USE_META_KEYBINDING macro is not defined anywhere. What > is the intent here? Only handle Alt and Meta separately? Is this documented > somewhere? I used USE_MACOSX_PACKAGING because of the low afford and it is a must for Mac OS X. I didn't understand why it is not needed on other platforms, therefor I introduced USE_META_KEYBINDING to play with it. But I didn't finish it… > Why not just define USE_META_KEYBINDING in configure for the mac build? Yes, this can be done. Other options are 1) to remove the USE_META_KEYBINDING macro 2) to handle Alt and Meta separately on all platforms Stephan