Hi all,
On Tuesday, November 30th, 2021 at 2:57 PM, Dominik Vogt
wrote:
> Still, what is the benefit of having an aspect ratio set?
For a non-swallowed floating FvwmPager, I think it makes a sense that screen
aspect ratio is preserved in it's smaller representation. Like: 16:10, 16:9,
4:3 etc
On Thursday, December 2nd, 2021 at 2:14 PM, Dominik Vogt
wrote:
> The command
>
> emulate mwm
>
> has almost no effect. I'd like to remove it. There are only
> three things it controls:
>
> 1) The geometry window during move and resize is hard coded to the
>center of the screen.
>
>=
On Wednesday, December 1st, 2021 at 2:13 AM, Dominik Vogt
wrote:
> On Tue, Nov 30, 2021 at 02:51:49PM +0000, Hegel3DReloaded wrote:
>> Maybe having ctrl+mouse-resize as I proposed above?
> Okay, I can imagine rare cases when one wants to re-enforce a
> multiple of the origin
On Saturday, December 4th, 2021 at 11:00 AM, Dominik Vogt
wrote:
> Fvwm is the only project I'm aware of that changes its name with
> each major version. Let's _please_ go back to "fvwm" and replace
> the 1.x versioning scheme with 3.x. Automake + autoconf can deal
> with renaming executables
On Saturday, December 4th, 2021 at 11:39 AM, Dominik Vogt
wrote:
> Okay, that is a real problem. The pager definitely needs to react
> to changes of the desktop layout, be it by attaching or detaching
> monitors at run time or by issuing the desktopsize command.
>
> The pager should fix that si
On Sat, Dec 04, 2021 at 02:13:06PM +0100, Dominik Vogt wrote:
>> On Sat, Dec 04, 2021 at 02:03:46PM +0100, Dominik Vogt wrote:
>> Maybe the scaling argument can be set to "auto" or something to
>> keep the desktopscale within reasonable limits? (The example with
>> desktopsize 50x1 earlkier in th
On Sunday, December 12th, 2021 at 12:40 PM, Dominik Vogt
wrote:
> On Sat, Dec 04, 2021 at 02:04:48PM +0000, Hegel3DReloaded wrote:
>> Sounds ok. Which branch should I checkout to test this?
> The dv/pager-noaspect should work now, but I've not tested it with
> multiple m
On Monday, December 13th, 2021 at 12:46 AM, Hegel3DReloaded
wrote:
> On Sunday, December 12th, 2021 at 12:40 PM, Dominik Vogt dominik.v...@gmx.de
> wrote:
> > The dv/pager-noaspect should work now, but I've not tested it with
> > multiple monitors.
I have found temporar
On Monday, December 13th, 2021 at 1:12 AM, Dominik Vogt
wrote:
> On Sun, Dec 12, 2021 at 11:46:05PM +0000, Hegel3DReloaded wrote:
> > Sorry to say, but I even didn't have a chance to start after trying to log
> > in.
> > It crashes badly. Something to do with malloc a
On Monday, December 13th, 2021 at 1:18 AM, Dominik Vogt
wrote:
> On Mon, Dec 13, 2021 at 12:12:30AM +0000, Hegel3DReloaded wrote:
> > "Move +32768p +32768p",
> Side note: The maximum valid position is +32767p +32767p. This
> probably wraps around to -32768.
That&#x
On Monday, December 13th, 2021 at 2:14 AM, Dominik Vogt
wrote:
> On Mon, Dec 13, 2021 at 12:22:47AM +0000, Hegel3DReloaded wrote:
> > Is this has something to do with intensive work you and Thomas did
> > couple weeks ago with new parser?
>
> Yes, I fixed a leak at the
On Monday, December 13th, 2021 at 2:51 AM, Dominik Vogt
wrote:
> I've committed a patch to master that truncates out of range sizes
> and positions to the max/min values instead of rejecting them.
Yes, it is ok now.
> Is there anything else in your config that's out of range? The X
> protocol
On Monday, December 13th, 2021 at 12:17 PM, Dominik Vogt
wrote:
> On Mon, Dec 13, 2021 at 07:40:06AM +0000, Hegel3DReloaded wrote:
> > > Yes, I fixed a leak at the cost of introducing a crash.
> >
> > I see. It is working now. May I close
> > https://github.com/f
On Monday, December 13th, 2021 at 12:37 PM, Dominik Vogt
wrote:
> On Mon, Dec 13, 2021 at 08:06:41AM +0000, Hegel3DReloaded wrote:
> > PlaceAgain is ignoring Style for panel:
> > PositionPlacement $[infostore.frontpanel.pos.placement]
> > ... where infostore.frontpanel.pos
Hi,
I have opened an issue about PositionPlacement Center style: after the recent
changes,
in multi monitor mode, this centers window split between left and right
monitor, while with
latest fvwm3 release, this was not the case. Using dv/pager-noaspect where the
current
issues have been resolved
On Thursday, December 16th, 2021 at 6:15 PM, Dominik Vogt
wrote:
> You forgot instructions to reproduce.
I tought it was obvious, so in hurry I didn't described that. Here it is:
Steps to reproduce with plain default FVWM setup:
1.Copy /share/fvwm3/default-config as ~/.fvwm
2.Edit ~/.
On Friday, December 17th, 2021 at 12:18 AM, Dominik Vogt
wrote:
> On Thu, Dec 16, 2021 at 07:18:23PM +0000, Hegel3DReloaded wrote:
>> xrandr --output Virtual-1 --mode 1400x1050 --primary --output Virtual-2
>> --mode 1400x1050 --right-of Virtual-1
> And how do I get these vi
On Friday, December 17th, 2021 at 1:18 AM, Dominik Vogt
wrote:
> When __pl_position_get_pos_simple() enconters a "center" argument
> it replaces it with DEFAULT_PLACEMENT_POS_CENTER_STRING which is
> defined to "screen $[w.screen] 50-50w 50-50w" as of commit id
> 71c57858ffebdede86c2097464339b65
On Friday, December 17th, 2021 at 1:34 AM, Dominik Vogt
wrote:
> > Libvirt/KVM/qemu virtualization.
> Wow, very complicated.
Not at all. Once you get 1st VM, you just clone others and have nice farm
of them. Getting new system for me is just to copy "golden" qcow2 image in
place, copy piece of
On Friday, December 17th, 2021 at 1:38 AM, Dominik Vogt
wrote:
> Should be fixed now.
>
> However, I find it really annoying that screens now have to be
> specified by name.
Yes, now it works. So you replaced $[w.screen] with ... something as I see
in git diff. Is it [c]urrent or is it aware if
On Friday, December 17th, 2021 at 2:33 AM, Dominik Vogt
wrote:
> It uses the window's screen which has already been set by the time
> the window is placed.
Great. So this is the right fix.
I have commented and closed https://github.com/fvwmorg/fvwm3/issues/648
--
Miroslav
://www.youtube.com/playlist?list=PLpVwwj0aIJjcaTFrZ5FLokl-kAMwmBxux
--
Hegel3DReloaded a.k.a. Miroslav
22 matches
Mail list logo
