Re: Problems with the new detection of IOCCC/Traditional move method
On Sat, Aug 09, 2003 at 11:28:43PM +0300, Mikhael Goikhman wrote: Here I demonstrate some bad problems with the current move/placement methods. I use TiledCascadePlacement, but this should not matter here. I know that xv was always problematic, but I see this with some other programs too. (And there were good workarounds for xv previously.) 1) Run: xv -geo 1500x1500 pictures/fvwm-logo-steelblue.gif Part of the image is out of the screen, because the title is fully visible, previously the image was fully visible and the title was out of the screen. Additionally, click right mouse and double click the file name, the window walks to the right (can't go down here). Press n several times to see it walking right-down. Note first that I have not xv on my machine (xv has disappeared from some distributions as Redhat and Mandrake). You should try: Style match_xv MoveByProgramMethod IgnoreGravity or Style match_xv MoveByProgramMethod UseGravity However, maybe the ICCCM/Traditional move method can be improved: Do not make any conclusion for window which are larger than the screen. [snip] 4) Run display from ImageMagick: display Then press right mouse and choose Image Info, this window is placed partially out of the screen. It does not seems that this is related to the new ICCCM/Traditional move stuff. For me this depends on the position of the main display window (if it is at top left then the transient image info pop up on my screen). I think it is a Transient Windows placement problem (or miss-feature). Regards, Olivier -- 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: Problems with the new detection of IOCCC/Traditional move method
On 10 Aug 2003 14:44:57 +0200, Olivier Chapuis wrote: On Sat, Aug 09, 2003 at 11:28:43PM +0300, Mikhael Goikhman wrote: Here I demonstrate some bad problems with the current move/placement methods. I use TiledCascadePlacement, but this should not matter here. I know that xv was always problematic, but I see this with some other programs too. (And there were good workarounds for xv previously.) 1) Run: xv -geo 1500x1500 pictures/fvwm-logo-steelblue.gif Part of the image is out of the screen, because the title is fully visible, previously the image was fully visible and the title was out of the screen. Additionally, click right mouse and double click the file name, the window walks to the right (can't go down here). Press n several times to see it walking right-down. Note first that I have not xv on my machine (xv has disappeared from some distributions as Redhat and Mandrake). Any of these should work: http://rpmfind.net/linux/rpm2html/search.php?query=xvarch=i386 You should try: Style match_xv MoveByProgramMethod IgnoreGravity or Style match_xv MoveByProgramMethod UseGravity However, maybe the ICCCM/Traditional move method can be improved: Do not make any conclusion for window which are larger than the screen. I know that I (and everyone else) should use IgnoreGravity for xv, otherwise it walks, but I thought the autodetection may be improved. I agree with your remark about large windows. It seems that the placement of the 7 xv tool windows was always problematic (just checked 2.2 and 2.4, for some reason I thought these windows were fully on the screen previously, but they were not). [snip] 4) Run display from ImageMagick: display Then press right mouse and choose Image Info, this window is placed partially out of the screen. It does not seems that this is related to the new ICCCM/Traditional move stuff. For me this depends on the position of the main display window (if it is at top left then the transient image info pop up on my screen). I think it is a Transient Windows placement problem (or miss-feature). After more experiments, yes, display does not try to place its transient aligned to some screen border as I originally thought, these were just coincidences in my test cases. The same happens with any 2.x version. 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: FVWM: FvwmButtons Panel binding to keystroke
Would be easier to have a keyboard shortcut to retract/contract the panel than having to move my mouse and click. That isn't possible yet. I'm also interested in this feature, and was planning to implement it one day if nobody else had yet, but i didn't have any time so far. cheers, Remko -- 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: FvwmButtons Panel binding to keystroke
On Sun, Aug 10, 2003 at 10:56:30AM +0200, Remko Troncon wrote: Would be easier to have a keyboard shortcut to retract/contract the panel than having to move my mouse and click. That isn't possible yet. I'm also interested in this feature, and was planning to implement it one day if nobody else had yet, but i didn't have any time so far. I think the following will do what you want, but you will need to modify it to suit your needs... have fun... DestroyFunc SeeFunc AddToFunc SeeFunc + I All ($0) Raise + I All ($0) AnimatedMove +0 +0 DestroyFunc HideFunc AddToFunc HideFunc + I All ($0) Lower + I All ($0) AnimatedMove -100 -100 DestroyFunc SeeHideFunc AddToFunc SeeHideFunc + I All ($0 !Sticky) HideFunc $0 + I All ($0 Sticky)SeeFunc $0 + I All ($0) Stick key f12 A A SeeHideFunc xclock -- 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: Two fvwm-2.4.16 window placement questions
On Mon, Aug 04, 2003 at 05:34:06PM -0400, Phil Stracchino wrote: Running with fvwm-2.4.16 on Linux, gtk-gnutella-0.92 consistently starts up with its titlebar 3/4 of the way off the top edge of the screen. I've tried Style NoPPosition without any effect. Clearly some kind of hinting on gtk-gnutella's part is incorrect; any ideas what I can do to tell fvwm2 to Do The Right Thing here? Style name_which_match_your_gnutella NoPPosition, NoUSPosition With 2.5.7 you may try to add FixedPPosition. Also, I use Style * RandomPlacement, SmartPlacement, ... in my fvwm2 configuration. 95% of the time, this does what I intend. However, fvwm2 refuses to place a window over an icon unless specifically directed to do so by -geometry. This frequently results in it placing a new window over an open window instead, because there isn't room to place the window NOT covering an existing window without covering icons instead, and given the choice, it seems to perversely prefer covering windows to covering icons. How can I tell fvwm2 that it's OK to place windows over icons, but not over regular windows? I suggest you upgrade to 2.5.7 and use the following styles: MinOverlapPlacement or MinOverlapPercentPlacement then you can use the MinOverlapPlacementPenalties or MinOverlapPercentPlacementPenalties styles to control various convering factor (e.g., ignore icons). Regards, Olivier -- 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: Внешнеэкономическая деятельность
Уважаемые коллеги! Приглашаем руководителей и специалистов компаний, в сферу деятельности которых входят внешнеэкономические интересы, принять участие в новом актуальном семинаре: Внешнеэкономическая деятельность и таможенный контроль Особое внимание на семинаре будет уделено принципиальным изменениям и дополнениям в сфере таможенного регулирования в связи с принятием нового Таможенного кодекса (вступит в силу с 1.01.2004г.). 13-14 августа 2003 года В ПРОГРАММЕ СЕМИНАРА: - Таможенные правила совершения внешнеторговых сделок. - Контракт с точки зрения таможенного инспектора. - Форма и структура контракта, общие положения, условия (существенные и факультативные) типичные ошибки при составлении; примерные схемы контрактов с учетом вида сделок. - Методы определения таможенной стоимости; виды скидок; платежи; страна происхождения. - Инкотермс-90 и Инкотермс-2000. - Анализ реальных сделок; арбитражная практика; примеры решения споров между участниками ВЭД и таможенными органами. - Перевозка товаров и транспортных средств под таможенным контролем. - Основания и порядок перемещения товаров по территории Российской Федерации. - Таможенный контроль соблюдения законодательства о доставке товаров. - Анализ практики применения законодательства о доставке товаров под таможенным контролем. - Перевозчик-правонарушитель - злоумышленник или жертва. Авторы семинара - консультанты в сфере таможенного регулирования, офицеры таможенной службы. Эксперты в различных вопросах таможенного законодательства, организаторы и участникы всероссийских и международных совещаний и семинаров по вопросам таможенного регулирования. Для того, чтобы получить более подробную информацию о курсе и зарегистрироваться в качестве участника, звоните нам по телефону: (095) 258-51-84 Если Вы не можете посетить этот семинар в указанные даты, мы будем рады провести его для сотрудников Вашей компании индивидуально. -- 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: help me with sessions to set it up
Dear Sir, I use FVWM version 2.4.16 compiled on Aug 10 2003 at 12:12:21 with support for: Stroke, XPM, GNOME WM hints, Shape, SM, Xinerama but, it seems nothing to happen when I activate function ``SaveSession'' or ``SaveQuitFunction''. thanks in advance -- Regards, Denis -- 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]
