On 2/2/06, Dominik Vogt [EMAIL PROTECTED] wrote:
So, the work can be split into several smaller steps:
1. Make all the modules use ParseModuleArgs() and copy the fds
from the ModuleArgs struct to the arrays that are currently
used by the modules.
2. Remove the fd arrays in the modules
On 2/2/06, Dominik Vogt [EMAIL PROTECTED] wrote:
So, the work can be split into several smaller steps:
1. Make all the modules use ParseModuleArgs() and copy the fds
from the ModuleArgs struct to the arrays that are currently
used by the modules.
2. Remove the fd arrays in the modules
On 2/4/06, seventh guardian [EMAIL PROTECTED] wrote:
On 2/2/06, Dominik Vogt [EMAIL PROTECTED] wrote:
So, the work can be split into several smaller steps:
1. Make all the modules use ParseModuleArgs() and copy the fds
from the ModuleArgs struct to the arrays that are currently
I think you need to keep the asterisk at the front of the name.
There are times when you need it there, and times when you don't.
It's easier to put it there in the first place rather than trying
to stick it back when you need it.
Since I put the macros there and I like to use macros,
I have to
On 2/4/06, Dan Espen [EMAIL PROTECTED] wrote:
I think you need to keep the asterisk at the front of the name.
There are times when you need it there, and times when you don't.
It's easier to put it there in the first place rather than trying
to stick it back when you need it.
Yes, it is far
seventh guardian [EMAIL PROTECTED] writes:
On 2/4/06, Dan Espen [EMAIL PROTECTED] wrote:
I think you need to keep the asterisk at the front of the name.
There are times when you need it there, and times when you don't.
It's easier to put it there in the first place rather than trying
to
On 2/4/06, Dan Espen [EMAIL PROTECTED] wrote:
seventh guardian [EMAIL PROTECTED] writes:
On 2/4/06, Dan Espen [EMAIL PROTECTED] wrote:
I think you need to keep the asterisk at the front of the name.
There are times when you need it there, and times when you don't.
It's easier to put
On 04 Feb 2006 16:56:47 +, seventh guardian wrote:
existing structure only stores the name, and not the asterisk. Of
course we could use the existing char* MyName, but that would defeat
the whole purpose of using the ModuleArgs struct.
I wonder if we need the asterisk in the
Mikhael Goikhman [EMAIL PROTECTED] writes:
On 04 Feb 2006 16:56:47 +, seventh guardian wrote:
existing structure only stores the name, and not the asterisk. Of
course we could use the existing char* MyName, but that would defeat
the whole purpose of using the ModuleArgs struct.
On 2/4/06, Mikhael Goikhman [EMAIL PROTECTED] wrote:
On 04 Feb 2006 16:56:47 +, seventh guardian wrote:
existing structure only stores the name, and not the asterisk. Of
course we could use the existing char* MyName, but that would defeat
the whole purpose of using the
On 04 Feb 2006 19:42:58 +, seventh guardian wrote:
Yes, but as I found in the source code, modules distinguish them by
looking for the *FvwmMyname string instead of just the asterisk. I
don't know about perl, but c modules usually do that. In this case it
would be as easy to look for
On Sat, 21 Jan 2006 04:17:43 +, David Maciver wrote:
Hello,
I've written a patch that lets you configure the menu title and colorset
separately from the rest of the menu.
I've added menustyle options HilightTitle, TitleColorset and TitleFont.
Here is an example of what it looks
Here goes the patch for making FvwmAuto use the ParseModuleArgs(),
just like with FvwmAnimate.
I must confess this was really straight-forward. I should have started
from this one..
Cheers!
Renato Caldas
FvwmAuto.patch
Description: Binary data
Hi.
I'm changing the official modules to use the new ParseModuleArgs
function, and I have a question regarding the module Alias argument.
Is it in fact a protocol standard or is it something some modules use?
I say that because some modules do use the argv[6] as an alias, but
others get the name
On 04 Feb 2006 22:49:00 +, seventh guardian wrote:
I'm changing the official modules to use the new ParseModuleArgs
function, and I have a question regarding the module Alias argument.
Is it in fact a protocol standard or is it something some modules use?
This is not currently the
Hi.
Here goes a patch for FvwmConsole. I've noticed there was an excess of
vars for dealing with the module's name. I've corrected that too.
I've tested it myself and it works ok.
One question: there is a #define for a constant FARGS, the minimum
number of args required for the module. It was
16 matches
Mail list logo
