Re: FVWM: best way to update a button or menu item

2015-01-21 Thread Lucio Chiappetti
On Wed, 21 Jan 2015, Chris Siebenmann wrote: 2) I want to keep the current date on the screen You want the old standby 'xclock', specifically 'xclock -digital' (possibly with '-strftime' as well Don't know why I junked it with a "don't like" back in 2006. As a clock I rather liked Jamie Za

Re: FVWM: another question about desktops

2015-01-21 Thread Thomas Adam
On Wed, Jan 21, 2015 at 04:54:31PM +0100, Lucio Chiappetti wrote: > Would it be possible to use the FvwmPager to show only the first page of > each 2x2 or 1x2 desktop (and consider the rest as hidden reserved space > which can be reached scrolling) ? No, the paget will always show the configured p

FVWM: another question about desktops

2015-01-21 Thread Lucio Chiappetti
So far (in the last 10 years or so !!) I've been using the following mental model when dealing with fvwm desktops and pages A page is a screen where I keep the terminals, editors, analysis tools I need for a particular sub-activity (say analysing the spectra of a particular source, or writing

Re: FVWM: best way to update a button or menu item

2015-01-21 Thread Chris Siebenmann
> 2) I want to keep the current date on the screen (and time as well, but > time is no problem) > > In my old configuration I do this already, I stick in a corner of the > screen, one above the other, two applications. > > - one is a xdaliclock with the (hh:mm:ss) time (no title,

Re: FVWM: best way to update a button or menu item

2015-01-21 Thread Lucio Chiappetti
On Wed, 21 Jan 2015, Lucio Chiappetti wrote: 2) I want to keep the current date on the screen (and time as well, but time is no problem) Is there a smart way to have a button periodically refresh its content ? thanks to the previous hint to SendToModule ... ChangeButton my solution

Re: FVWM: best way to update a button or menu item

2015-01-21 Thread Lucio Chiappetti
On Wed, 21 Jan 2015, Thomas Adam wrote: On Wed, Jan 21, 2015 at 02:23:21PM +0100, Lucio Chiappetti wrote: On Wed, 21 Jan 2015, Thomas Adam wrote: This is why you use FvwmEvent and the SendToModule directive: DestroyModuleConfig FE-UpdateDeskNum *FE-UpdateDeskNum: new_desk New

Re: FVWM: best way to update a button or menu item

2015-01-21 Thread Thomas Adam
On Wed, Jan 21, 2015 at 02:23:21PM +0100, Lucio Chiappetti wrote: > On Wed, 21 Jan 2015, Thomas Adam wrote: > > >This is why you use FvwmEvent and the SendToModule directive: > > > > DestroyModuleConfig FE-UpdateDeskNum > > *FE-UpdateDeskNum: new_desk NewFunc > > > > AddToFunc StartFun

Re: FVWM: best way to update a button or menu item

2015-01-21 Thread Lucio Chiappetti
On Wed, 21 Jan 2015, Thomas Adam wrote: This is why you use FvwmEvent and the SendToModule directive: DestroyModuleConfig FE-UpdateDeskNum *FE-UpdateDeskNum: new_desk NewFunc AddToFunc StartFunction I Module FvwmEvent FE-UpdateDeskNum DestroyFunc NewFunc

Re: FVWM: best way to update a button or menu item

2015-01-21 Thread Thomas Adam
On Wed, Jan 21, 2015 at 12:27:49PM +0100, Lucio Chiappetti wrote: > 1) I want to keep (e.g. in the lower left corner of my screen) a text >label with the desktop number or name > >After some experiments, I think the best is to use FvwmButtons Yes. >I define a transparent color set >

FVWM: best way to update a button or menu item

2015-01-21 Thread Lucio Chiappetti
First of all my apologies if I'm asking in the wrong place, I was a member of the mailing list , but some times after my last posting (a few years ago) I received nothing. I assumed recently that the list was replaced by the forum, but since registration to the forum is barred by a totally unun