re: xview program resize delay/windowlist
if (sf == NULL) return False; // xview may have this condition Ahem, this effectively prevents that any window not using the WM_TAKES_FOCUS protocol ever gets focus unless another window is already focused. Have you looked at my newer fix i sent? focus.c changed if (!FP_IS_LENIENT(FW_FOCUS_POLICY(fw)) !focus_does_accept_input_focus(fw) sf == NULL sf-Desk == Scr.CurrentDesk) to if (!FP_IS_LENIENT(FW_FOCUS_POLICY(fw)) !focus_does_accept_input_focus(fw) (sf == NULL || sf-Desk == Scr.CurrentDesk)) For windowlist, how about using a user-defined format list instead of the present if/then/else tree? For instance, mine would be Windowlist Hotkey Flags Pagex Class Name The are for me to insert an extra space, but they could be any literal Flags: S for sticky, I for iconic, correct # of spaces to keep later fields aligned -- 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: FVWM: .fvwm2rc syntax guide?
On Mon, Aug 26, 2002 at 09:26:56PM -0500, Len Philpot wrote: On Sun, Aug 25, 2002 at 10:20:47PM +, Mikhael Goikhman wrote: On 25 Aug 2002 16:18:42 -0500, Len Philpot wrote: 2. When I configure a Popup StartMenu, is there a way to accurately control where it appears on screen, in regard to the Start button? If I understood MenuStyle a bit better, maybe the answer is there (PopupOffset, or whatever it's called)...? Yes, you may do this accurately in 2.5.1+, scan NEWS file. In 2.4.x, you may do this too using Rectangle or Mouse hint (there are examples in fvwm-themes), but not as accurately as in 2.5.x. I'm using FvwmTaskBar, with no RootMenu configured, but rather all the same entries on the StartMenu. It pops up just fine when I click the task bar button, but the position is relative to the mouse pointer, not to the task bar. That's what I'm trying to achieve. I'm currently running 2.4.6, BTW (latest RPM for RedHat 7.x I could locate in a quick search). Here's what I've tried to pin down the location: AddToMenu StartMenu Root x y SelectInPlace You are adding the position hint to the wrong command. It only works with the Menu and Popup commands. This is because it's a parameter of a specific menu invocation, not of the menu as a whole. Try this instead: *FvwmTaskBarStartMenu RootMenu root +0p o100-25p SelectInPlace FvwmTaskBar passes the whole string with Menu prepended to fvwm. It's really not the most intuitive syntax I could make up. ...where x and y are various offsets. I would expect x to be 0 and y to basically be height_of_root_window - height_of_menu - height_of_taskbar. In this intance, referencing the lower left corner of the menu would have been more convenient and less prone to change, although menu's typically _do_ drop down, so I see the value in the upperleft reference point. Trouble is, it doesn't seem to make any difference at all what I put there - Nothing ever changes. See above. My MenuStyle is : MenuStyle * Foreground black, Background grey70, Greyed grey90,\ HilightBack grey60, ActiveFore black, Hilight3DThickness -1, \ font -adobe-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*, Animation,\ PopupDelay 55, PopdownDelay 5, TitleWarpOff, SeparatorsLong,\ TrianglesRelief, PopupOffset 0 95 ...with the exception that it's actually all on one line. You can split it into multiple lines for readability as long as the mwm or fvwm menu style appears as the first item of the list (as both override most settings): MenuStyle * Foreground black, Background grey70, Greyed grey90 MenuStyle * HilightBack grey60, ActiveFore black ... It works as expected, but is something there interfering? What exactly annoys you about menus and windows? Provide configurations. It's just that I prefer the mouse pointer to stay where it is when I click it. In general, I'm not a big fan of anything in the UI responding or taking any kind of action without an explicit instruction on the part of the user. I'd rather not even have the menu selection move with the mouse without the button being down, given a choice, and I don't care for highlighting icons that change as you mouseover them (so popular in Windows, Gnome, KDE, etc.), but that's just my personal GUI preferences. I like intefaces that are totally static until acted upon by the user. Once again, just my preference. Even under Windows, I don't turn on the option to jump to the active control. With those sort of things active, I tend to spend more time looking for the mouse pointer. The way I have it now, I have no warping happening, at least none I've noticed, so I'm happy with that. That's mostly a relic of the fvwm menu style. I never understood why it had to be so annoying, but we never changed it fpr backward compatibility. The first menu style everybody may want to use is MenuStyle * mwm which corrects most of the funny behaviour. Let me clarify something - I may have inadvertently come across as critical of fvwm and the way things are done. That was not intentional, but rather just the product of frustration (indeed, I even stated such in one post). I usually never write when in such a state, as I always regret it later. I'll state again: I like what I'm learning of fvwm and I'm appreciative of the help; it's just that the learning process is somewhat painful at times (at least, it smarts here and there...). You're welcome. I know the documentation isn't good for beginners. As someone else pointed out, being a developer disqualifies me for writing a tutorial. That again brings us back to the issue that we need a volunteer to write and maintain such a guide. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a
Re: FVWM: Focus back to parent
On Tue, Aug 27, 2002 at 11:35:00AM +0200, Imre Vida wrote: Hi, if i start an application and quit it (immediatelly - e.g. briefly looking at an image, etc) the focus is not returned to the parent window, the focus seems to be undefined (i.e. no window selected). I use ClickToFocus and GrabFocus. Which version or snapshot are you using? This works fine with 2.5.3. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: .fvwm2rc syntax guide?
--- Len Philpot [EMAIL PROTECTED] a écrit : On Mon, Aug 26, 2002 at 05:28:28PM +0200, szonyi calin wrote: Welcome to *nix It was hard to write, therefore it should be hard to learn, right? ;-) This kind of attitude worked for a long time when there weren't alternatives (at least perceived if not in reality). However, in today's market, as much as we (I?) sometimes dislike it, the customer deserves some consideration. Even in free software it helps. Sorry. I didn't know that people with *nix experience didn't discovered fvwm yet. I think the man page should remain as it is. The man page format is standard. I wish KDE / Gnome and others would include (more) man pages instead of all the (*?%$ HTML documentation. They try to emulate windoze (with some success :-) ) Man page _is_ a reference. Man page _is not_ a tutorial. Will never be. I agree - However some explantory text/refernce material might be in order here and there, whether in the man page or as a separate document. I think a separate document will be better. As someone wrote on this list, the man page is too big allready. If you are impatient and newbie in the same time the chances of screwing things up are big, so my advice is to start with a configuration file that _works_ and modify it to suit your needs, Well, since I started this thread let me say that I am not new to computers, nor am I totally new to *nix -- I use and administer Solaris every day at work in a decent sized production environment and have done so for almost 4 years. I'm certainly not a guru (I learn every day), but not a Unix newbie either... an fvwm newbie, certainly, though! Sorry again. :-) Many new users which come from windows don't read documentation so I thought you are one of those. My apologies, but i'm became sick of seeing windoze lusers who can't configure their pc saying that *nix is hard to learn, when the only thing they have read in their life was the label from the OK button in a dialog box. I think somebody wrote a tutorial for fvwm. Use it. The only one I've found is a bit thin. What's there is useful enough, but it's not much (as the author freely admits). I found the examples distributed with the source a good start. Maybe I'll try to write an extensive tutorial. I'm not an expert but with some help I think I can do it. The main problem are the differences between versions of fvwm Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: .fvwm2rc syntax guide?
--- Imre Vida [EMAIL PROTECTED] a écrit : On Mon, Aug 26, 2002 at 05:28:28PM +0200, szonyi calin wrote: Welcome to *nix Well, thanks for the nice welcome. :-) I think the man page should remain as it is. The man page format is standard. Man page _is_ a reference. Man page _is not_ a tutorial. Will never be. I was making a benevolent suggestion, what i thought would/could help some people. It was not about any kind of tutorial, but only about putting a piece of information (that is already in the manual) somewhere at the begining, where people reading the man the first time can easily spot it. That's the problem with man pages: the references are at the end, usually :-) There was a good manual viewer (X11 based) which was acting like a browser (i.e. you had a TOC at the beginning and when you pressed the word on that TOC the program took you right to the place where it was in the manual.) but it seems it's not on the net anymore. I was also not suggesting to change the (holy) Format either. But i can't fail to note here, that the standard does not seem to be that very strictly defined - see man of man: A manual page consists of several parts. They may be labelled NAME, SYNOPSIS, DESCRIPTION, OPTIONS, FILES, SEE ALSO, BUGS, and AUTHOR. Please note: MAY be labelled. Sorry. Next time i'll double check before saying something So i don't really understand your rather harsh tone. Could you explain? I saw some man pages which were written some kind backwards: Name , Synopsys, Description (very long -literature), Options (command options), real description of options (after a couple of pages). I don't want to read man pages where the options of command are after ten pages of scrolling. A tutorial has many literature (by literature underestanding the part that tells to users what's a pager, what's a taskbar and other similar things.) If you are impatient and newbie in the same time the chances of screwing things up are big The To the Impatient was meant to have a pinch of irony/humor. Well, it seems i could not bring it through - sorry about that. Sorry, i misunderestood that one :-( My apologies. best imre Calin ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: .fvwm2rc syntax guide?
On Tue, Aug 27, 2002 at 12:33:49PM +0200, szonyi calin wrote: --- Imre Vida [EMAIL PROTECTED] a ?crit?: On Mon, Aug 26, 2002 at 05:28:28PM +0200, szonyi I was also not suggesting to change the (holy) Format either. But i can't fail to note here, that the standard does not seem to be that very strictly defined - see man of man: A manual page consists of several parts. They may be labelled NAME, SYNOPSIS, DESCRIPTION, OPTIONS, FILES, SEE ALSO, BUGS, and AUTHOR. Please note: MAY be labelled. Sorry. Next time i'll double check before saying something Well, the man manpage is not the authorative source for information about man page formats. For Linux, there is the Linux Man Page Howto. Of course this isn't authorative either, but the standard we use for fvwm. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Focus back to parent
On Tue, Aug 27, 2002 at 11:49:33AM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 11:35:00AM +0200, Imre Vida wrote: if i start an application and quit it (immediatelly - e.g. briefly looking at an image, etc) the focus is not returned to the parent window, the focus seems to be undefined (i.e. no window selected). I use ClickToFocus and GrabFocus. Which version or snapshot are you using? This works fine with 2.5.3. it is the snapshot form 28.08 imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Focus back to parent
On Tue, Aug 27, 2002 at 02:16:07PM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 01:32:51PM +0200, Imre Vida wrote: On Tue, Aug 27, 2002 at 11:49:33AM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 11:35:00AM +0200, Imre Vida wrote: if i start an application and quit it (immediatelly - e.g. briefly looking at an image, etc) the focus is not returned to the parent window, the focus seems to be undefined (i.e. no window selected). I use ClickToFocus and GrabFocus. Which version or snapshot are you using? This works fine with 2.5.3. it is the snapshot form 28.08 Er, this snapshot will be built tomorrow. :-) sorry, i meant 20.08 imre -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: Focus back to parent
On Tue, Aug 27, 2002 at 02:29:02PM +0200, Imre Vida wrote: On Tue, Aug 27, 2002 at 02:16:07PM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 01:32:51PM +0200, Imre Vida wrote: On Tue, Aug 27, 2002 at 11:49:33AM +0200, Dominik Vogt wrote: On Tue, Aug 27, 2002 at 11:35:00AM +0200, Imre Vida wrote: if i start an application and quit it (immediatelly - e.g. briefly looking at an image, etc) the focus is not returned to the parent window, the focus seems to be undefined (i.e. no window selected). I use ClickToFocus and GrabFocus. Which version or snapshot are you using? This works fine with 2.5.3. it is the snapshot form 28.08 Er, this snapshot will be built tomorrow. :-) sorry, i meant 20.08 Then the problem should be already fixed in 2.5.3. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: FvwmIconMan: Can't set geometry
Hi, I'd like to simply start my session with a FvwmIconMan on my screen. However, it appears always in the upper left corner. (It is not swallowed into FvwmButtons.) How do I place it elsewhere? Nothing of the following was successful (these values are just to test it): *FvwmIconMan: Geometry 100x100+50+50 FvwmIconMan -geometry 100x100+50+50 Style FvwmIconMan Geometry 100x100+50+50 ? 'bye Felix -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: FvwmIconMan: Can't set geometry
f [EMAIL PROTECTED] net writes: I'd like to simply start my session with a FvwmIconMan on my screen. However, it appears always in the upper left corner. (It is not swallowed into FvwmButtons.) How do I place it elsewhere? Nothing of the following was successful (these values are just to test it): *FvwmIconMan: Geometry 100x100+50+50 FvwmIconMan -geometry 100x100+50+50 Style FvwmIconMan Geometry 100x100+50+50 You could try reading the manpage of FvwmIconMan or just search it for geometry. I admit it's not very clear, but at least it tells you that Geometry is not a valid option, while buttongeometry and managergeometry are. Of course, reading a manpage can be dangerous, because you might spend hours trying all the fancy configurable things you discover in it :-) So, to protect you from this danger, here are the relevant lines of my config: *FvwmIconMan*managergeometry1x0+0+272 *FvwmIconMan*buttongeometry 193x0 Disclaimer: The syntax is obsolete, because I still use 2.2 at work, and didn't bother to update the fvwm2rc on my laptop running 2.4. I didn't want to tell you something I haven't tested myself. Hope this helps, Rainer -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: New vs.moved window in FvwmEvent?
On 27 Aug 2002 10:12:49 -0600, Gregg Dameron wrote: Running 2.4.7 on Solaris. I would like to conditionally override any window's position when it first appears, to bring into full view any window that comes up too low (i.e., partially obscured by the Task Bar, which I have on Layer 6). ManualPlacement is not an option in this case. FvwmEvent sees both new and user-moved windows as a configure_window event. (I trapped for, but never saw, an add_window event.) PlacedByFvwm is false on a new window if the app has its own ideas about position. Is there another discriminator I can use? The add_window event should do it. Please provide the config that traps this event and does not work for you. Regards, Mikhael. -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: FVWM: FvwmIconMan: Can't set geometry
On Tue, 27 Aug 2002 12:26:35 -0700 Rainer Koehler [EMAIL PROTECTED] wrote: By the way: I have searched the man pages for more than 1 hour to find the way. The discussion about the documentation of fvwm2 via the man pages will not come to an end ... ;-) That's interesting. Why didn't you find the relevant information? I just searched for geometry and found two entries in the Configuration Options Reference Chart, the two options in the full list of options, and about three examples. Admittedly, the text in the Reference Chart is misleading (and someone gave exactly this chart as an example for a good manpage...), the full explanations are not very clear, either (you have to figure out that geometry means position and size), but the examples are quite clear, I think. Yes, the reference chart is a good overview. But the detailed description of geometry stuff is not very helpful. The description of 'managergeometry' doesn't mention the option of positioning, the 'default 1x0' in 'Configurations Options Ref. Chart' leads the reader also into the opposite direction, and, third, the new term 'managergeometry' (in comparison to 'geometry') made me think that something is different - and I interpreted it that position was not a suitable attribute here. I don't think you're stupid, but I would like to know how a manpage has to be written so that the readers understand it. So, I encourage you to think about it and submit an improved manpage to the developers ;-) I don't think you're stupid neighter, so you'll know that there's no time for everyone to be into everything ;-) I hope that those who administrate the current man page will decide if to improve this aspect. I am discussing general ideas about better documentation in another forum right now. Schoene Gruesse, Felix -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
FVWM: Re: .fvwm2rc syntax guide?
(My apologies if this reply is quoted wrong or inaccurate - I was a bit careless with a 'd$' in mutt... Must've had the wrong message selected, so I had to go to the web archive and paste it back in here to reply) You are adding the position hint to the wrong command. It only works with the Menu and Popup commands. This is because it's a parameter of a specific menu invocation, not of the menu as a whole. Try this instead: *FvwmTaskBarStartMenu RootMenu root +0p o100-25p SelectInPlace FvwmTaskBar passes the whole string with Menu prepended to fvwm. It's really not the most intuitive syntax I could make up. That works great - Thanks. Well...actually, I changed the 25 to 21, but... :) That's mostly a relic of the fvwm menu style. I never understood why it had to be so annoying, but we never changed it fpr backward compatibility. The first menu style everybody may want to use is MenuStyle * mwm which corrects most of the funny behaviour. Once again - It's not so much that I find it actively annoying, but rather just a matter of personal preference. You're welcome. I know the documentation isn't good for beginners. As someone else pointed out, being a developer disqualifies me for writing a tutorial. That again brings us back to the issue that we need a volunteer to write and maintain such a guide. -- +-+ | Len Philpothttp://philpot.org/ | | [EMAIL PROTECTED] [EMAIL PROTECTED] (alt) | +-+ -- Visit the official FVWM web page at URL: http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
