Hi Carlos,
something is wrong in this patch. Please, don't apply it yet.
Sorry.
kix
Quoting "Rodolfo García Peñas (kix)" :
From: "Rodolfo García Peñas (kix)"
The function dockMenuCreate is splitted in four functions:
- create_clip_main_menu(WScreen*)
- create_dock_main_menu(WScreen*)
- cr
2013/4/16 Iain Patterson
> The victim window should end up back to where it started in all cases,
> because the old_maximize flag remembers the previously applied operations
> and can be used to judge whether or not we should override the old_geometry
> values.
>
> With the patch as it stands
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project wmaker-crm.git.
The branch, next has been updated
via 25b5ca256614020150ecf5f13637d1e931ead666 (commit)
from 729886ef52e271375
Hi,
the next days I will be busy. I would like to share some ideas to make
the XRandR integration easier.
When the user adds/removes a screen these items change:
1. Screen size.
2. Workspace size.
3. Dock position.
4. Clip position.
5. Menu position (if open).
6. Appicons position.
7. Window pos
On 16/04/2013 22:06, Carlos R. Mafra wrote:
>> +int wWorkspaceNew(WScreen *scr, Bool with_clip)
>> {
>> WWorkspace *wspace, **list;
>> int i;
>> @@ -102,7 +102,7 @@ int wWorkspaceNew(WScreen *scr)
>> sprintf(wspace->name, _("Workspace %i"),
>> scr->workspace_count)
On Sun, 14 Apr 2013 at 23:13:31 +0200, Rodolfo García Peñas (kix) wrote:
> From: "Rodolfo García Peñas (kix)"
>
> The function wWorkspaceRestoreState() creates two Clips:
>
> 1. First, calling wWorkspaceNew(), because this function creates
>a new Workspace, with the Clip included.
> 2. Secon
Quoth Renan Traba,
simplified logic of handleMaximize function
I won't pretend that the logic wouldn't benefit from simplification.
But...
removed unneeded old_maximize flags
Despite the hairiness of the code the old_maximize flag does serve
a purpose. Windows end up where you int
