You are not logged in.
Running arch linux with a tiling windows manager (AwesomeWM) There seems to be 2 main issues I am coming across.
First picture shows when I hover over a tab i.e. ask or bid a window shown on the left of the Trader Workstation window blinks open which moves the main window to the right and makes the experience quite cumbersome. The New window just seems to give the option to remove a tab.
Second picture is when you unlock the layout and you try to move a window within the layout i.e. options chain and then all those tiling window positions show up? The work around is resizing the window inside the layout to move the position which is not ideal.
Last edited by darkeve (2025-05-20 22:29:09)
Offline
which moves the main window to the right
Isn't that what a tiling window manager is supposed to do? Try with a non-tiling windows manager!
Offline
Awesome isn't a tiling WM but an awesome WM (self described
)
I assume by "tabs" you mean what awesomewm referst to sa "tags" (the numbers in the upper left corner)?
I also assume that what happens is that some dialog/popup shows up for some tag configuration, but that's not standard.
What is this? You need to rule the relevant window to be always floating.
I'm not sure what the second problem is supposed to describe.
Offline
By tabs I mean in the application where you see the bid and ask column. I was saying the issue is when you mouse hover over those tabs it creates that new grey window on the left which causes the main trader workstation application to go from full screen to be shifted to the right which makes it hard to click on anything.
I tried making the application a floating client but that just makes that window on the left full screen over the main application which makes things worse. The ideal solution is it should just create a small dialog box instead of spawning a new window.
The 2nd issue is you can move the sections inside the application around changing the layout but instead the 2nd picture just happens.
Offline
Ah, so the window is a popup from/generated by the trade client.
Problem remains the same, you want that /window/ to be floating (not the application and sounds you set it to be fullscreen maximizes)
Run "xprop; xwininfo" and click the supposed-to-be-popup window (twice), post the output of those commands.
Offline
The program is a badly optimized Java application. I really hope the hover window has its own id, so you can set it to floating.
Offline
Yeah that was a thought I had changing the window that gets spawned to floating, whatever it is but I was hoping there was a cleaner way.
Offline
I was hoping there was a cleaner way.
ideal solution is it should just create a small dialog box instead of spawning a new window.
which /is/
changing the window that gets spawned to floating
You'll have to at least post the outputs of xwininfo and xprop so we can figure how to identify that window, then see https://wiki.archlinux.org/title/Awesom … o_not_open for a rough idea how that works, then post the relevant rc.luad segment of your failed attempt
Sanity check: the screenshot has a single maximized/fullscreen window and apparently you don't want any tiling going on on that workspace?
moves the main window to the right and makes the experience quite cumbersome.
Why are you using a tiling setup itfp? Just use a stacking layout and maximize the window?
In case: https://awesomewm.org/apidoc/documentat … em.md.html you can have different layouts on every workspace/tag.
Offline
I was hoping there was a cleaner way.
ideal solution is it should just create a small dialog box instead of spawning a new window.
which /is/
changing the window that gets spawned to floating
You'll have to at least post the outputs of xwininfo and xprop so we can figure how to identify that window, then see https://wiki.archlinux.org/title/Awesom … o_not_open for a rough idea how that works, then post the relevant rc.luad segment of your failed attempt
Sanity check: the screenshot has a single maximized/fullscreen window and apparently you don't want any tiling going on on that workspace?
moves the main window to the right and makes the experience quite cumbersome.
Why are you using a tiling setup itfp? Just use a stacking layout and maximize the window?
In case: https://awesomewm.org/apidoc/documentat … em.md.html you can have different layouts on every workspace/tag.
Okay I'll have to rewrite my rc.lua file so I can make one tag/workspace a floating layout and see what I can come up with.
For the Sanity check question, when I made the master client ib-tws float then the window that pops up on the left go full screen over the master client which was another issue. So yeah I'll see if making the tag floating somehow changes anything.
Also I'm using a tiling layout because it's just what I'm used to using on all the tags by default.
Offline
I made the master client ib-tws float then the window that pops up
still adheres to the overall tiled layout, the plan would have been to rule that popup to be floating, not its parent.
Offline
For reference this is the xprop details of the window that appears on the left. I am currently rewriting the taglist to give the client floating properties and see what happens
_NET_WM_DESKTOP(CARDINAL) = 3
2 _NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 0, 0
3 WM_STATE(WM_STATE):
4 window state: Normal
5 icon window: 0x0
6 awful.client.property.single_instance_id(UTF8_STRING) =
7 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
8 _NET_WM_STATE(ATOM) = _NET_WM_STATE_SKIP_TASKBAR
9 WM_HINTS(WM_HINTS):
10 Client accepts input or input focus: False
11 window id # of group leader: 0x1e004a5
12 WM_TRANSIENT_FOR(WINDOW): window id # 0x0
13 _NET_WM_PID(CARDINAL) = 11772
14 WM_CLIENT_MACHINE(STRING) = "n"
15 WM_PROTOCOLS(ATOM): protocols
16 _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x0, 0x0, 0x0, 0x 0
17 WM_NORMAL_HINTS(WM_SIZE_HINTS):
18 program specified location: 443, 163
19 program specified size: 183 by 24
20 window gravity: NorthWest
21 WM_CLASS(STRING) = "jclient-LoginFrame", "jclient-LoginFr ame"
22 WM_CLIENT_LEADER(WINDOW): window id # 0x1e0000d
23 _NET_WM_NAME(UTF8_STRING) = "win0"
24 WM_NAME(STRING) = "win0"Offline
Resolved. Changed the lua code to make workspace 3 layout floating instead of tiled. Seems okay now, You can see the prompt is alot smaller now but when the application isnt maximmised the prompt kinda goes to a random place but the main issue is fixed. I can also add other sections to the application workspace and no issues there anymore.
Offline
program specified location: 443, 163Does the random location match the programs request (might be different any time from that particular instance)?
Offline
program specified location: 443, 163Does the random location match the programs request (might be different any time from that particular instance)?
I am not following
Offline
Running xprop on a window will list its attributes, including whether it requested to be positioned - and where.
You suggested that "the prompt kinda goes to a random place" and the idea would be to check whether that random place is where the client application asked it to be positioned.
Offline