On Thu, Jun 05, 2003 at 04:52:00PM +, Mikhael Goikhman wrote:
On 05 Jun 2003 18:16:24 +0200, Dominik Vogt wrote:
On Thu, Jun 05, 2003 at 03:39:45PM +, Mikhael Goikhman wrote:
We don't seem to have the png or colorset support in FvwmBanner.
So if a logo with an alpha channel
On 06 Jun 2003 09:15:10 +0200, Dominik Vogt wrote:
On Thu, Jun 05, 2003 at 04:52:00PM +, Mikhael Goikhman wrote:
On 05 Jun 2003 18:16:24 +0200, Dominik Vogt wrote:
On Thu, Jun 05, 2003 at 03:39:45PM +, Mikhael Goikhman wrote:
We don't seem to have the png or colorset
On Fri, Jun 06, 2003 at 07:38:12AM +, Mikhael Goikhman wrote:
I'm speaking about tarball size, not executable size.
So it will be 2283442 instead of 2243442 for each new logo. Why not?
Because the gain you get for the additional size is close to zero.
It's against the philosophy fvwm
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: migo03/06/06 04:59:21
Modified files:
modules: ChangeLog
modules/FvwmDebug: FvwmDebug.1 FvwmDebug.in
modules/FvwmPerl: FvwmPerl.in
perllib: ChangeLog
perllib/FVWM
On 06 Jun 2003 10:12:57 +0200, Dominik Vogt wrote:
On Fri, Jun 06, 2003 at 07:38:12AM +, Mikhael Goikhman wrote:
I'm speaking about tarball size, not executable size.
So it will be 2283442 instead of 2243442 for each new logo. Why not?
Because the gain you get for the additional
Mikhael Goikhman wrote:
On 06 Jun 2003 10:12:57 +0200, Dominik Vogt wrote:
On Fri, Jun 06, 2003 at 07:38:12AM +, Mikhael Goikhman wrote:
I'm speaking about tarball size, not executable size.
So it will be 2283442 instead of 2243442 for each new logo. Why not?
Because the
Alex Wallis [EMAIL PROTECTED] writes:
Mikhael Goikhman wrote:
On 06 Jun 2003 10:12:57 +0200, Dominik Vogt wrote:
On Fri, Jun 06, 2003 at 07:38:12AM +, Mikhael Goikhman wrote:
I'm speaking about tarball size, not executable size.
So it will be 2283442 instead of 2243442
Dan Espen wrote:
Alex Wallis [EMAIL PROTECTED] writes:
Mikhael Goikhman wrote:
I don't see a problem to distribute 2-3 logos in 3 variants (or include
them all into C source if they are xpm/xbm).
How about including new banners in an updated fvwm-icons package? Then
it is left
Alex Wallis [EMAIL PROTECTED] writes:
Dan Espen wrote:
Alex Wallis [EMAIL PROTECTED] writes:
Mikhael Goikhman wrote:
I don't see a problem to distribute 2-3 logos in 3 variants (or include
them all into C source if they are xpm/xbm).
How about including new banners in
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: domivogt03/06/06 08:44:53
Modified files:
. : NEWS todo-2.6
Log message:
* Updated NEWS.
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: olicha 03/06/06 10:44:04
Modified files:
. : ChangeLog
libs : PictureImageLoader.c
Log message:
* Fixed loading of png images if the caller want no alpha
--
Visit the official FVWM web
On Thu, Jun 05, 2003 at 03:39:45PM +, Mikhael Goikhman wrote:
We don't seem to have the png or colorset support in FvwmBanner.
There is png support in FvwmBanner. There is just a bug ... fixed
soon (I hope).
However, the support is limited: no alpha blending! if a point has
an alpha of =
Hey, check this out, they've got great prices on Adobe and Macromedia. Best.
Adobe Photoshop at 56% OFF,
Office XP Standard at 71% OFF,
Macromedia Studio MX at 76% OFF,
Adobe Design Collection at 62% OFF
Microsoft Visual Studio.NET at 91% OFF,
FREE SHIPPING (Ground Only)
THROUGH June 15,
Please report this to fvwm-workers@fvwm.org
hint override = 0
flags = 23a
min_width = 632, min_height = 580, max_width = 634, max_height = 551
width_inc = 1088303360, height_inc = 634
min_aspect = 580/256, max_aspect = 230/256
base_width = 230, base_height = 889
win_gravity = 1
N.B. I did not
On 06 Jun 2003 18:43:42 +0200, Winfried Boettcher wrote:
Please report this to fvwm-workers@fvwm.org
hint override = 0
flags = 23a
min_width = 632, min_height = 580, max_width = 634, max_height = 551
width_inc = 1088303360, height_inc = 634
min_aspect = 580/256, max_aspect = 230/256
On 06 Jun 2003 17:41:24 +0200, Olivier Chapuis wrote:
On Thu, Jun 05, 2003 at 03:39:45PM +, Mikhael Goikhman wrote:
We don't seem to have the png or colorset support in FvwmBanner.
There is png support in FvwmBanner. There is just a bug ... fixed
soon (I hope).
Thanks, it is fixed.
Previously I got Failed to write descriptor to 'FvwmConsole' often, but
now I can narrow the problem, this time with FvwmBanner, not FvwmConsole.
Minimal rc file:
*FvwmBanner: Timeout 200
OpaqueMoveSize unlimited
FvwmConsole
FvwmBanner
If you don't do anything during 200 seconds,
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: olicha 03/06/06 15:27:47
Modified files:
modules: ChangeLog
modules/FvwmBanner: FvwmBanner.c
Log message:
* Set msg mask to M_CONFIG_INFO | M_END_CONFIG_INFO:
* This fixes a Failed to write descriptor
On Fri, Jun 06, 2003 at 07:35:21PM +, Mikhael Goikhman wrote:
Previously I got Failed to write descriptor to 'FvwmConsole' often, but
now I can narrow the problem, this time with FvwmBanner, not FvwmConsole.
Fixed, I think.
Regards, Olivier
--
Visit the official FVWM web page at
Hi Mikhael,
I tried out your ModuleConfig tracker with FvwmTabs - it works great.
Should I expect to get an 'observation' if I dynamically change
config parameters? (using FvwmTalk or FvwmCommand) The dynamic values
are only propogated after I restart FvwmTabs.
Also, you need to
20 matches
Mail list logo
