Re: CVS griph: fixes for resizing shaded windows, and windows changed by complex functions
On Thu, Sep 29, 2005 at 02:09:49AM -0500, fvwm-workers wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: griph 05/09/29 02:09:48 Modified files: . : ChangeLog NEWS fvwm : frame.c move_resize.c Log message: fixes for resizing shaded windows, and windows changed by complex functions as AddToFunc ResizeShadedOpaque + I WindowShade off + I Resize + I WindowShade on Can you please post the diffs on frame.c and explain what you did? I've been working on some resize-when-shaded issues a while ago but had to stop because the patch became too difficult to manage and I wanted to think more about it first. Also, latest CVS does not compile without warnings: frame.c: In function `frame_setup_border': frame.c:309: warning: assignment makes integer from pointer without a cast frame.c:320: warning: assignment makes integer from pointer without a cast frame.c:330: warning: assignment makes integer from pointer without a cast frame.c:340: warning: assignment makes integer from pointer without a cast The corresponding code is PressedW = NULL; Which should be PressedW = None; (I'll fix that). Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] signature.asc Description: Digital signature
CVS domivogt: * Fixed compiler warning.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt05/09/29 05:15:20 Modified files: . : ChangeLog fvwm : frame.c Log message: * Fixed compiler warning.
Re: FVWM: Remembering desktop locations
On Thu, Sep 29, 2005 at 06:17:19AM +0200, Viktor Griph wrote:
On Wed, 28 Sep 2005, Zack Brown wrote:
On Wed, Sep 28, 2005 at 07:13:52PM +0200, Viktor Griph wrote:
On Wed, 28 Sep 2005, Zack Brown wrote:
DestroyFunc RememberDesk
AddToFunc RememberDesk
+ I SetEnv VillageDeskX$[desk.n] $[page.nx]
+ I SetEnv VillageDeskY$[desk.n] $[page.ny]
+ I PipeRead `echo GotoDeskAndPage $0 ${VillageDeskX$0}
${VillageDeskY$0}`
# move from desktop to desktop
Key F1 A M RememberDesk 0
Key F2 A M RememberDesk 1
With the current CVS version (or any snapshot after September 19) FVWM is
capable of nested variable expansion.
That is you will be able to do
+ I GotoDeskAndPage $0 $[VillageDeskX$0] $[VillageDeskY$0]
instead of the PipeRead invoking a shell.
I'm using 2.5.12 as found in Debian Testing. Will this feature be
officially
introduced in 2.5.15?
Yes. Until then you might actually be able to trick FVWM to expand
variables in the order you want by escaping and use of always true tests.
+ I Test (True) GotoDeskAndPage $0 $$[VillageDeskX$0] $$[VillageDeskY$0]
will probably work for you. That is it will expand the $0 before the Test
is evalueated, and at the same time change $$ to $, and then expand the
variables as the test is evalueated and the command executes.
OK, I've tested this, but it didn't work for me. It had no effect. Does it
actually work for you? Is there some kind of output I could produce that would
help debug the situation?
Be well,
Zack
/Viktor
--
Zack Brown
FVWM: Feature request: desktop pages larger than the screen?
Hi folks, It would be nice to be able to specify the page size at startup. A lot of folks run maximized xterms with no window decorations, just because if they expanded the window to keep the decorations outside of the screen, the decorations would encroach on neighboring pages. Having a page size larger than the screen size would fix this. There are other workarounds for this. You can define your own grid on the desktop, where each grid element is the size you want, and you can use Scroll to jump between them. When switching desktops (if you want the system to remember where you were on each desktop), you can use a combination of GotoDeskAndPage, and a complex Scroll calculation, to align yourself with your grid element. The drawback of this is the complex calculations, and the fact that you have to sacrifice much of Fvwm's navigational simplicity and do everything by hand. Another workaround is to only use every other page on the desktop. Then your decorations will only encroach on empty pages. You can Scroll + or - 200 to get between used pages. This has other drawbacks, such as only making use of 1/4 of the total number of pages. Also, the windows are so far apart in this case, that it's impossible to scroll partway between them for a quick cut-and-paste from one to the other. Variable page sizes would solve this problem elegantly. Pages could be just large enough to accomodate windows, decorations, and a small amount of surrounding space. Every page on the desktop could be used; and at need it would be possible to partially scroll between windows. Be well, Zack -- Zack Brown
Re: FVWM: Feature request: desktop pages larger than the screen?
On Thu, Sep 29, 2005 at 04:53:35PM +, Mikhael Goikhman wrote: On 29 Sep 2005 09:04:06 -0700, Zack Brown wrote: It would be nice to be able to specify the page size at startup. A lot of folks run maximized xterms with no window decorations, just because if they expanded the window to keep the decorations outside of the screen, the decorations would encroach on neighboring pages. Having a page size larger than the screen size would fix this. I think you simply want to have a command to switch a window into full-screen mode and back. Just use this: DestroyFunc FuncFvwmMaximizeFullScreen AddToFunc FuncFvwmMaximizeFullScreen + I ThisWindow (Maximized) WindowStyle Title, Borders + I TestRc (!Match) WindowStyle !Title, !Borders + I TestRc (!Match) Raise + I TestRc (!Match) UpdateStyles + I Maximize ewmhiwa Key F11 A SC Pick FuncFvwmMaximizeFullScreen I considered this, but there are problems. For one thing, having maximized, borderless xterms right next to each other leaves no empty desktop area to click in to call up a menu. For another, a maximized xterm with no borders will extend slightly into the neighbording pages, which is ugly. Variable page sizes would solve this problem elegantly. I don't think so. Can you give some reason? I don't see any drawback to variable-sized pages. It's just an elegant solution to any situation where you want portions of the window to extend beyond the edge of the screen, without encroaching on neighboring pages. Be well, Zack Regards, Mikhael. -- Zack Brown
FVWM: Feature request: display icon titles as tooltips.
Hi all, I'd like to suggest / request a feature: To allow icons to be displayed without their titles, and such that when the cursor is placed over an icon i.e. hovering to have the full title of the icon displayed - just like a tooltip. This currently occurs when placing the mouse cursor over the mini windows in the panels. But as well, note that currently the default title of an icon is truncated to fit into the specified icon size...however when the cursor *is* placed over icon, then the full title is displayed. I'm suggesting to allow the suppression of the default truncated title. Perhaps something like: ... *FvwmIconBox: IconTitles Always | Never | Tooltip ... where: Always = current functionality Never = always suppress icon titles ToolTip = display titles only when mouse cursor hovers over icon. Thanks.
Re: FVWM: Feature request: desktop pages larger than the screen?
On 29 Sep 2005 13:35:57 -0700, Zack Brown wrote: On Thu, Sep 29, 2005 at 04:53:35PM +, Mikhael Goikhman wrote: On 29 Sep 2005 09:04:06 -0700, Zack Brown wrote: It would be nice to be able to specify the page size at startup. A lot of folks run maximized xterms with no window decorations, just because if they expanded the window to keep the decorations outside of the screen, the decorations would encroach on neighboring pages. Having a page size larger than the screen size would fix this. I think you simply want to have a command to switch a window into full-screen mode and back. Just use this: DestroyFunc FuncFvwmMaximizeFullScreen AddToFunc FuncFvwmMaximizeFullScreen + I ThisWindow (Maximized) WindowStyle Title, Borders + I TestRc (!Match) WindowStyle !Title, !Borders + I TestRc (!Match) Raise + I TestRc (!Match) UpdateStyles + I Maximize ewmhiwa Key F11 A SC Pick FuncFvwmMaximizeFullScreen I considered this, but there are problems. For one thing, having maximized, borderless xterms right next to each other leaves no empty desktop area to click in to call up a menu. This is not really a priblem, you may bind any mouse or keyboard action in W (client window). And if you prefer an empty desktop place, then do Maximize 100 95 or something like this. For another, a maximized xterm with no borders will extend slightly into the neighbording pages, which is ugly. This is not true, a maximized window fully fits one page only. In the case of a terminal (that defines a step-like resize) there will be usually a free space left even with Maximize 100, not the other way. Variable page sizes would solve this problem elegantly. I don't think so. Can you give some reason? I don't see any drawback to variable-sized pages. It's just an elegant solution to any situation where you want portions of the window to extend beyond the edge of the screen, without encroaching on neighboring pages. I don't see how variable-sized pages may solve any problem at all. Do you also mean one page may be 800x600 and another 1200x900? Will sticky windows just disappear in the hole? Please give concrete numbers, what is your resolution, what is your border width, title height, and what do you suggest for the page size. Regards, Mikhael.
Re: FVWM: Feature request: desktop pages larger than the screen?
Zack Brown [EMAIL PROTECTED] writes: It would be nice to be able to specify the page size at startup. A lot of folks run maximized xterms with no window decorations, just because if they expanded the window to keep the decorations outside of the screen, the decorations would encroach on neighboring pages. Having a page size larger than the screen size would fix this. If you don't want overlap, use desks, not pages. -- Dan Espen E-mail: [EMAIL PROTECTED]
Re: FVWM: Feature request: desktop pages larger than the screen?
On Thu, Sep 29, 2005 at 06:58:21PM -0400, Dan Espen wrote: Zack Brown [EMAIL PROTECTED] writes: It would be nice to be able to specify the page size at startup. A lot of folks run maximized xterms with no window decorations, just because if they expanded the window to keep the decorations outside of the screen, the decorations would encroach on neighboring pages. Having a page size larger than the screen size would fix this. If you don't want overlap, use desks, not pages. But that would lose all the 2D navigation ability of having xterms in different pages of a desktop. Be well, Zack -- Dan Espen E-mail: [EMAIL PROTECTED] -- Zack Brown
FVWM: Solution for problem with fribidi (fvwm-2.5.14)
Apparently some guys found a solution for that problem with fribidi library. Here goes: sed -i 's:FRIBIDI_CHARSET_NOT_FOUND:FRIBIDI_CHAR_SET_NOT_FOUND:' libs/FBidi.c That worked for me. -- Isaque Galdino Beat to fit, paint to match...
