FVWM: Speed on Interactive Move/Resize
Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Thanks in advance.
Re: FVWM: Speed on Interactive Move/Resize
On 28 October 2012 14:53, Walter Alejandro Iglesias e...@roquesor.com wrote: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Are you referring to MoveThreshold? -- Thomas Adam
Re: FVWM: Speed on Interactive Move/Resize
On Sun, Oct 28, 2012 at 02:59:34PM +, Thomas Adam wrote: On 28 October 2012 14:53, Walter Alejandro Iglesias e...@roquesor.com wrote: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Are you referring to MoveThreshold? -- Thomas Adam No. For example, I bind the function Move (as is) to Alt+F7. Once pressed Alf+F7 it starts interactive move. Now I can use arrow keys (or vi / emacs keys via readline) to move the window. If I use just that keys the window moves 5 pixels each time, doing the same while I hold Shift the window moves 100 pixels each time and holding Ctrl 1 pixel. I'd like to know if there is a way to customize that and move with a i.e. 10 pixel steps. Thomas, answer just in case you have time, because it is not too important. I can live with the default :). Thanks. Walter
Re: FVWM: Speed on Interactive Move/Resize
Walter Alejandro Iglesias e...@roquesor.com writes: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Currently no. The values 1,5,100 are defined in: libs/default.h #define DEFAULT_KDB_SHORTCUT_MOVE_DISTANCE 5 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_SMALL 1 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_BIG 100 /* pixels */ And the logic is in: libs/Target.c -- Dan Espen
Re: FVWM: Speed on Interactive Move/Resize
On Sun, Oct 28, 2012 at 02:24:42PM -0400, Dan Espen wrote: Walter Alejandro Iglesias e...@roquesor.com writes: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Currently no. The values 1,5,100 are defined in: libs/default.h #define DEFAULT_KDB_SHORTCUT_MOVE_DISTANCE 5 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_SMALL 1 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_BIG 100 /* pixels */ And the logic is in: libs/Target.c -- Dan Espen Hi Dan, Good to know what you point above. Thanks. I'd like to start learning about Xlib programing. I found this: http://www.tronche.com/gui/x/xlib-tutorial/ Could you point me (advice) to more related documentation? Where/how is it convenient to start? Walter
Re: FVWM: Speed on Interactive Move/Resize
Walter Alejandro Iglesias e...@roquesor.com writes: On Sun, Oct 28, 2012 at 02:24:42PM -0400, Dan Espen wrote: Walter Alejandro Iglesias e...@roquesor.com writes: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Currently no. The values 1,5,100 are defined in: libs/default.h #define DEFAULT_KDB_SHORTCUT_MOVE_DISTANCE 5 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_SMALL 1 /* pixels */ #define KDB_SHORTCUT_MOVE_DISTANCE_BIG 100 /* pixels */ And the logic is in: libs/Target.c -- Dan Espen Hi Dan, Good to know what you point above. Thanks. I'd like to start learning about Xlib programing. I found this: http://www.tronche.com/gui/x/xlib-tutorial/ Could you point me (advice) to more related documentation? Where/how is it convenient to start? Visit the Developer section at the Fvwm web site. -- Dan Espen
Re: FVWM: Speed on Interactive Move/Resize
On Sun, Oct 28, 2012 at 02:24:42PM -0400, Dan Espen wrote: Walter Alejandro Iglesias e...@roquesor.com writes: Hello, On interactive Move/Resize the default step is 5 pixels, 100p holding Shift and 1p holding Ctrl. Is there a way of customize that? Currently no. The values 1,5,100 are defined in: libs/default.h Hi again Dan, off topic but related Reading this header file I discovered something related to other post I did here titled Bitmap Fonts and UTF-8. That the three fonts that appeared on PrintInfo output (I explained on that post not included by me on any style) are the fonts hard coded on libs/default.h: -*-fixed-medium-r-semicondensed-*-13-*-*-*-*-*-*-*, -*-fixed-medium-r-normal-*-14-*-*-*-*-*-*-*, -*-*-medium-r-normal-*-16-*-*-*-*-*-*-* Now I tried the following. I commented out all Font entries in my styles and let FVWM load the fonts itself. In theory FVWM should load some of the fonts above (Am I wrong?). Once started all defaulted to the first of the three mentioned: -*-fixed-medium-r-semicondensed-*-13-*-*-*-*-*-*-* with NO errors on start up and rendering the correct characters. But if I include that font in any style entry it appears the error: [fvwm][FlocaleGetFontSet]: (-*-fixed-medium-r-semicondensed-*-13-*-*-*-*-*-*-*) Missing font charsets: JISX0208.1983-0, KSC5601.1987-0, GB2312.1980-0, JISX0201.1976-0 Googling, I saw that this is an old issue with utf-8 and X server trying to find the font that matches on all encodings. I don't know if all this comment is useful because that X issue seems not to have a solution.
