Hello, I think I found a bug in the latest ion3: WFrame.maximize_* don't seem to work well under an IonWS. Sometimes they work i.e. they maximize in that direction and on the next call they put the workspace in the previous state, but applied to other frames they maximize that frame but won't return to the previous state. Kind of hard to describe, better try it out. Rui
On Mon, 28 Mar 2005 18:10:59 +0000 (UTC) Tuomo Valkonen <tuomov@...> wrote: > On 2005-03-28, Pedro Martelletto <pedro.martelletto@...> wrote: > > Would it be possible, using Ion extensions, to have different > > themes/bindings per workspace? > > No, and I don't think it even should possible. but why shouldn't it be possible to write a hook or wrapper that switches themes or bindings when switching workspaces/screens? seems perfectly doable. ofcourse you can not have different themes in nested workspaces visible on the same screen, maybe tuomov meant that. (but you could handle keypresses differently depending on what workspace has the focus) it's all just a matter of plugging some lua code into the right places...
Hi,
[I've waited a couple of days before re-posting this:
is the berlios server just slow due to being
overloaded, or does it actually lose mail sometimes?]
I've been having very frequent (every 20 min)
crashes of the latest Ion3 snapshot, where the ion
crash takes down the X server. All the core dumps have
gdb stacks like
#0 0x00712337 in strncmp () from /lib/tls/libc.so.6
#1 0x08061d69 in compare_nameinfos (ni1=0xbffc1b10,
ni2=0x8a72448)
at minmax.h:15
#2 0x0807e1a1 in rb_find_gkey_n (n=0x8a58428,
key=0xbffc1b10,
fxn=0x8061cc0 <compare_nameinfos>, fnd=0xbffc1b08)
at rb.c:198
#3 0x0806207f in do_use_name (reg=0x8a60918,
ns=0x809a960,
name=0x8a96f80 "Efficient Evaluation of
Classification and Recognition Systems - Micheals,
Boult (ResearchIndex) - Mozilla", instrq=-1,
failchange=0)
at names.c:290
#4 0x0806244f in do_set_name (fn=0x8062250
<use_name_anyinst>, reg=0x8a60918,
ns=0x809a960,
p=0x8a72400 "Efficient Evaluation of
(Continue reading)
On 2005-04-04, David Tweed <tweed314@...> wrote: > [I've waited a couple of days before re-posting this: > is the berlios server just slow due to being > overloaded, or does it actually lose mail sometimes?] Some weekends ago it didn't lose mail although was down, but this weekend it seems to have... *sigh*. > I've been having very frequent (every 20 min) > crashes of the latest Ion3 snapshot, where the ion > crash takes down the X server. All the core dumps have > gdb stacks like Fixed yesterday, probably (or else the problem is likely to be in the red-black tree code I took from somewhere...) -- -- Tuomo
On 2005-03-31, Rui Tiago Matos <tiagomatos@...> wrote: > WFrame.maximize_* don't seem to work well under an IonWS. Sometimes > they work i.e. they maximize in that direction and on the next call > they put the workspace in the previous state, but applied to other > frames they maximize that frame but won't return to the previous > state. Kind of hard to describe, better try it out. I can't notice any problems. -- -- Tuomo
On Apr 3, 2005 3:19 PM, Tuomo Valkonen <tuomov@...> wrote: > I can't notice any problems. I'll try to put it better: Create a IonWS. Split it horizontally. If you call said function on the left frame it works OK. If you call it on the right frame it will expand that frame, but calling again won't return to the split in half WS but instead the right frame shrinks only a little bit on the left so you can see about ~10 pixels of the left frame. Shouldn't it return to the previous state like it does when applied to the left frame?
On 2005-04-04, Rui Tiago Matos <tiagomatos@...> wrote: > Create a IonWS. Split it horizontally. If you call said function on > the left frame it works OK. If you call it on the right frame it will > expand that frame, but calling again won't return to the split in half > WS but instead the right frame shrinks only a little bit on the left > so you can see about ~10 pixels of the left frame. Shouldn't it return > to the previous state like it does when applied to the left frame? Oh, the layout must be so that status display adaptation is triggered by the toggle, and this will cause the frame to think it has been resized again and thus loses its saved size. Will be fixed when I'm less drowsy... -- -- Tuomo
On 2005-04-04 15:42 +0100, Rui Tiago Matos wrote: > Create a IonWS. Split it horizontally. If you call said function on > the left frame it works OK. If you call it on the right frame it will > expand that frame, but calling again won't return to the split in half > WS but instead the right frame shrinks only a little bit on the left > so you can see about ~10 pixels of the left frame. Shouldn't it return > to the previous state like it does when applied to the left frame? Oh, the layout must be so that status display adaptation is triggered by the maximize toggle. This will cause the frame to think it has been resized again, and thus lose its saved size. Will be fixed later when I'm less drowsy... -- -- Tuomo
Hi, One of the things that I've always wanted to do in ion is reorder the window tabs in a frame, e.g. stick a web browser at the left, and move other xterms so that related ones are close to each other, so that when I move back and forth between related windows I don't end up having to go over a bunch of windows I don't care about at the moment. Is this feature implemented, and I just don't know how to use it, or am I right in assuming that it hasn't been implemented yet? If the latter, is it planned? Frederik -- -- http://ofb.net/~frederik/
On 2005-04-04, Rui Tiago Matos <tiagomatos@...> wrote: > Create a IonWS. Split it horizontally. If you call said function on > the left frame it works OK. If you call it on the right frame it will > expand that frame, but calling again won't return to the split in half > WS but instead the right frame shrinks only a little bit on the left > so you can see about ~10 pixels of the left frame. Shouldn't it return > to the previous state like it does when applied to the left frame? Oh, the layout must be so that status display adaptation is triggered by the toggle, and this will cause the frame to think it has been resized again and thus loses its saved size. Will be fixed when I'm less drowsy... -- -- Tuomo
RSS Feed5 | |
|---|---|
11 | |
8 | |
5 | |
121 | |
9 | |
3 | |
2 | |
15 | |
25 | |
1 | |
39 | |
24 | |
10 | |
11 | |
21 | |
25 | |
53 | |
6 | |
45 | |
14 | |
52 | |
23 | |
93 | |
9 | |
56 | |
22 | |
60 | |
25 | |
23 | |
102 | |
78 | |
79 | |
48 | |
89 | |
58 | |
45 | |
87 | |
37 | |
123 | |
63 | |
140 | |
96 | |
91 | |
42 | |
74 | |
111 | |
24 | |
77 | |
26 | |
39 | |
100 | |
20 | |
110 | |
95 | |
67 | |
70 | |
150 | |
34 | |
41 | |
98 | |
30 | |
13 | |
115 | |
89 | |
176 | |
161 | |
73 | |
40 | |
44 | |
41 | |
94 | |
74 | |
134 | |
60 | |
156 | |
80 | |
138 | |
154 | |
147 | |
126 | |
58 | |
54 | |
58 | |
101 | |
116 | |
142 | |
124 | |
133 | |
133 | |
211 | |
221 | |
67 | |
89 | |
123 | |
109 | |
121 | |
15 | |
44 | |
70 | |
47 | |
37 | |
89 | |
91 | |
12 | |
93 | |
73 | |
12 | |
19 | |
37 | |
32 | |
59 | |
54 | |
153 | |
138 | |
34 | |
2 |
