From the FVWM manual:. The Arduino IDE window now keeps focus when switching between virtual desktops, using window selection hotkeys, etc. It still seems to require explicitly clicking the window with the mouse to actually accept keyboard events, which is annoying, but at least it is no longer impossible to type into the window.
Not sure if this is a fundamental "feature" of Arduino, or if there is a way to fix this also. I rarely use the Arduino IDE anyway. From the FVWM documentation it would appear that this is a problem with the Arduino code or the underlying Java window toolkit, I remember seeing similar problems in other Java applications.
My blog has moved! Read it in the new location here. For the last few days, I have been playing with some small displays we have lying…. Could not load tags. Latest commit. Git stats 5, commits. Failed to load latest commit information. View code. Releases Latest stable release: 2. Installation See the installation instructions Development Those interested in contributing to FVWM should have a read of the developer documentation. Comments, Questions?
Have fun! View license. Releases 4 2. Sep 5, For instance, suppose one wanted a function that would close all windows in the current page other than the one which has focus. That function can be defined as below:. The All conditional matches all windows that meet the conditions defined in parenthesis.
Functions can execute more than one action, just add one line for each action beginning with a plus sign:. Modules are separate programs, spawned by FVWM that can add extra functionality. Sometimes, one might want to spawn multiple instances of the same type of module, each with their own separate configuration. In this case, one should spawn the module with an identifier, for instance:.
Most modules will have a number of module commands which can be used to configure the module's appearance or behavior. Use the following syntax:. For instance, if one spawned an FvwmPager with the identifier MyPager then one could configure it in the following fashion:. The FvwmPager is a module which provides a visual representation of the desks and pages provided by the window manager. Like all modules, it must be spawned by FVWM. To start an FvwmPager, add something similar to the following to your StartFunction:.
With no arguments, the FvwmPager will only display the viewports for desk 0. With the arguments 0 9, FvwmPager will show the 10 desks from See FvwmPager 1 for a list of module commands. FvwmButtons is a module which can create a box of buttons which can perform actions when pressed. FvwmButtons can also "swallow" application windows. This might be useful for swallowing a system tray window or a clock window. The size of the panel is automatically determined the panel will resize to accommodate all elements however it is also possible to manually set a size using the Geometry command.
This takes a standard X geometry. The basic commands needed to create an FvwmButtons panel are outlined below. Note that items are added by filling each row from left to right, from the top row to the bottom one. Create a button this example creates a button with a title and an icon which launches an XTerm when left clicked :. The Swallow command takes a number of "hangon" arguments. Here, the UseOld and NoClose arguments have been used.
UseOld means that an existing window will be swallowed if it exists. NoClose means that the window will not be closed if the FvwmButtons process is terminated. The stalonetray argument is the class of the window that we want to swallow.
Replace as appropriate. The last argument is a command to start the application that is to be swallowed. In this example, it is assumed that the application has already been started so the argument provided is Nop which is a function that does nothing. One could replace this with "Exec stalonetray" to start the application from the FvwmButtons module instead of assuming that the application has been started elsewhere.
Containers are spaces defined which can span multiple rows and columns or subdivide a row or column into more rows or columns. This can be useful for instance if one wants to allocate a certain percentage of space to an element. This can be defined as such:. Note that a container is created by defining a certain number of columns and rows and then using the keyword container. Elements inside the container are defined underneath this line and the container is then closed with the End command.
For a full list of options, see FvwmButtons 1. FvwmEvent is a module which can be used to bind a function or an audio file to a window manager event such as the closing of a window. In the case of an audio file, the audio will be played when the event that it is bound to occurs. FvwmEvent can be spawned from within Fvwm by adding the following to your StartFunction :. FvwmEvent can also be spawned with an identifier - see Modules.
Once spawned, FvwmEvent will run in the background, waiting for events that it has been configured to recognize. Events can be configured in the following form:. In the case where you wish to execute a function with arguments, that function and its arguments need to be quoted - see below:. For a full list of events, see FvwmEvent 1. FvwmIdent is a module which can display many items of information about a particular window that it is called on, such as the window's class name, resource name, layer, geometry and more.
This information is displayed in a separate window which is created by the module. FvwmIdent can be started using the Module FvwmIdent command. This could be bound to a menu entry or a hotkey. When an FvwmIdent is started in the context of a window, that window's information will be displayed. Otherwise, the user will be prompted to select a window manually. Colorsets in FVWM are a set of four colors a foreground color, a background color, a shadow color and a highlight color as well as an optional background pixmap.
Any part of FVWM that uses a particular colorset will be affected if that colorset is changed. All colorsets are identified by a number. Any numbering convention can be used; the fvwm-themes project documents one such convention that uses the first 40 colorsets See [5]. Colorsets can be created with the ColorSet command - syntax: ColorSet number options. See fvwm 1 - the Colorsets section - for more information. For styles such as Font , use xorg-xfontsel to determine the correct font names for X11 fonts - see X Logical Font Description and Font configuration for more information.
Windows in FVWM can be iconified minimized. This means that the window will disappear from view and be replaced by an icon on the desktop, similar to the behavior in Microsoft Windows 3. The program itself will supply the icon. This means that the window will simply disappear when iconified. The positioning of icons can be controlled using the IconBox style - note that this is not the same thing as the FvwmIconBox module - along with the IconFill style.
This means that icons will be placed at the position of the top left corner of the window. These arguments should be the number of pixels away from the screen edge that the IconBox edge should be. When the first IconBox overflows, icons will then be placed in the second IconBox.
0コメント