In a particular script, I'd like to maximize the Konsole window, and DCOP seems like the way to do this, but though the DCOP interface for Konsole provides a maximize() function, it doesn't seem to do anything.
Using KDCOP I found in Konsole-16415 => konsole-mainwindow#1, void maximize(), but it doesn't seem to do anything. Entering the equivalent command in Konsole,
| @15:30:39 leslie@pinto | wd=~ | $ dcop --user leslie --session .DCOPserver_pinto__0 konsole-16415 konsole-mainwindow#1 maximize | rc=0
completes successfully, but the window does not become maximized.
Is this DCOP function's purpose not what it seems, or perhaps I have found a bug?
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.3 tde-config: 1.0
On 2025-03-05 16:38:40 J Leslie Turriff via tde-devels wrote:
In a particular script, I'd like to maximize the Konsole window, and DCOP seems like the way to do this, but though the DCOP interface for Konsole provides a maximize() function, it doesn't seem to do anything.
Using KDCOP I found in Konsole-16415 => konsole-mainwindow#1, void maximize(), but it doesn't seem to do anything. Entering the equivalent command in Konsole,
| @15:30:39 leslie@pinto | wd=~ | $ dcop --user leslie --session .DCOPserver_pinto__0 konsole-16415
konsole-mainwindow#1 maximize
| rc=0
completes successfully, but the window does not become maximized.
Is this DCOP function's purpose not what it seems, or perhaps I have found a bug?
Leslie
This is very strange: On another system the | DCOP Konsole mainwindow#1 maximize works after enabling the 'Configure Konsole... Allow programs to resize terminal window', but not on this machine; however, Nikolaus Klepp provided a workaround: | wmctrl -r konsole -b add,maximized_vert,maximized_horz
This does what the DCOP command fails to do.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.3 tde-config: 1.0
Anno domini 2025 Fri, 7 Mar 17:16:34 -0600 J Leslie Turriff via tde-devels scripsit:
On 2025-03-05 16:38:40 J Leslie Turriff via tde-devels wrote:
In a particular script, I'd like to maximize the Konsole window, and DCOP seems like the way to do this, but though the DCOP interface for Konsole provides a maximize() function, it doesn't seem to do anything.
Using KDCOP I found in Konsole-16415 => konsole-mainwindow#1, void maximize(), but it doesn't seem to do anything. Entering the equivalent command in Konsole,
| @15:30:39 leslie@pinto | wd=~ | $ dcop --user leslie --session .DCOPserver_pinto__0 konsole-16415
konsole-mainwindow#1 maximize
| rc=0
completes successfully, but the window does not become maximized.
Is this DCOP function's purpose not what it seems, or perhaps I have found a bug?
Leslie
This is very strange: On another system the | DCOP Konsole mainwindow#1 maximize works after enabling the 'Configure Konsole... Allow programs to resize terminal window', but not on this machine; however, Nikolaus Klepp provided a workaround: | wmctrl -r konsole -b add,maximized_vert,maximized_horz
This does what the DCOP command fails to do.
IMO "maximize" and "maximized_vert,maximized_horz" are handled differently. To be more precise, there is no Wm-flag for m"maximized", twin interprets DCOP calls to "maximize" after checking if "maximized"=="maximized_vert"||"maximized_horz" and chooses to do nothing if either is true. If the state of one of those is set, it's good enough to he "maximized". You can check the wm flags:
$ xwininfo -wm ... Window state: Maximized Vert ...
Nik
Leslie
Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.3 tde-config: 1.0 ____________________________________________________ tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
On 2025-03-08 00:52:31 Dr. Nikolaus Klepp via tde-devels wrote:
Anno domini 2025 Fri, 7 Mar 17:16:34 -0600
J Leslie Turriff via tde-devels scripsit:
On 2025-03-05 16:38:40 J Leslie Turriff via tde-devels wrote:
In a particular script, I'd like to maximize the Konsole window, and DCOP seems like the way to do this, but though the DCOP interface for Konsole provides a maximize() function, it doesn't seem to do anything.
Using KDCOP I found in Konsole-16415 => konsole-mainwindow#1, void maximize(), but it doesn't seem to do anything. Entering the equivalent command in Konsole,
| @15:30:39 leslie@pinto | wd=~ | $ dcop --user leslie --session .DCOPserver_pinto__0 konsole-16415
konsole-mainwindow#1 maximize
| rc=0
completes successfully, but the window does not become maximized.
Is this DCOP function's purpose not what it seems, or perhaps I have found a bug?
Leslie
This is very strange: On another system the
| DCOP Konsole mainwindow#1 maximize
works after enabling the 'Configure Konsole... Allow programs to resize terminal window', but not on this machine; however, Nikolaus Klepp provided a
workaround: | wmctrl -r konsole -b add,maximized_vert,maximized_horz
This does what the DCOP command fails to do.
IMO "maximize" and "maximized_vert,maximized_horz" are handled differently. To be more precise, there is no Wm-flag for m"maximized", twin interprets DCOP calls to "maximize" after checking if "maximized"=="maximized_vert"||"maximized_horz" and chooses to do nothing if either is true. If the state of one of those is set, it's good enough to he "maximized". You can check the wm flags:
$ xwininfo -wm ... Window state: Maximized Vert ...
Nik
Hm. xwininfo -wm says,
| @01:56:27 leslie@pinto | wd=~ | $ xwininfo -wm | | xwininfo: Please select the window about which you | would like information by clicking the | mouse in that window. | | xwininfo: Window id: 0x1500008 "Leslie - Konsole" | | Window manager hints: | Client accepts input or input focus: Yes | Initial state is Normal State | Displayed on desktop 2 | Window type: | Normal | Window state: | Maximized Vert | Process id: 20404 on host pinto | Frame extents: 4, 4, 25, 4 | | rc=0
but looking at Advanced => Special Window Settings (attached) shows that the Maximized setings are disabled; however, in the Size being Remembered, 759x1080, 1080 is the actual height of the display, so apparently when Trinity sees that the window's vertical size matches the display's vertical size it doesn't do whatever is necessary to maximize the window horizontally as well. Thank goodness wmctrl doesn't make that assumption. I'd say that this bit of optimization in Trinity has produced a bug.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.3 tde-config: 1.0
-
Dr. Nikolaus Klepp -
J Leslie Turriff