t; > understood, that is what seems to be meaning of the first
> > part of the explainations...
>
> Well, I probably wrote what has confused you.
> But I don't follow your change suggestions.
>
To summarize:
- To have the icons filled from left to right, and from top to
bottom, we currently have to specify "IconFill left top".
Specifying a direction, instead of an origin, would be far more
intuitive (although of course changing it now will be a
problem, again I was just noting it).
- The manual defines the syntax as: "IconFill Bottom Right".
With the above change, it should be changed to something like
"IconFill " (well, you
use an italic style in the manual for parameter names, but it
can be confusing...).
Thanks for your reply,
Bye.
--
Mathieu Bonnet
g it a bit more, although
I don't like the idea losing immediate dragging precision...
There should probably at least be some option to limit this to
focusing/raising clicks...
==
71) Option for per-page focus, so we don't risk doing things in
an application we do not see, and so we don't have to focus
back applications everytime we do something in another page.
- Another issue with the normal behavior of pages, is that even
with page switching deactivated, when an application creates a
window leaking maybe more than 50% to another page (or we move
it similarly), and we focus it, we are switched to the other
page, which is most confusing, frustrating, and anti-usable.
- I want to use your two-level workspace system for easier
pager management (e.g., showing the current desk in a taskbar
pager, with three pages, simply by calling the pager with
"Module FvwmPager *"), and easier navigation using a 2D space
(Win+Left/Right for pages, Win+Top/Bottom for desks), instead
of a single row or line of desks (of course I still could
implement the 2D space with only desks, but this would require
much more work), considering I need 18 pages (6 desks of 3
pages), but it is apparently difficult, if not impossible, to
make pages behave more like independent desks, except for the
pager and shortcuts.
==
72) I have 4px window borders. If I click on a pixel closer to
the content to resize the window to a page/screen border, it
will hide all or part of the window border outside the
page/screen, which is not clean. It should probably not be
possible. It goes with the snapping option suggestion for
resizing windows.
- If using diagonal resizing, and clicking farther below, on a
side, it can even hide the titlebar almost completely... (same
for status bars on the bottom). I don't want having the be
precise when resizing. And I don't want having to move the
window for snapping, after each resize...
==
73) I'm using "Style * IconBox none", without any other IconBox
style definitions, nor any use of FvwmIconBox, yet, after even
a complete FVWM restart (I mean computer restart in-between),
when I iconify windows, they still show as icons on my
workspace. As I'm using a taskbar, I don't want icons at all on
my desktop (catches the attention, risks of clicking on them
when trying to unfocus a window, etc.). Nothing about icons in
my session log.
--
Mathieu Bonnet
