LOGIN / SIGN UP

#156 Harbour "forgotten" on config reload.

Reported by: wallex Assigned to: ioerror
Phase: release-0.1.11 Component: harbour
Type: bug Status: closed
Priority: 3: Medium
Watchers:

Attachments

Description

I noticed that after invoking a reload of the pekwm config files (eg: Entry = "Reload" { Actions = "Reload" }), the Harbour boundary data is lost:

- Maximize over harbour no longer works and apps maximize directly over them.

- Snapping no longer works, and windows smoothly pass over the edges.

- Commands like "MoveToEdge" will happily ignore the harbour and place things over it.

The current workaround is to use Restart rather than reload for now.

2009-03-09

20:40:04 changed from open to closed
20:39:58

I pushed a slightly different patch to git HEAD after discussing it with pekdon. Please check if this works for you, too. If it doesn't work, please reopen this task.

2009-03-08

23:33:22

Oops, that should be _harbour_maximize_over, but anyway... I don't really know the code well to know what's going on. It's almost like the config setting of one were being applied to both or something freaky like that.

23:30:55

With the patch the bug is fixed regardless of the "OnTop" property of the Harbour. Which I guess was to be expected.

Then the bug must be that somehow the config setting _harbour_ontop is only read correctly on startup, not on reload..?

21:49:32 changed from new to open
21:49:12 attached HarbourMaximise_1.patch
21:48:56

I think the actual question is: Why does the behaviour change after a reload? Please try the attached patch and test if it produces a consistent behaviour over a reload.

2009-03-01

00:49:08

Oh... it DOES work when I set OnTop to true :o Okay, that should be a good enough hint on where lies the problem.

2009-02-28

23:28:47

Thanks for the information. Does it work when you set OnTop to true?

13:20:08

Hmm... let's see, Harbour config is false for OnTop, the harbour is configured as so:

Harbour {

   OnTop = "False"
   MaximizeOver = "False"
   Placement = "Right"
   Orientation = "TopToBottom"
   Head = "0"
   DockApp {
      SideMin = "10"
      SideMax = "0"
   }

}

PekWM version is 0.1.10 About the toolchain... well, perhaps this part from emerge --info should help with that:

app-shells/bash: 3.2_p39

dev-java/java-config: 1.3.7-r1, 2.1.6-r1

dev-lang/python: 2.5.2-r7

dev-util/cmake: 2.4.8

sys-apps/baselayout: 2.0.0

sys-apps/openrc: 0.3.0-r1

sys-apps/sandbox: 1.2.18.1-r2

sys-devel/autoconf: 2.13, 2.63

sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3

sys-devel/gcc-config: 1.4.0-r4

sys-devel/libtool: 1.5.26

virtual/os-headers: 2.6.27-r2

CBUILD="i686-pc-linux-gnu"

CFLAGS="-march=pentium4 -g -Os -fomit-frame-pointer -momit-leaf-frame-pointer -fno-ident -pipe"

CHOST="i686-pc-linux-gnu"

I could try debugging this myself, but I'd need some clues on what part of the code to look at as I am not familiar with it.

2009-02-25

20:59:33

wallex, do you have any further information? Especially concerning the configuration options mentioned above. It might be just a configuration issue.

2009-02-13

00:23:09 changed from Claes Nästén to Andreas
00:23:03

Sorry, but I cannot reproduce it on my system. Do you have 'OnTop = "True"' in the Harbour section of ~/.pekwm/config? And please provide some further information about your pekwm version and the toolchain of your system.