You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The weights could be passed down to the layout calculations and allow windows in a stack to have different sizes based on their weight. The reason for passing in weights via parameters instead of keeping them as a property of the layout-definition is that an end-user is more likely interested in changing the weight of a particular application (a window), not a specific tile inside the layout. Since applications are moved and occupy different tiles during their lifetime, keeping the weight as a property of a specific tile seems wrong. Since the layouts library does not know anything about applications or windows, keeping the list (and order) of weights for particular application is outside the scope of this library and therefore not its responsibility.
The text was updated successfully, but these errors were encountered:
hertg
changed the title
optional weights parameter to apply() for
optional weights parameter in apply() method
Feb 26, 2023
Note
Not approved, just an idea for now
Introduce an optional
weights: Vec<f32>
parameter to the layoutapply()
method.leftwm-layouts/leftwm-layouts/src/lib.rs
Line 15 in 6bf1c76
The weights could be passed down to the layout calculations and allow windows in a stack to have different sizes based on their weight. The reason for passing in weights via parameters instead of keeping them as a property of the layout-definition is that an end-user is more likely interested in changing the weight of a particular application (a window), not a specific tile inside the layout. Since applications are moved and occupy different tiles during their lifetime, keeping the weight as a property of a specific tile seems wrong. Since the layouts library does not know anything about applications or windows, keeping the list (and order) of weights for particular application is outside the scope of this library and therefore not its responsibility.
The text was updated successfully, but these errors were encountered: