. The current rotation feature is great, but if
a theme uses not-so-symmetrical buttons you will never *want* to rotate
the titlebar - because the theme will start to look ugly, or it will
simply lose it's "magic". Unless the buttons get rotated together with
the text/background pixmaps.
e and know how to do it. I'm not pushing "do it
quickly", I just wouldn't like you abandoning the idea of doing it at
all. Because the title rotation could be a real beauty. If it could
rotate the whole titlebar.
And the rotation thing should not be seen as a way to force
h of a problem in simple themes (like Kliin), but any
titlebar background different from a Solid color makes using MwmDecor*
buttons difficult. Or am I doing something terribly wrong? I mean, a
"ButtonStyle All -- flat usetitlestyle" should do the trick, but it
does not.
--
\hoppke
(Grzegorz Nieweglowski)
kliin.tar.gz
Description: application/tar-gz
. However, I'm not really having enough time
right now. Studying and all... I'll be preoccupied 'till February, at
least. But if that delay would be acceptable, then it's OK."
--
\hoppke
(Grzegorz Nieweglowski)
--
Visit the official FVWM web page at http://www.fvwm.org
rouble.
Resolution, however, seems to work only for manager no. 1.
--
\hoppke
(Grzegorz Nieweglowski)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
misplaced, sometimes very far away from the icon itself.
There's even a chance of the icon itself getting misplaced.
--
\hoppke
(Grzegorz Nieweglowski)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers"
There's a small mistake in the FvwmIconMan manpage. The manual describes the
"ShowOnlyIcons" option, but it should be spelled "ShowOnlyIconic".
(FvwmIconMan doesn't know anything about an option named "ShowOnlyIcons")
--
\hoppke
(Grzegorz Nieweglowski)
h
e proxies every time some window decides
to change it's title?
--
\hoppke
(Grzegorz Nieweglowski)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
ybe?)
It's nothing really important, but would be nice.
--
\hoppke
(Grzegorz Nieweglowski)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
Hi.
CVS fvwm (current, 07-Feb-2003).
Trouble: The usuall autoheader/automake/autoconf procedure goes well, but
the resulting ./configure script bombs out when it tries to create Makefile
in the "fvwm/tests/hints" subdirectory.
I'm using autoconf-2.54 and automake-1.7.1
--
\hoppke
--
Visit the
Dan Espen wrote:
>> Dominik, do you have any idea whats going on here.
>
> Dominik, never mind.
>
> Grzegorz,
>
> It didn't bomb out for me, just printed a message.
> I'm using a much older version of autoconf and automake.
I already suspected that it must be the version I'm using. Obviously no
FVWM branch: CVS version.
Bug:
I've noticed that if you move/resize a window in outline mode, and have the
geometry window hidden, a single grayish pixel appears at (0,0) and stays
there until you finish moving/resizing.
The pixel doesn't show up with opaque move/resize, only the "rubber band"
m
[EMAIL PROTECTED] wrote:
>> this should give me two nice IconMan windows, listing different things.
>> The two IconMan windows do show up, but the second one never displays
>> anything. No matter what "Resolution" I use, it stays empty. Other
>> options work perfectly - different colorsets, geomet
Concerning: FVWM, current CVS version
I have a request:
_Please_ make the functable.c the way it was before 2003-03-03.
Why? Let me explain:
On that day Dominik introduced a slight modification ("trigger
on ButtonPress for many of the functions"), and it's been causing trouble
ever since. I don'
Dominik Vogt wrote:
> Should be fixed now. Please report back if you notice any
> unexpected behaviour.
Sure. Well, the buttons work fine now, thank you.
But some new bugs were introduced. Try doing something like
Mouse 1 T N Move
And then dragging the window (by the titlebar).
Well, normally
Dominik Vogt wrote:
> After all, you can achieve the dragging effect with
>
> AddToFunc titlebar_move
> + M Move
> Mouse 1 T N Function titlebar_move
>
> But of course we have to think about old configurations too.
Well, the complex function is a acceptable solution.
> You forget that the
fight. Unresolved perl dependencies during rpm-build, modules that
were installed but will never work etc. Really annoying stuff.
Nothing near "mission-critical", but still annoying.
Well, that's all.
--
\hoppke
(Grzegorz Nieweglowski)
http://lubuska.zapto.org/~hoppke/
--
Visit
ut some (most) browsers allow it.
Anyway, both "title" and "alt" should be provided with every image you
wish to have descriptions/popups.
--
\hoppke
(Grzegorz Nieweglowski)
http://lubuska.zapto.org/~hoppke/
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To uns
Something got broken in fvwm menus.
A config snippet:
#v+
Colorset 4 bg #b4ae9c, fg black, iconalpha 40
MenuStyle LeftMenu Font shadow="2 1":xft:Arial-10:bold, HilightBackOff, \
ActiveFore white, Hilight3dOff, Animation, PopupOffset 0 100, \
TitleWarpOff, TitleUnderlines2, SeparatorsShort, SideCol
[EMAIL PROTECTED] wrote:
>> This has changed - when I move the mouse over a menu position the
>> text label stays black, but the underscore(!) (accel-key marker)
>> turnes white. Only underscores get the "ActiveFore" option applied.
>
> Fixed.
Thank you :)
--
\hoppke
(Grzegorz Niewęgłowski)
ht
FVWM, CVS version, two weeks old. The IconGrid option doesn't seem to
work properly with arguments smaller than defaults (IconGrid 3 3).
Style * IconFont xft:arial-10, \
IconTitleRelief 1, \
IconBackgroundRelief 1, \
IconSize 52 48, \
IconBackgroundPadding 6, \
IconBackgroundColorset 2, \
IconBox
Dominik Vogt wrote:
>> IconGrid 1 1
>>
>> should (according to fvwm man page) give a nicely packed box of
>> icons, with no gaps (1 pixel long "steps" when searching for free
>> room).
>
> Only in theory. Note that the IconGrid style says nothing about
> the distance between the icons, only abou
I have some troubles with WindowStyle/fvwm functions.
This sample code:
DestroyFunc FSMax
AddToFunc FSMax
+ I WindowStyle !Borders, !Title
+ I Maximize true
should, according to my knowledge of fvwm:
a. remove the title and borders from a window
b. and then maximi
Dominik Vogt wrote:
>> I never said that I'm against reading docs. I just found lisp easier,
>> clearer, more coherent than what fvwm has to offer.
>
> I guess many people disagree with this opinion. The main
> difference is that to learn lisp, you have to learn programming.
In Sawfish you could
Dominik Vogt wrote:
> Any decent kernel is clever enough not to load multiple copies of the
> same write-only data.
I'm using the linux kernel, 2.4.21.
Results of the "free" command with 100 instances of FvwmPager running:
total used free sharedbuffers cached
Mem
Ethan Blanton nawypisowywa³(a):
> The point is that the memory consumed here is not consumed by either
> the FvwmPager text (that is, executable data) itself or the minimal
> bookkeeping required to load a second instance of the program. It was
> probably the actual run-time data required by each
26 matches
Mail list logo
