Re: CVS domivogt: * Fixed RaiseOverUnmanaged vs. RaiseLower.
On 28 Jun 2001 22:05:45 -0500, FVWM CVS wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: domivogt01/06/28 22:05:45 Modified files: . : ChangeLog fvwm : events.c stack.c Log message: * Fixed RaiseOverUnmanaged vs. RaiseLower. You committed your experiments with events.c, which you obviously didn't want to commit. I am restoring events.c. We don't want FvwmButtons panels, FvwmTaskBar, gnome panel and others get fantastic positions and xv walk, right? :) cvs diff [files] | less before cvs commit [files] is a good idea. Regards, Mikhael. -- Visit the official FVWM web page at URL: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]
Re: busy menu wait
On Fri, Jun 29, 2001 at 06:38:24PM -0400, Dan Espen wrote: Dominik Vogt fvwm-workers@fvwm.org writes: On Fri, Jun 29, 2001 at 02:27:38PM -0400, Dan Espen wrote: Dan Espen [EMAIL PROTECTED] writes: Dominik Vogt fvwm-workers@fvwm.org writes: On Fri, Jun 29, 2001 at 10:36:02AM -0400, Dan Espen wrote: Ok, heres a trace: I'm not quite sure what I should see in this trace. To me, it looks like a random piece of code recorded in a log file. Is this meant to demonstrate one of the busy wait cycles? If it is, it contains neither the start nor the end of the cycle. It is meant to demonstrate the cycle. I thought when it went from XQueryPointer at line 371 in menus.c back to the same location I had the whole cycle. In the sample I sent, it seems to fake a MotionNotify event (line 1539, menus.c) and then start querying the pointer, I think its looking for a release event. If it still looks bad to you, I'll redo it. I might have inadvertantly moved the mouse while trying to get gdb to operate. Probably. A cycly should start at the beginning of the loop in MenuInteraction(). Attached is a new trace. The while loop in menus.c starts with: flags.do_popdown_now = False; thats line 1427 in this trace. You will see that twice in the attached trace. What you noticed is that fvwm periodically bumps out of the loop where it waits for events (Each time the PopupDelay is over) and checks if something has to be popped up. In the process, XQueryPointer is called three times. This happens every 150 milliseconds, so this should hardly be noticeable. I'll rewrite a bit of code so that it only needs to call XQueryPointer once. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: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]
Re: CVS domivogt: * Fixed RaiseOverUnmanaged vs. RaiseLower.
On Sat, Jun 30, 2001 at 05:22:11AM +, Mikhael Goikhman wrote: On 28 Jun 2001 22:05:45 -0500, FVWM CVS wrote: CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/06/28 22:05:45 Modified files: . : ChangeLog fvwm : events.c stack.c Log message: * Fixed RaiseOverUnmanaged vs. RaiseLower. You committed your experiments with events.c, which you obviously didn't want to commit. I am restoring events.c. We don't want FvwmButtons panels, FvwmTaskBar, gnome panel and others get fantastic positions and xv walk, right? :) cvs diff [files] | less before cvs commit [files] is a good idea. Oops, thanks. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: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]
CVS down?
Although I can ping the CVS machine, it does not respond any CVS requests. What's going on? Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL: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]
Re: Yet another unclutter problem
On 29 Jun 2001 08:57:43 -0700, Danek Duvall wrote: On Fri, Jun 29, 2001 at 08:39:09AM -0400, Dan Espen wrote: The Next [*] Focus command violates that rule, but unclutter fixes it up. If you want to focus on a new window with either of these focus models, warptowindow should be used. One inconvenient thing about warptowindow is that there's no programmatic way to get back to the original window. So if you want a command to temporarily get you to a different window and then put you back as if nothing had happened, warping the pointer doesn't work so well. Specifically, I like to bring up FvwmConsole with a single keystroke. I get focus in the new window immediately, type whatever I need in it, and when I hit ^D to get out of it, my focus returns to the window I was in before (because the mouse hasn't moved). Is there a better way of doing this? If I correctly understand the question, here is how to achieve this: Style * StickyFocus Style FvwmConsole GrabFocus Key F12 A M FvwmConsole The second way, which also achieves this (in 2.2.x it works differently): AddToFunc StartFvwmConsole + I FvwmConsole + I Wait FvwmConsole + I Next (FvwmConsole) Focus # Focus NoWarp if 2 non-sticky FvwmConsole I only post tested examples. Regards, Mikhael. -- Visit the official FVWM web page at URL: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]
Problems building snap-20010630
'
make[2]: Entering directory `/lust/home/tibbs/fvwm/utils'
cd .. CONFIG_FILES=utils/fvwm-config CONFIG_HEADERS= /bin/sh ./config.status
creating utils/fvwm-config
cd .. CONFIG_FILES=utils/fvwmbug.sh CONFIG_HEADERS= /bin/sh ./config.status
creating utils/fvwmbug.sh
BUILDER=${USER-${LOGNAME-`whoami`}} \
sed -e 's,xCCx,gcc,' -e 's,xCFLAGSx,-g -O2,' \
-e 's,xprefixx,/usr/local,' -e 's,xdatadirx,/usr/local/share,' \
-e 's,xlibexecdirx,/usr/local/libexec,' -e s,xBUILDERx,$BUILDER, \
fvwmbug.sh fvwmbug
cd .. CONFIG_FILES=utils/fvwm-menu-xlock CONFIG_HEADERS= /bin/sh
./config.status
creating utils/fvwm-menu-xlock
cd .. CONFIG_FILES=utils/fvwm-menu-directory CONFIG_HEADERS= /bin/sh
./config.status
creating utils/fvwm-menu-directory
cd .. CONFIG_FILES=utils/fvwm-menu-desktop CONFIG_HEADERS= /bin/sh
./config.status
creating utils/fvwm-menu-desktop
cd .. CONFIG_FILES=utils/fvwm-menu-headlines CONFIG_HEADERS= /bin/sh
./config.status
creating utils/fvwm-menu-headlines
make[2]: Leaving directory `/lust/home/tibbs/fvwm/utils'
Making all in docs
make[2]: Entering directory `/lust/home/tibbs/fvwm/docs'
cd .. \
CONFIG_FILES=docs/Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating docs/Makefile
make[2]: Leaving directory `/lust/home/tibbs/fvwm/docs'
make[2]: Entering directory `/lust/home/tibbs/fvwm/docs'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/lust/home/tibbs/fvwm/docs'
Making all in rpm
make[2]: Entering directory `/lust/home/tibbs/fvwm/rpm'
cd .. \
CONFIG_FILES=rpm/Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating rpm/Makefile
make[2]: Leaving directory `/lust/home/tibbs/fvwm/rpm'
make[2]: Entering directory `/lust/home/tibbs/fvwm/rpm'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/lust/home/tibbs/fvwm/rpm'
Making all in sample.fvwmrc
make[2]: Entering directory `/lust/home/tibbs/fvwm/sample.fvwmrc'
cd .. \
CONFIG_FILES=sample.fvwmrc/Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating sample.fvwmrc/Makefile
make[2]: Leaving directory `/lust/home/tibbs/fvwm/sample.fvwmrc'
make[2]: Entering directory `/lust/home/tibbs/fvwm/sample.fvwmrc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/lust/home/tibbs/fvwm/sample.fvwmrc'
Making all in tests
make[2]: Entering directory `/lust/home/tibbs/fvwm/tests'
cd .. \
CONFIG_FILES=tests/Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating tests/Makefile
make[2]: Leaving directory `/lust/home/tibbs/fvwm/tests'
make[2]: Entering directory `/lust/home/tibbs/fvwm/tests'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/lust/home/tibbs/fvwm/tests'
make[2]: Entering directory `/lust/home/tibbs/fvwm'
make[2]: Leaving directory `/lust/home/tibbs/fvwm'
make[1]: Leaving directory `/lust/home/tibbs/fvwm'
rm -rf fvwm-snap-20010630
mkdir fvwm-snap-20010630
chmod 777 fvwm-snap-20010630
here=`cd . pwd`; \
top_distdir=`cd fvwm-snap-20010630 pwd`; \
distdir=`cd fvwm-snap-20010630 pwd`; \
cd . \
automake --include-deps --build-dir=$here --srcdir-name=.
--output-dir=$top_distdir --gnu Makefile
/bin/sh ./mkinstalldirs fvwm-snap-20010630/vms
mkdir fvwm-snap-20010630/vms
for subdir in libs fvwmmodules utils docsrpm
sample.fvwmrc tests; do \
if test $subdir = .; then :; else \
test -d fvwm-snap-20010630/$subdir \
|| mkdir fvwm-snap-20010630/$subdir \
|| exit 1; \
chmod 777 fvwm-snap-20010630/$subdir; \
(cd $subdir /usr/bin/make top_distdir=../fvwm-snap-20010630
distdir=../fvwm-snap-20010630/$subdir distdir) \
|| exit 1; \
fi; \
done
make[1]: Entering directory `/lust/home/tibbs/fvwm/libs'
here=`cd .. pwd`; \
top_distdir=`cd ../fvwm-snap-20010630 pwd`; \
distdir=`cd ../fvwm-snap-20010630/libs pwd`; \
cd .. \
automake --include-deps --build-dir=$here --srcdir-name=..
--output-dir=$top_distdir --gnu libs/Makefile
make[1]: Leaving directory `/lust/home/tibbs/fvwm/libs'
make[1]: Entering directory `/lust/home/tibbs/fvwm/fvwm'
here=`cd .. pwd`; \
top_distdir=`cd ../fvwm-snap-20010630 pwd`; \
distdir=`cd ../fvwm-snap-20010630/fvwm pwd`; \
cd .. \
automake --include-deps --build-dir=$here --srcdir-name=..
--output-dir=$top_distdir --gnu fvwm/Makefile
make[1]: Leaving directory `/lust/home/tibbs/fvwm/fvwm'
make[1]: Entering directory `/lust/home/tibbs/fvwm/modules'
here=`cd .. pwd`; \
top_distdir=`cd ../fvwm-snap-20010630 pwd`; \
distdir=`cd ../fvwm-snap-20010630/modules pwd`; \
cd .. \
automake --include-deps --build-dir=$here --srcdir-name=..
--output-dir=$top_distdir --gnu modules/Makefile
for subdir in FvwmAnimate FvwmAuto FvwmBacker FvwmBanner FvwmButtons
FvwmCommand FvwmConsole FvwmCpp FvwmDebug FvwmDragWell FvwmEvent
FvwmForm FvwmGtk FvwmIconBox FvwmIconMan FvwmIdent FvwmM4 FvwmPager
FvwmRearrange FvwmSave FvwmSaveDesk FvwmScript FvwmScroll FvwmTaskBar
FvwmTheme FvwmWharf FvwmWinList; do \
if test $subdir = .; then :; else \
test -d ../fvwm
CVS migo: * Setup95: several fixes, rewordings and updates (see ChangeLog)
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo01/06/30 14:19:18 Modified files: . : ChangeLog fvwm : fvwm2.1 modules: ChangeLog modules/FvwmScript/Scripts: FvwmScript-Setup95.in sample.fvwmrc : system.fvwm2rc-sample-95 utils : ChangeLog make_fvwmdist.sh Log message: * Setup95: several fixes, rewordings and updates (see ChangeLog) * fvwm2.1: minor corrections * make_fvwmdist.sh: make the date format for NEWS to match the one in NEWS -- Visit the official FVWM web page at URL: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]
Re: CVS down?
DV == Dominik Vogt [EMAIL PROTECTED] writes: DV Although I can ping the CVS machine, it does not respond any CVS DV requests. What's going on? I don't know. It works OK for me, and I see lots of CVS activity in the logs. - J -- Visit the official FVWM web page at URL: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]
CVS migo: * Setup95: update Restart menu
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo01/06/30 15:39:58 Modified files: sample.fvwmrc : system.fvwm2rc-sample-95 modules: ChangeLog modules/FvwmScript/Scripts: fvwm-script-setup95.pl Log message: * Setup95: update Restart menu * fvwm-script-setup95.pl: process Restart like Exec, leave only existing WMs -- Visit the official FVWM web page at URL: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]
