00:01.20 | pigeon | doctor says i don't have pneumonia |
00:01.31 | pb_ | pigeon: phew! |
00:01.52 | pb_ | well, let's hope he's right. |
00:01.54 | pigeon | I had one in 1997, btw :\ |
00:02.05 | pb_ | :-/ |
00:44.37 | dc_ | pigeon: god yes...:} |
00:45.01 | dc_ | pb_: so, mind if I start this clock thing? |
00:45.11 | dc_ | pb_: only because it sounds like fun. |
00:45.59 | pb_ | dc_: no, but... |
00:46.13 | dc_ | ... |
00:46.24 | pb_ | you might like to take a look at http://handhelds.org/~pb/gpe-clock_0.0_arm.ipk first |
00:50.30 | dc_ | ah cool |
00:50.32 | dc_ | nice. |
00:50.40 | dc_ | pb_: I mean more for gpe-conf time selection |
00:51.03 | pb_ | dc_: absolutely, go for it. |
00:51.14 | dc_ | we'll have to see how it turns out :} |
00:51.50 | pb_ | dc_: we could put the code for gpe-clock's draggable-hands widget into libgpewidget if you want to reuse something similar in gpe-conf. |
00:52.47 | dc_ | quite. it'd be nice to have a full size clock be able to replace gpe-ownerinfo if wanted by the user. |
00:52.58 | dc_ | at the login screen. |
00:53.16 | pb_ | yes, that's a good idea also. |
00:54.50 | pb_ | so, how do you plan to arrange things in gpe-conf? |
00:55.00 | dc_ | the clock...? |
00:55.03 | pb_ | yeah |
00:55.17 | dc_ | well, have a button that pops up the clock. |
00:55.20 | dc_ | to select a time. |
00:55.42 | pb_ | right, sounds cool |
00:55.55 | pb_ | I guess that avoids Florian's worry about space in the dialog |
00:55.56 | dc_ | it could also be used in gpe-calendar if it works okay and is faster than the current method I guess. |
00:56.01 | dc_ | pb_: indeed. |
00:56.15 | pb_ | yes, that's a good idea. I've always hated the way gpe-calendar selects times at the moment. |
00:56.38 | pb_ | if you can make a popup-clock widget that can be used in many places, that would be great. |
00:56.42 | dc_ | :} |
00:56.58 | dc_ | then I can officialy claim position as popup and drawing area master! |
00:57.10 | pb_ | exactly. |
01:04.29 | *** join/#gpe jg (~jg@dialup-67.30.191.123.Dial.Boston1.Level3.net) |
01:04.36 | pb_ | hi jg |
01:04.49 | jg | pb_: evening... |
01:04.51 | jg | pb_: how goes it? |
01:05.05 | pb_ | jg: yeah, not bad, how's things with you? |
01:05.19 | jg | I only today caught up on my inbox for the first time in over a week.... |
01:05.33 | jg | pb_: well over 1000 messages to deal with.... |
01:05.41 | pb_ | :-/ |
01:05.47 | jg | pb_: you can guess the topics.... |
01:06.32 | pb_ | yeah, I think I can. |
01:06.45 | mallum | jg: 'Urgent Assistance' ? |
01:06.57 | jg | mallum: the XFree86 and X.org messes... |
01:07.05 | mallum | jg: 'Make Money FAST" ? |
01:07.29 | mallum | jg: x.org involved too now ? |
01:08.04 | jg | mallum: they managed to insert themselves into things, and had to be told similar messages.... |
01:08.17 | jg | whether they will listen is unclear. |
01:09.04 | moray | mallum: "I am sincerely proposing to you to render me some of your highly needed assistance in respect to safekeeping of the X Window System that was left to me by my uncle ..." ;) |
01:09.13 | mallum | moray: hehe |
01:09.51 | mallum | jg: it could be ( get?) worse, RMS could be involved ;-) |
01:10.23 | jg | mallum: yes, it could. I had him to deal with a month ago, soaking amazing amounts of time.... |
01:10.26 | jg | Sigh... |
01:10.39 | moray | jg: hm, how bad is it all? I looked up the Slashdot story after you mentioned it, but that's hardly a trustworth source |
01:10.51 | jg | I'd rather get to do some hacking than open source politics. |
01:10.55 | moray | indeed. |
01:11.24 | jg | moray: a line got drawn in the sand. Deadline for fundamental reform is next Thursday. Only time will tell.... |
01:12.07 | mallum | jg: I've been hacking a little gnome panel app frontend to xrandr :-) |
01:12.11 | moray | jg: ah right, was that the right thing to happen, or someone overdramatising? |
01:12.44 | jg | moray: no, teleconference occurred yesterday: minutes and a copy of the audio shortly forthcoming.... |
01:12.45 | moray | mallum: do you know if any of the 'normal' drivers have got round to xrandr support yet in 4.3? |
01:13.14 | jg | moray: just size change. I have to read to my son. BBL. |
01:13.14 | mallum | moray: for resize I think most do, for rotation ( and reflection ) on tinyx |
01:13.20 | mallum | s/on/only/ |
01:13.54 | moray | mallum: hm, rotation would be nice for my rotatable TFT occasionally |
01:14.09 | moray | mallum: ha |
01:14.15 | mallum | moray: what card are you using ? |
01:14.39 | moray | mallum: it's a matrox g450 in this box IIRC |
01:14.43 | mallum | "and this little X call was bad as it gernerated a round trip all the way up the hill to the X Server" |
01:15.11 | mallum | moray: you could try an XVesa tinyx server on it |
01:15.39 | dc_ | mallum: :S |
01:15.41 | dc_ | mallum: :DD |
01:15.42 | moray | true, it's not as if I'm doing anything overly graphically intensive anyway... |
01:15.44 | dc_ | mallum: how fun |
01:15.44 | mallum | moray: I have one I can put somewhere public for you if you want |
01:15.55 | moray | mallum: ah, might be worth a try |
01:16.11 | mallum | moray: I'll upload it tommorow as bedtime in a mo .. |
01:16.22 | moray | thanks. |
01:16.47 | mallum | moray: on the tablet, performance isn't much off the nv ( open ) driver on the tablet |
01:16.54 | moray | ah right. |
01:17.42 | mallum | okey, Im repeating myself, bedtime I think :-) |
01:17.46 | mallum | g'night all |
01:17.47 | moray | good night |
01:17.50 | dc_ | night |
01:30.05 | *** join/#gpe paul ([sotz7SZWm@hibernia.jakma.org) |
01:37.35 | dc_ | hey paul |
01:37.42 | paul | heya damien |
01:37.54 | paul | dc_: up late? |
01:37.57 | dc_ | paul: how'd the gpe-irc stuff go? |
01:38.01 | dc_ | paul: yeah, weekend ;) |
01:38.28 | paul | dc_: i know why its crashing |
01:38.36 | dc_ | coolio |
01:38.53 | moray | paul: ah right - buffer overflow, or anything more exciting? |
01:39.08 | paul | moray: dereference of null pointer |
01:39.11 | moray | ok |
01:40.21 | paul | its trying to look up '#gpe ' in a hash-table - returns result, caller doesnt check for null. |
01:40.42 | paul | it should be looking up '#gpe' |
01:41.06 | paul | i havnt looked at anything gpe related during the week. |
01:41.44 | paul | hopefully will get that dillo web page done over the weekend, small gpe-login change phil wanted and, touch wood, gpe-irc :) |
01:42.41 | paul | moray: anything exciting happening? |
01:44.02 | moray | paul: hm, not especially - if I have time tomorrow I might put some startup notification support into keylaunch |
01:44.10 | paul | ooh. |
01:45.16 | paul | some of the icons have changed on gpe apps, least the size has, eg in gpe-calendar. the icon toolbar no longer completely fits in the screen. |
01:45.26 | paul | same icons, slightly bigger size. |
01:47.01 | pb_ | paul: sounds like you have lost your gpe-confd database |
01:47.08 | pb_ | xst write Gtk/ToolbarIconSize int 2 |
01:47.09 | paul | ah |
01:47.14 | pb_ | (or int 1 if you want them even smaller) |
01:48.03 | paul | pb_: methinks i'm an interesting test case... i see problems others dont, because i always ipkg upgrade - i dont reflash. |
01:48.20 | paul | (is the impression i get anyway) |
01:49.20 | moray | speaking of which, are there new images out yet? |
01:51.48 | paul | pb_: aha, that did the trick. |
01:52.15 | *** join/#gpe dc__ (~dc@modem-58-55-60-62.vip.uk.com) |
01:52.22 | pb_ | moray: no, no sign of pre7 yet. |
01:52.31 | pb_ | paul: yeah, that could well be it. |
01:59.25 | dc__ | sleep :\ |
02:04.30 | paul | anyone else burning the late night oil? |
02:09.53 | pb_ | yeah, but I've had about enough now. |
02:09.59 | pb_ | just been working on gpe-calendar. |
04:06.44 | *** join/#gpe jg (~jg@dialup-67.30.191.123.Dial.Boston1.Level3.net) |
07:32.42 | *** join/#gpe drkness (~sharath@nwkea-http-2.sun.com) |
07:33.04 | drkness | anyone configured their 3900 for irda? |
10:00.44 | *** join/#gpe drkness (~sharath@nwkea-http-1.sun.com) |
10:45.48 | *** join/#gpe drkness (~sharath@nwkea-http-2.sun.com) |
11:07.36 | *** join/#gpe dc_ (~dc@modem-97-48-60-62.vip.uk.com) |
11:07.53 | dc_ | morning :D |
11:08.20 | dc_ | stargirl: up a bit early are we? |
11:08.41 | stargirl | how'd you know I was awake? |
11:08.53 | dc_ | ;-P |
11:09.08 | stargirl | are you in cambridge outside my window? |
11:09.16 | dc_ | oh damn! |
11:09.56 | stargirl | :-) |
11:10.05 | stargirl | did you hear that I got injured? |
11:10.15 | dc_ | no :-\ |
11:10.31 | stargirl | I was cycling and some woman opened her car door without looking |
11:10.37 | stargirl | and I got viciously attacked by it |
11:10.39 | dc_ | ouch! |
11:10.41 | dc_ | :/ |
11:10.49 | stargirl | fortunately, I totalled her car door ;-) |
11:10.58 | dc_ | stargirl: what's the damage report then ;]? |
11:11.01 | stargirl | but I am now in lots of pain from bruising and pulled muscles |
11:11.09 | dc_ | :-{ |
11:11.16 | stargirl | and I have a silly graze on my chin |
11:11.20 | stargirl | which makes me look silly |
11:11.27 | dc_ | oww. |
11:11.43 | dc_ | better stay inside untill it heals then |
11:12.13 | stargirl | yes, else I might never live down thte embarassment |
11:13.51 | stargirl | I had to go to the hospital last night and everything |
11:14.01 | dc_ | have to wait long? |
11:14.10 | stargirl | because I suddenly got worried that I'd broken bones, but it turns out that I hadn't |
11:14.15 | stargirl | nah, it was amazingly quiet |
11:14.22 | stargirl | there was no one there apart from me and the doctors |
11:14.26 | dc_ | thank god. |
11:14.36 | stargirl | yeah, well I made sure I went before the pubs closed |
11:14.45 | stargirl | so I wouldn't get all the drunk kids |
11:14.46 | dc_ | I've had to wait 7 hours in a hospital for some little thing... |
11:14.53 | dc_ | :} |
11:14.54 | stargirl | ooh that's not fun |
11:15.13 | dc_ | then I went in, they took one look and handed me some antibiotics.. |
11:15.21 | stargirl | hehe |
11:15.24 | dc_ | which took under 3 minutes....that was one boring night. |
11:17.16 | stargirl | hehe |
11:18.17 | stargirl | hmm all the tube lines in london today are b0rked |
11:19.18 | dc_ | ack. |
11:19.34 | dc_ | when I was getting back last week the thameslink was down. |
11:19.42 | dc_ | and I had to do some funky tube trips. |
11:34.17 | stargirl | fun fun fun |
11:35.01 | dc_ | hehe, you bot. |
11:35.04 | dc_ | s/bot/bet/ |
12:06.50 | *** join/#gpe pb_ (~pb@pc2-cmbg4-3-cust239.cmbg.cable.ntl.com) |
12:10.48 | *** join/#gpe PaxAnima (~petter@v058b.studby.ntnu.no) |
12:30.14 | *** join/#gpe dan_t (~dan_t@212-41-206-101.adsl.galactica.it) |
12:32.09 | *** join/#gpe Hallski (~micke@ns2.codefactory.se) |
13:04.22 | *** join/#gpe dc_ (~dc@modem-97-48-60-62.vip.uk.com) |
13:06.41 | PaxAnima | hi, dc_ |
13:07.56 | *** join/#gpe dc__ (~dc@modem-251-62-60-62.vip.uk.com) |
13:10.23 | PaxAnima | hi, dc__ |
13:10.50 | dc__ | hey PaxAnima |
13:10.57 | pb_ | dc__: yo |
13:11.02 | dc__ | pb_: morning... |
13:11.32 | dc__ | pb_: my clock got as far as a circle and a white background. |
13:11.41 | dc__ | pb_: I wasted alot of time with gdk_draw_arc |
13:11.55 | pb_ | dc__: ah, heh |
13:12.11 | pb_ | dc__: did you look at the code for mine? |
13:12.19 | dc__ | pb_: gdk seems to want it in 64ths of an angle |
13:12.26 | pb_ | yeah |
13:12.27 | dc__ | pb_: gkttimesel? |
13:12.36 | pb_ | dc__: no, gpe-clock/da-clock.c |
13:12.40 | dc__ | ah |
13:12.43 | dc__ | let me see :) |
13:13.44 | PaxAnima | pb_: what's the good way of doing utf8, without using glib? any other libraries? |
13:13.53 | pb_ | what are you trying to do? |
13:14.24 | PaxAnima | planning to look at libdictionary today, and use utf8 as internal representation |
13:14.52 | pb_ | well, kind of the whole point about utf8 is that you don't need to "do" it in any serious way. |
13:15.47 | PaxAnima | how? |
13:16.42 | pb_ | for most things, the standard C string functions will just work. |
13:18.42 | PaxAnima | aren't there functions for dealing with wide chars etc. I'd have to use? and what about indexing char*? |
13:18.58 | PaxAnima | e.g., mystring[3] = 'æ' |
13:19.05 | dc__ | clock.c: In function `update_time': |
13:19.05 | dc__ | clock.c:44: parse error before `const' |
13:19.05 | dc__ | clock.c:48: `format' undeclared (first use in this function) |
13:19.05 | dc__ | clock.c:48: (Each undeclared identifier is reported only once |
13:19.05 | dc__ | clock.c:48: for each function it appears in.) |
13:19.08 | dc__ | pb_: |
13:19.21 | pb_ | dc__: oops |
13:19.24 | pb_ | C99 strikes again |
13:19.37 | dc__ | :} |
13:19.38 | pb_ | dc__: move line 44 up a bit so it is before lines 42 and 43 |
13:19.47 | pb_ | or get a better compiler |
13:22.38 | *** join/#gpe flypiper (~netwinder@12-222-141-210.client.insightBB.com) |
13:26.55 | pb_ | dc__: I checked that change in, so the code in CVS now should build again. |
13:49.47 | dc__ | pb_: um...okay...what should gpe-clock actualy do? |
13:49.55 | dc__ | ah wait.. |
13:49.57 | dc__ | my bad... |
13:49.59 | pb_ | dc__: it dock itself in the panel bar. |
13:50.03 | dc__ | hrm |
13:50.03 | pb_ | er, docks itself |
13:50.06 | dc__ | damn this gnome2 |
13:50.14 | pb_ | You need to add a "notification area" to the panel under Gnome to make it work. |
13:50.37 | pb_ | (add to panel -> utility -> notification area) |
13:50.48 | dc__ | right. |
13:51.27 | dc__ | pb_: ah great, that's just what I ment :) |
13:51.47 | pb_ | :-) |
13:52.06 | pb_ | I was trying to have it draw the hands anti-aliased with Render this morning, but clearly I am too stupid for that. |
13:52.11 | dc__ | I'll have a go at making it a wind up clock |
13:52.27 | dc__ | pb_: yeah, aa would look very nice |
13:52.51 | pb_ | Maybe we can persuade one of the X Men to help with that. |
13:53.10 | dc__ | hrm |
13:53.23 | dc__ | I'm not sure if wind up or grabbable hands is better |
13:53.35 | pb_ | The grabbable hands seem to work quite well. |
13:53.46 | dc__ | is it usable with a stylus? |
13:53.51 | pb_ | Yeah, it seems to be. |
13:53.57 | dc__ | great |
13:54.04 | pb_ | I think there's an ipk in unstable now if you want to try it out. |
13:54.11 | dc__ | ah cool! |
13:54.19 | dc__ | pb_: you must have been up late last night ;) |
13:54.47 | pb_ | dc__: heh |
13:55.35 | dc__ | pb_: we can always put a nice png behind the hands for the background |
13:55.42 | dc__ | instead of drawing it ourselves. |
13:55.52 | pb_ | yup, good thinking |
13:57.45 | pb_ | dc__: want to have a go at making a proper clock widget that we can put in libgpewidget? |
13:58.25 | dc__ | sure thing |
13:58.31 | pb_ | great |
14:18.49 | pb_ | hm, I guess there needs to be an AM/PM radio button on the clock face as well. |
14:19.20 | dc__ | ah yes! |
14:20.14 | dc__ | yay. new we have a nice bacground |
14:20.19 | pb_ | yay |
14:20.19 | dc__ | s/new/now/ |
14:21.08 | dc__ | umm |
14:21.35 | dc__ | ah.. |
14:22.27 | dc__ | pb_: what gc do I use when I want the color of the widget's default background? |
14:22.55 | dc__ | n/m |
14:25.32 | dc__ | pb_: any idea why it flickers? |
14:25.48 | pb_ | I think because it's redrawing the whole clock every time. |
14:26.11 | dc__ | I guess we should use expose->area then |
14:26.13 | pb_ | It might be possible to make it smarter, by un-drawing the old hands and then drawing the new ones. |
14:26.27 | dc__ | un-drawing? |
14:27.08 | pb_ | well, the problem at the moment is that when it wants to move one of the hands, in order to get rid of the old one it needs to redraw the whole of the background. |
14:27.24 | pb_ | if it was smart enough to just draw background over where the hand used to be, it would flicker less. I think. |
14:29.30 | pb_ | though, I'm not totally convinced that this is the cause of the problem anyway. |
14:30.44 | dc__ | hrm |
14:30.51 | pb_ | ah, hm, maybe I see the problem |
14:30.55 | dc__ | what if we have pixmaps of the hands and rotate then? |
14:30.55 | pb_ | let me check in a fix |
14:31.27 | dc__ | okay, um, can you tell me the fix, because my current code is a bit different.. |
14:31.52 | pb_ | do "cvs diff -u -r1.4 -r1.5 da-clock.c" |
14:31.55 | spung | pb_: why does gpe-login continue to run after login? ps reports its VmSize is 11M |
14:31.59 | dc__ | right |
14:32.05 | pb_ | spung: autolock |
14:32.38 | spung | pb_: maybe it should drop the background to save mem? |
14:32.49 | pb_ | I don't think it loads the background. |
14:32.58 | pb_ | if it does, yes, that would be a bug. |
14:33.17 | spung | pb_: what do you mean? |
14:33.35 | spung | isn't gpe-login "transparent" ? |
14:33.50 | pb_ | yeah |
14:34.06 | spung | 14:34 <pb_> I don't think it loads the background. |
14:34.14 | spung | well then? |
14:34.50 | pb_ | well then, gpe-login doesn't actually load the background image, it just allows its parent window to show through. |
14:35.11 | pb_ | it is also not transparent in autolock mode. |
14:35.16 | spung | pb_: i thought X didn't have real transparent? |
14:35.34 | spung | transparency |
14:35.53 | pb_ | it doesn't, but it has enough transparency for this purpose. |
14:36.32 | spung | pb_: i thought librootimage created a new pixmap? |
14:37.29 | pb_ | yes, it does. I didn't think gpe-login used librootimage, but even if it does, it is still not being used in autolock mode. |
14:38.05 | dc__ | pb_: that fix won't work with a pixbuf as the background |
14:38.20 | pb_ | dc__: oh dear. why not? |
14:38.56 | pb_ | ah, I suppose you just don't have those arc calls any more. |
14:39.00 | dc__ | pb_: because the border isn't drawen anymore. |
14:39.02 | dc__ | pb_: yes |
14:39.06 | pb_ | right |
14:39.08 | spung | pb_: just checked, yes, you do use librootimage :) |
14:39.11 | dc__ | let me try and use event->ara |
14:39.16 | dc__ | s/ara/area/ |
14:39.19 | pb_ | dc__: in that case I guess your flickering must have had a different cause to mine |
14:39.35 | spung | pb_: is it being free'd when you change to autolock mode? |
14:40.18 | pb_ | spung: you don't ever change to autolock mode dynamically. the mode is set when gpe-login is started, and never changed. |
14:40.42 | pb_ | it follows a substantially different code path to normal operation. |
14:41.18 | spung | pb_: hmmm, I see. does gpe-login restart when you logout? |
14:41.23 | pb_ | yes |
14:41.41 | pb_ | it's launched from Xinit.d |
14:42.01 | spung | pb_: hmm, then it'd be easier to free librootimage's created pixmap after login no? |
14:42.22 | pb_ | umm |
14:42.37 | spung | pb_: or maybe ps is tricking me? |
14:43.04 | pb_ | well, unless you have a more advanced ps than me, it doesn't even claim to show you which pixmaps exist. |
14:43.34 | pb_ | when you log in, gpe-login dies, and its pixmaps ought to go away as well. |
14:43.43 | spung | ohhh |
14:43.58 | pb_ | if that's not happening, yes, it would be a bug, but I haven't seen any evidence to suggest it's the case. |
14:44.12 | spung | pb_: yes, of course.. |
14:44.17 | pb_ | I guess the new XRes extension would allow us to find out though |
14:44.30 | spung | pb_: so, gpe-login dies and a new one (with --autolock) is started? |
14:44.33 | pb_ | yes |
14:44.51 | spung | ahh, makes no sense what I'm saying then :) |
14:45.08 | pb_ | :-} |
14:45.15 | spung | just sounded alarming it's VmSize that's all |
14:45.22 | spung | probably doesn't mean anything |
14:45.24 | pb_ | vmsize doesn't mean a whole lot. |
14:45.28 | spung | yeah |
14:45.56 | pb_ | once you've got libc, libgtk, libx11, libxft and some fonts you are probably up to 9 or 10MB quite easily. |
14:46.15 | spung | ahhh, I see |
14:46.18 | pb_ | but, none of this is real RAM, so there is no point in worrying about it too much. |
14:46.33 | spung | that explains why gpe-today has such a big size |
14:46.37 | spung | it links to tons of libs |
14:46.41 | pb_ | you can check in /proc/pid/maps to see what is mapped. |
14:49.11 | dc__ | pb_: why is there all this x_offset stuff? |
14:49.37 | pb_ | dc__: to cope with the drawing area not being square |
14:49.48 | dc__ | and why isn't it squre? |
14:50.01 | pb_ | gtk can allocate it any size it wants. |
14:50.15 | dc__ | heh |
14:50.49 | pb_ | right now I think it actually always is square, but if it's made into a proper widget that won't necessarily be the case. |
14:51.03 | dc__ | ahh, okay |
14:51.21 | pb_ | a widget can request a square box with its requisition, but it is not guaranteed to get that back in the actual allocation. |
14:51.54 | pb_ | if it winds up packed into a box with EXPAND set, it can get stretched out in one dimension or the other. |
15:01.54 | spung | pb_: gpe-calendar2 0.40 seems to have a messed up .desktop |
15:02.06 | pb_ | oh dear |
15:02.08 | pb_ | what's wrong with it? |
15:02.34 | spung | pb_: well, are you sure an old .destkop didn't get packaged by mistake? |
15:02.45 | spung | i remember make clean failing to remove old .desktop's |
15:03.08 | pb_ | ah. |
15:03.16 | pb_ | make clean certainly ought to remove the old ones. |
15:03.42 | spung | pb_: btw, ipkg installed all gpe-calendar-* translations, is that a known bug? |
15:03.53 | pb_ | yeah, I think jamey broke it yesterday. |
15:03.58 | spung | lol |
15:06.18 | spung | pb_: can you try gpe-today out, don't you think that the dragging of the gtkpaned sucks? |
15:06.54 | pb_ | yeah, I think I tried it before. |
15:07.03 | spung | ah ok |
15:07.22 | spung | it seems that gtk is drawing twice |
15:07.36 | pb_ | yeah. did you have any luck asking the gtk folks about that? |
15:07.42 | spung | not really |
15:07.46 | pb_ | :-/ |
15:07.51 | spung | i'll try again |
15:07.53 | spung | :) |
15:08.01 | pb_ | yeah, looks like gpe-calendar's makefile is wrong. I'll fix that. |
15:08.54 | *** join/#gpe dc___ (~dc@modem-154-59-60-62.vip.uk.com) |
15:11.30 | pb_ | I plan to do another new gpe-calendar release this weekend anyway, to tie in some alarm stuff (and hopefully make tasks work as well), so it should get mopped up then. |
15:17.04 | dc___ | oh no, gdk stole my mouse! |
15:18.03 | pb_ | ! |
15:18.19 | pb_ | hate it when that happens. |
15:18.26 | dc___ | yes.. |
15:18.38 | dc___ | something isn't right with my code ;) |
15:18.44 | pb_ | heh |
15:18.51 | pb_ | suspected as much |
15:19.15 | dc___ | crashing on my gdk_rectangle_intersect....must be faulty rects. |
15:19.26 | pb_ | yeah |
15:25.04 | dc___ | pb_: mind if I commit the broken background code ;}? |
15:26.00 | pb_ | dc___: sure, go for it. |
15:26.06 | dc___ | :} |
15:26.16 | pb_ | it'll make a change from looking at my broken atd code. |
15:26.23 | dc___ | hehe |
15:28.16 | dc___ | pb_: right... |
15:28.37 | pb_ | dc___: so, what seems to be the problem? |
15:28.54 | dc___ | pb_: compile and run |
15:29.08 | dc___ | pb_: segfaults at gdk_rectangle_intersect. |
15:29.12 | pb_ | ok |
15:29.17 | pb_ | let me run it in Xnest to be safe :-} |
15:29.24 | dc___ | ah eyah |
15:29.26 | dc___ | do that too :) |
15:29.31 | pb_ | ah, I see. |
15:29.34 | pb_ | nice pixmap though :-) |
15:29.42 | dc___ | yes... |
15:30.31 | pb_ | ah, you are not coping with the NULL event you get from adjustment_value_changed (). |
15:30.55 | dan_t | hello. any ipkg developper here ? |
15:31.32 | pb_ | I'm not sure what to do about that. We could try to have it supply a proper event struct, I guess, but it might not be easy to figure out what rectangle to supply. |
15:32.26 | dc___ | pb_: oh I see, for the spin buttons? |
15:32.38 | pb_ | yeah |
15:32.46 | pb_ | but that's also the mechanism for moving the hands when you drag. |
15:32.58 | dc___ | damn... |
15:34.11 | pb_ | well, let me see what I can come up with |
15:35.44 | pb_ | dc___: what's the gdk_draw_rectangle (gray_gc) required for? |
15:40.20 | cmarqu | pb_: Can you make the help tooltips match the color of the ones for the matchbox dock apps? |
15:40.34 | pb_ | cmarqu: Yeah. |
15:41.15 | *** join/#gpe dc___ (~dc@modem-154-59-60-62.vip.uk.com) |
15:52.20 | pb_ | dc___: okay, I just checked in some changes. try that and see if it's better. |
15:57.48 | dc___ | pb_: much better :) |
15:57.55 | pb_ | cool |
15:59.40 | dc___ | now the only problem we have is our ugly hands |
15:59.57 | pb_ | yeah |
16:02.08 | dc___ | I have a really cool idea for the AM/PM display |
16:02.18 | dc___ | that would just make people go 'awww' |
16:02.20 | dc___ | but.. |
16:02.42 | dc___ | the clock hands need to be slightly transparent for it to work properly |
16:02.51 | pb_ | well, we could manage that. |
16:03.04 | dc___ | :) |
16:03.21 | pb_ | if we can get Render working for the hands, it supports translucent drawing. |
16:03.24 | dc___ | I'm thinking of having a little wheel in the center of the clock with a sun and moon on it. |
16:03.28 | dc___ | pb_: ah cool |
16:03.35 | pb_ | ah, ingenious. |
16:03.41 | cmarqu | Oh, then we could overlay the hands with ownerinfo too maybe? |
16:03.55 | pb_ | as an alternative to render, we could just use pixmaps for the hands and rotate them. But that might be slow and yield bad results. |
16:04.06 | dc___ | then the bottom half of the wheel is shaded out, and it spins round with the time selected. |
16:04.14 | pb_ | sounds good |
16:04.25 | dc___ | plus it'll looks even better ;D |
16:04.40 | pb_ | :-) |
16:04.47 | *** join/#gpe mallum (~mallum@pc-80-193-218-21-hw.blueyonder.co.uk) |
16:04.52 | dc___ | he mallum |
16:05.29 | mallum | hey dc__________________ |
16:05.35 | dc___ | hehe |
16:06.49 | mallum | dc___: whats new ? |
16:07.10 | dc___ | mallum: gpe/base/gpe-clock |
16:07.20 | dc___ | mallum: have a look at the 'Alarm...' menu item :) |
16:07.41 | mallum | dc___: what is it ? |
16:08.10 | dc___ | mallum: a clock with draggable hands |
16:08.15 | dc___ | mallum: to set the time for an alarm |
16:08.26 | mallum | dc___: oh cool |
16:08.53 | mallum | dc___: a mini analog dock app clock would be cool :-) |
16:09.13 | dc___ | mallum: well, apart from the lack of space :\ |
16:09.28 | dc___ | mallum: I don't think 16x16 is enough for one |
16:10.25 | mallum | dc___: yeah, Im writing a whole new api for the panel apps |
16:10.35 | mallum | dc___: so they handle scaling etc |
16:10.55 | mallum | dc___: 16x16 apps are just too small on 640x480 |
16:11.12 | dc___ | mallum: ah, maybe when that's finished then :) |
16:12.57 | dc___ | I find it really amusing that the new gnome2 stock icons look fine without aa. |
16:13.10 | dc___ | set gnome 1.2 stock looked really bad without aa. |
16:13.18 | dc___ | like they should be the other way round |
16:13.35 | dc___ | BBrox: ;) |
16:13.49 | dc___ | BBrox: wait till we have the sun and moon :D |
16:17.24 | mallum | dc___: how do you remove the AA from them ? |
16:18.42 | dc___ | mallum: well, I was just saying, say the new icon in 1.2. |
16:18.58 | dc___ | mallum: it's from a perspective, so it looks crap without aa. |
16:19.15 | dc___ | mallum: whereas all the gnome2 icons are front on with not many curves. |
16:20.41 | chrisime | hey all |
16:23.51 | dc___ | hello chrisime |
16:24.39 | pb_ | hm, I need to get a better X server. |
16:24.44 | dc___ | :} |
16:24.47 | dc___ | don't we all pb_ |
16:25.00 | *** join/#gpe TheMasterMind1 (foobar@h-68-166-65-211.MCLNVA23.covad.net) |
16:25.10 | pb_ | this poxy one on my desktop doesn't seem to do Render properly. |
16:25.18 | dc___ | eek |
16:25.21 | dc___ | that does suck |
16:25.30 | pb_ | 4.2.1 :-/ |
16:27.16 | mallum | pb_: I've been running these 4.3 exp debs on the tablet and they seem ok |
16:27.53 | pb_ | yeah, I guess that's what I should get. |
16:31.29 | mallum | pb_: arg, though it seems its missing all the xrandr headers :( |
16:34.05 | mallum | pb_: hmmm forget that |
16:34.51 | spung | mallum: have you considered making figment available in debian? i've fallen in love with this outliner thing :) |
16:35.26 | mallum | spung: :-) |
16:36.08 | mallum | spung: I think its a little broke at the mo ? |
16:37.51 | spung | mallum: is it? |
16:37.59 | spung | why? |
16:38.09 | spung | why can't I teleport it btw? |
16:38.57 | mallum | spung: I though gtk2.2 bust it a bit |
16:39.41 | mallum | spung: its needs to compiled againsts pb's teleport library to do that |
16:40.32 | *** join/#gpe TMM1 (foobar@h-68-166-65-209.MCLNVA23.covad.net) |
16:41.28 | spung | ohh |
16:41.39 | spung | mallum: it'd be cool to be able to teleport it |
16:42.00 | *** join/#gpe TheMasterMind1 (foobar@h-68-166-65-209.MCLNVA23.covad.net) |
16:43.11 | dc___ | yy |
16:43.12 | dc___ | yay |
16:43.20 | dc___ | behold the wheel of day and night |
16:43.38 | pb_ | cool |
16:43.50 | BBrox | dc___: screenshot :-) |
16:44.37 | dc___ | be patient ;] |
16:44.43 | dc___ | pb_: now....my question. |
16:44.57 | dc___ | pb_: how do we put a transparent box over half of it? |
16:45.13 | pb_ | I guess I'd have to see the code first. |
16:45.21 | dc___ | heh right... |
16:45.36 | pb_ | :-) |
16:51.37 | dc___ | awwwww |
16:51.40 | dc___ | it looks so cute :D |
16:51.43 | pb_ | heh |
16:51.56 | mallum | spung: why not grab it from CVS and hack on it a bit ;-) |
16:52.33 | dc___ | pb_: it might make sense to color the hand blue or something aswell. |
16:52.41 | pb_ | yep |
16:53.54 | mallum | dc___: is there a scap of it ? |
16:54.02 | dc___ | not yet. |
16:54.08 | dc___ | pb_: now we need some rotation code :\ |
16:55.18 | dc___ | pb_: checked into cvs btw. |
16:55.25 | pb_ | great |
16:56.10 | dc___ | pb_: do you have any ideas for the whereabouts of some rotation code with smoothing aswell? |
16:56.43 | pb_ | dc___: hm, not really. But I think I just about have Render working for the hands, if that's what you were planning to use it for. |
16:56.58 | dc___ | yes |
16:57.18 | pb_ | the problem I was having earlier turned out to be that it was interacting badly with Gdk's double buffering. |
16:57.24 | dc___ | pb_: cool, so...yeah, what I plan to do is rotate the little wheel in the center |
16:57.30 | dc___ | pb_: ah |
16:58.13 | pb_ | ah yes, looks nice |
17:01.41 | dc___ | hrm |
17:01.56 | pb_ | well, I checked in a very rough cut of the render stuff. |
17:02.11 | pb_ | it will be desperately flickery to start with; I need to put the double buffering back in to stop that. |
17:02.12 | dc___ | pb_: if we can draw a transparent polygon there will be no need for any rotation code. |
17:02.25 | dc___ | okay |
17:02.42 | dc___ | um |
17:02.44 | pb_ | dc___: yeah, take a look at the new hand drawing routine. it should be fairly obvious how to tweak it for other arbitrary transparent polygons |
17:02.53 | dc___ | ./gpe-clock: relocation error: /opt/garnome-0.19.3/lib/libXft.so.2: undefined symbol: XRenderQuerySubpixelOrder |
17:02.58 | dc___ | pb_: oh course :) |
17:03.10 | dc___ | I ehh...hope that's not my xserver. |
17:03.14 | pb_ | ah, hm, sucks. seems your libxrender is out of date. |
17:03.22 | dc___ | hum |
17:03.40 | mallum | pb_, dc___: in case you hadn't already noticed, xclock and xlogo have a lot of xrender code in them |
17:03.58 | dc___ | doh |
17:04.02 | pb_ | dc___: but this is most likely a bad path, as if your libxft2 was really broken no gnome program would work |
17:06.36 | dc___ | pb_: any suggestions? |
17:06.57 | pb_ | dc___: do "ldd ./gpe-clock", see where it is getting libXrender from. |
17:07.05 | dc___ | just did...hrm |
17:07.11 | pb_ | then compare that to some gnome program that works |
17:07.42 | mallum | dc___: do you have a /usr/X11R6/lib/libxft.so.2 ? |
17:07.43 | dc___ | ah okay. |
17:07.51 | dc___ | now....how do I stop it using the wrong one? |
17:08.03 | pb_ | check $LD_LIBRARY_PATH, I guess |
17:08.26 | pb_ | I'm not sure what garnome is doing, maybe some bad stuff with -rpath. |
17:09.30 | *** join/#gpe dc__ (~dc@62.60.118.234) |
17:09.44 | dc__ | eek |
17:09.46 | dc__ | well I changed a line in /etc/ld.so.conf |
17:09.49 | dc__ | and it start now... |
17:09.54 | pb_ | aha |
17:09.56 | dc__ | but then I get: |
17:10.04 | dc__ | Gdk-ERROR **: The program 'gpe-clock' received an X Window System error. |
17:10.04 | dc__ | This probably reflects a bug in the program. |
17:10.04 | dc__ | The error was 'BadImplementation (server does not implement operation)'. |
17:10.04 | dc__ | <PROTECTED> |
17:10.04 | dc__ | <PROTECTED> |
17:10.05 | dc__ | <PROTECTED> |
17:10.07 | dc__ | <PROTECTED> |
17:10.09 | dc__ | <PROTECTED> |
17:10.09 | pb_ | oh dear |
17:10.11 | dc__ | <PROTECTED> |
17:10.12 | pb_ | your X server sucks too |
17:10.13 | dc__ | aborting... |
17:10.15 | dc__ | flood :} |
17:10.17 | pb_ | that's what mine does. |
17:10.30 | dc__ | suck. |
17:10.51 | pb_ | X 4.2.1 doesn't seem to support XRenderCompositeDoublePoly. |
17:10.59 | dc__ | :( |
17:11.00 | dc__ | suck |
17:11.05 | pb_ | try running it with $DISPLAY pointing at the ipaq, that's what I had to do. |
17:11.09 | dc__ | but my iPAQ should... |
17:11.10 | dc__ | yeah |
17:11.11 | dc__ | quite. |
17:17.10 | dc__ | weird... |
17:17.20 | dc__ | ssh gone from unstable. |
17:17.29 | pb_ | oh, I think that's an ipkg bug. |
17:17.34 | dc__ | yeah |
17:17.35 | dc__ | I see... |
17:17.41 | dc__ | it's in the package list |
17:17.55 | pb_ | you might need to tweak ipkg.conf |
17:18.18 | pb_ | or get latest ipkg if you haven't already. |
17:18.32 | dc__ | ahha |
17:19.01 | pigeon | ... |
17:19.09 | pigeon | Can someone tell me what's the time in Sydney now? |
17:20.23 | dc__ | pigeon: apparently it's march 30th -3:16 |
17:20.29 | dc__ | 03:16 |
17:20.39 | pigeon | Damn it. |
17:20.44 | pigeon | Daylight saving. |
17:20.51 | dc__ | heh |
17:20.54 | pigeon | I woke up an hour earlier. |
17:21.08 | dc__ | pigeon: hehe |
17:21.15 | pigeon | And I need to go to the airport. |
17:21.15 | pb_ | heh |
17:21.34 | dc__ | pigeon: earlier.... |
17:21.43 | dc__ | pigeon: that can't be a bad thing can it? |
17:21.57 | pigeon | Considering I was sick, maybe not :\ |
17:22.43 | dc__ | hrm |
17:22.53 | dc__ | pb_: the iPAQ doesn't have enough space for the clock :\ |
17:23.06 | pb_ | dc__: yeah, I noticed. |
17:23.07 | pigeon | I hope the time of the flight is daylight saving adjusted as well. -.- |
17:23.25 | pigeon | I'm going back to bed. |
17:23.25 | pb_ | dc__: but if the clock is going in a popup window, shouldn't be a problem |
17:24.31 | dc__ | yeah |
17:24.36 | dc__ | but man it looks cool. |
17:24.49 | dc__ | pb_: eek, you've brung back my old problem |
17:25.20 | pb_ | dc__: which one was that? |
17:26.08 | pb_ | dc__: I still have some changes to make to the drawing, but I need to go out for a bit first. I'll do them in a couple of hours. |
17:27.16 | dc__ | pb_: right, let me just show you this scap |
17:27.23 | pb_ | ok |
17:27.24 | dc__ | pb_: I'm going out in 15 minutes aswell |
17:27.58 | dc__ | pb_: http://handhelds.org/scap/port.2510.png |
17:28.16 | dc__ | mallum, BBrox: http://handhelds.org/scap/port.2510.png |
17:28.24 | pb_ | dc__: scap looks nice. |
17:28.36 | dc__ | pb_: even though it looks alright, the heavy border around the bottom of the clock isn't supposed to be there. |
17:28.46 | dc__ | pb_: it's just supposed to be a light shadow. |
17:29.26 | dc__ | pb_: but when 1 or more clock are drawen on top of each other, the transparency counts up and makes the border blacker with each expose event |
17:29.31 | pb_ | dc__: okay, I'll look at that. |
17:29.52 | pb_ | dc__: guess I shouldn't have removed that background-clearing line. |
17:30.02 | dc__ | pb_: quite. |
17:30.07 | pb_ | doh :-} |
17:30.09 | spung | dc__: you should make the pointer darker/wider |
17:30.18 | dc__ | spung: yeah |
17:30.27 | dc__ | pb_: step up the opacity a bit. |
17:31.13 | pb_ | dc__: you can tweak it at line 282. want to experiment and find a good number? |
17:31.24 | dc__ | sure |
17:32.03 | pb_ | we can also experiment with different shaped hands to see if we can find anything that looks a bit prettier. |
17:32.17 | dc__ | pb_: um, 282 in which file? |
17:32.35 | pb_ | dc__: da-clock.c |
17:32.49 | pb_ | oh, I checked in some recent changes, you might need to update. |
17:32.52 | pb_ | the line should read |
17:32.54 | pb_ | <PROTECTED> |
17:33.44 | dc__ | ah, bad emacs. |
17:34.27 | pb_ | ah |
17:35.55 | mallum | dc__: oh, very nice |
17:36.31 | mallum | dc__: why not make the arms non transparent so clearer and mybe give them transparent shadows ? |
17:40.40 | dc__ | mallum: that would look nice :} |
17:41.08 | dc__ | all the opie people can drool over our clock now |
17:41.18 | PaxAnima | dc__: ;) |
17:46.17 | dc__ | time to go... |
17:46.18 | dc__ | bbl |
18:04.03 | spung | pb_: what flags are set when an event is a reminder? (but has time set) |
18:04.27 | *** join/#gpe Hallski (~micke@lite-149-247.umenet.net) |
18:05.30 | spung | ahh, maybe duration = 0 |
18:24.16 | *** join/#gpe dc__ (~dc@modem-200-48-60-62.vip.uk.com) |
18:30.21 | BBrox | dc__: well, it's nice.. But it's kinda confusing :-) |
18:30.26 | pb_ | spung: I think a reminder is just an event with no duration. |
18:30.50 | pb_ | BBrox: hm, confusing in what way? |
18:31.25 | BBrox | pb_: well, the sun up means AM or PM :-) ? |
18:31.58 | pb_ | ah, yeah, I can see that bit would be confusing. |
18:32.03 | pb_ | I wonder what to do about it. |
18:32.05 | spung | BBrox: good point :) |
18:32.24 | BBrox | As AM is half day, half night and the same for PM :-) |
18:32.27 | pb_ | it would certainly make no sense to have the sun up at 1am. |
18:32.58 | BBrox | It certainly looks nice though |
18:33.09 | spung | pb_: except if you're your in the north pole in that time of the year :) |
18:33.56 | pb_ | I guess we could put the changeover points at 06:00 and 18:00 instead, which would probably make it work out OK if you didn't think about it too much. |
18:34.09 | pb_ | ie 3 o'clock, sun up = 3pm, sun down = 3am |
18:34.19 | pb_ | 7 o'clock, sun up = 7am, sun down = 7pm |
18:34.21 | pb_ | etc |
18:35.15 | pb_ | well, that's probably something for dc to worry about. |
18:35.22 | pb_ | I will fix the drawing code though. :-] |
18:35.34 | BBrox | Well, I would see the 'Sun / Moon' stuff rotating also.. |
18:35.48 | BBrox | Ie showing the hour at a 24 hour format instead of 12 hours like the dial |
18:36.27 | BBrox | Or a marker on the 'Sun / Moon' stuff moving in a 24 hour format and clikcing on the disk would switch the marker to 12 hours later. |
18:36.52 | pb_ | Yeah. I'm not sure which Damien planned to do. |
18:37.22 | BBrox | BTW, played the other day with Motorola's Linux phone |
18:37.34 | BBrox | Need to put X and GPE on it :-) |
18:37.40 | pb_ | heh, cool |
18:38.02 | BBrox | It's really a nice looking phone... |
18:41.12 | pigeon | Hey bbrox |
18:42.44 | BBrox | 'lo pigeon |
18:49.49 | *** join/#gpe chrisime_ (~chrisime@p5080269F.dip0.t-ipconnect.de) |
18:57.10 | mallum | spung: btw, figment is in garnome |
19:15.47 | spung | pb_: sorry but i have to say this... gtk_simple_menu_new() makes people spend a lot of time searching for docs on google, and gtk api references :\ |
19:16.02 | spung | i'm refering to choice of name, of course |
19:16.03 | spung | :\ |
19:16.25 | pb_ | spung: best write some docs then |
19:16.46 | spung | pb_: what i mean, is I thought it was a gtk function and couldn't find the docs |
19:17.02 | pb_ | yes, I know what you meant. |
19:17.31 | spung | pb_: why not gpe_simple_menu_new() ? |
19:17.51 | pb_ | no particular reason. |
19:18.02 | spung | :\ |
19:20.00 | *** join/#gpe dneuer (~smoothie@192.204.192.36) |
19:20.07 | spung | anyway, I was trying to fix a small gpe-calendar bug.. is it not possible to change the selected item in a "gtk_simple_menu" through code? |
19:20.57 | pb_ | yeah, it derives from GtkOptionMenu, so those functions should work. |
19:21.15 | spung | ahh |
19:21.23 | spung | cool |
19:31.29 | spung | pb_: is gpe-calendar's week_view broken or something? |
19:31.38 | pb_ | dunno. what seems to be the problem? |
19:31.48 | spung | does it require a super up-to-date gtk? |
19:31.55 | pb_ | dunno |
19:32.01 | spung | week_view.c: In function `draw_expose_event': |
19:32.01 | spung | week_view.c:140: parse error before `*' |
19:32.01 | spung | week_view.c:142: `buffer' undeclared (first use in this function) |
19:32.09 | spung | plus a couple of other comile errors |
19:32.22 | pb_ | oh, that |
19:32.26 | pb_ | mccarthy had that problem too. |
19:32.31 | pb_ | you need a newer compiler. |
19:32.37 | spung | hmm |
19:32.39 | pb_ | I'll fix the code. |
19:33.56 | pb_ | okay, I fixed that one. |
19:34.23 | spung | pb_: what's wrong with that code? i don't see anything too weird? |
19:34.36 | spung | ahhhhh |
19:34.37 | spung | nevermind |
19:34.44 | spung | C99 stuff |
19:34.44 | spung | :) |
19:34.51 | spung | that's evil!! |
19:35.09 | spung | declaring a var there, that's soooo evil :) |
19:35.40 | dneuer | hey all |
19:36.02 | dneuer | what format are .ipk files in? I thought they were tar.gz's |
19:38.55 | spung | dneuer: that's the old format |
19:39.20 | dneuer | what's the new format? |
19:39.24 | spung | dneuer: good question :) |
19:39.44 | spung | just a sec |
19:39.45 | dneuer | well that's a little irritating |
19:40.02 | pb_ | dneuer: they're ar now, same as .deb. |
19:40.12 | spung | dneuer: there you go |
19:40.37 | dneuer | ar? How do you un-ar something? |
19:40.43 | pb_ | with ar |
19:40.53 | pb_ | ar x package.ipk |
19:41.03 | pb_ | or use dpkg-deb or ipkg-unbuild |
19:41.31 | dneuer | ipkg-unbuild is a script? |
19:41.35 | pb_ | yep |
19:41.35 | dneuer | or a binary? |
19:41.40 | dneuer | ok |
19:41.43 | pb_ | script. it's in ipkg-utils cvas |
19:41.46 | pb_ | cvs |
19:43.37 | dneuer | pb_: I assume ipkg-unbuild depends on ar? I dont' have ar on my system |
19:43.50 | pb_ | dneuer: yeah, probably. ar is part of binutils, so most people would have it. |
19:44.39 | dneuer | ok, I do have it, there's just no manpage |
19:44.46 | pb_ | ah. |
19:48.27 | dneuer | pb_: ok, here's where I get confused: task-bluez's control file just has bluez-utils, bluez-libs, bluez-pan, bluez-sdp, etc. |
19:48.48 | dneuer | no version #s. But there are packages in unstable w/ very weird version #s |
19:49.11 | dneuer | lie bluez-utils_2.2-khh2_arm.ipk |
19:49.14 | dneuer | like |
19:49.29 | pb_ | right |
19:49.40 | dneuer | or, alternatively, bluez-utils_2.2_kc1_arm.ipk |
19:49.51 | dneuer | or bluez-utils_2.2-hh2_arm.ipk |
19:50.03 | dneuer | which is the one that would get installed? |
19:50.22 | dneuer | or *should* get installed, which is really what I care about |
19:50.31 | pb_ | not sure. I'm guessing the latter. The first one has a malformed version number. |
19:51.49 | dneuer | another question: is the kernel which is part of familar .7pre6 known to be completely screwed? |
19:52.55 | pb_ | not that I know of. Russ is in process of building pre7, so it should be a moot point soon in any case. |
19:53.35 | dneuer | pb_: why, is he putting hh8 in? |
19:53.40 | pb_ | yeah |
19:53.51 | dneuer | ok |
19:54.04 | pb_ | the images are usually built from the latest packages at that time. |
19:54.37 | dneuer | I'm having all kinds of problems w/ hh6 (like going to sleep for the 2nd time means never being able to wake up again) |
19:55.00 | pb_ | strange |
19:55.05 | dneuer | I agree |
19:55.07 | pb_ | I've never seen that. |
19:55.13 | pb_ | what model of ipaq is that on? |
19:56.42 | dneuer | pb_: 3650, souped up (extra RAM) |
19:57.39 | pb_ | did you try hh8? |
19:58.39 | dneuer | pb_: not yet. I was going to build cvs today and try that instead |
19:59.18 | dneuer | I find it's still easier to forget about ipkg for kernel stuff and just zmodem a kernel and modules tar'd up |
19:59.29 | pb_ | right |
20:00.53 | dneuer | I'm on an obsessive mission to get my Belkin BT card working |
20:02.59 | dneuer | does MonMotha not have hh commit privs? |
20:03.29 | pb_ | not sure |
20:03.49 | dneuer | I remember yesterday before jamey left, jamey was told him to open a bug report if CONFIG_MAGIC_SYSRQ wasn't turned on in def-configs/h3600 |
20:03.53 | pb_ | no, he doesn't. |
20:04.01 | dneuer | I can change it, and commit it |
20:04.12 | pb_ | ok, cool, go for it. |
20:04.23 | pb_ | fwiw, members of proj_linux are a7r,andyc,anoncvs,ayer,bavery,chri,christopher,cworth,davep,dneuer,duffekn,dwkim,dwmw2,france,gcolburn,gitars,jamey,jca,jg,jjburch,joshua,ksteele,nils,pb,timr,wim |
20:04.27 | dneuer | h3600 is the right one, correct? |
20:04.32 | pb_ | yeah |
20:04.37 | pb_ | be worth changing h3900 also |
20:04.47 | dneuer | ok, can do |
20:12.18 | spung | pb_: let me know when you're back :) |
20:14.05 | spung | dneuer: that away was fast, what did you do? smack him? |
20:22.58 | *** join/#gpe dc___ (~dc@modem-15-62-60-62.vip.uk.com) |
20:33.53 | PaxAnima | yay! my image library can now render (ugly, fixed font) text!... |
20:34.11 | spung | yay |
20:34.17 | PaxAnima | http://v058b.studby.ntnu.no/images/test_font.png |
20:35.13 | spung | PaxAnima: I can confirm that it is text |
20:35.22 | PaxAnima | spung: good ;) |
20:35.30 | spung | lol :) |
20:37.32 | PaxAnima | good to know it wasn't the coffee that gave me halucinations... |
20:37.59 | spung | pb_: ahh, prepare to be flooded |
20:38.33 | spung | pb_: after i do a gtk_option_menu_set_history() on a gtk_simple_menu |
20:38.56 | spung | pb_: gtk_simple_menu_get_result() and gtk_option_menu_get_history() return different values |
20:39.06 | pb_ | ah, hm. |
20:39.24 | pb_ | yeah, we should just make gtk_simple_menu_get_result call gtk_option_menu_get_history. |
20:40.21 | spung | pb_: that's a barrier to my fix of the day :\ |
20:41.41 | spung | pb_: so, we should get rid of guint item in _GtkSimpleMenu |
20:42.12 | spung | pb_: and change every instance of sm->item = 0; to gtk_option_menu_set_history() ? |
20:43.28 | pb_ | well, try the change I just checked in. |
20:43.39 | spung | cool |
20:45.29 | dneuer | pb_: you understand the IRQ stuff? |
20:45.37 | pb_ | dneuer: mostly, I guess |
20:46.40 | dneuer | pb_: andyc broke the compile yesterday. Specifically, IRQ_H3800_MMC in h600.c is not declared in irqs.h |
20:46.56 | pb_ | ah, ok, lemme look |
20:47.08 | pb_ | this is h3600 compile, right? |
20:47.23 | dneuer | pb_: I can see where he moved it from, but it was called something else, and it was defined as IRQ_GPIO18 |
20:47.28 | dneuer | yeah |
20:48.30 | pb_ | well, I guess it should just be defined in irqs.h with all its friends. |
20:48.42 | dneuer | pb_: so, in irqs.h, I'm trying to figure out what would be correct for IRQ_GPIO18. It seems like it should be IRQ_BOARD_START + 11, but that's take by IRQ_H3800_USB_DETECT |
20:48.54 | dneuer | taken |
20:49.11 | pb_ | hm, actually I have EAR_IN at board_start + 11 |
20:49.21 | dneuer | oops, right, just caught that |
20:49.37 | dneuer | which means nothing to me |
20:49.50 | dneuer | I know nothing about the 3800's |
20:50.42 | pb_ | I think you should just be able to #define IRQ_H3800_MMC IRQ_GPIO18 |
20:51.20 | pb_ | or use IRQ_GPIO_H3800_MMC_INT, defined in h3600_asic.h |
20:52.24 | dneuer | pb_: well, sure, but that doesn't fit the scheme in irqs.h for board-specific irqs |
20:52.37 | pb_ | I don't think it's board-specific in that sense. |
20:52.59 | pb_ | The "board specific" irqs are ones that are generated by the ASIC and need to be specially demuxed. |
20:53.36 | pb_ | It sounds like the MMC interrupt arrives directly at a gpio pin on the sa-1110, so no further indirection is required. |
20:54.37 | dneuer | hmmm |
20:55.00 | dneuer | it was moved from h3600_asic.c |
20:55.01 | pb_ | this is why the board-specific ones are arranged in two groups, for the GPIO and KPIO blocks in the rosella chip. |
20:55.15 | dneuer | rosella chip? is that the asic? |
20:55.25 | pb_ | yeah, "asic2" |
20:55.53 | pb_ | there's also an "asic1" in h3800, or "asic3" in h3900. |
20:57.09 | pb_ | when you say h3600_asic.c, which file do you mean? h3600_asic.c itself has been dead for months. |
20:57.51 | pb_ | dinner time, bbl |
20:58.13 | dneuer | really? that's where the disable interrupt code was moved from, by andy, yesterday (into h3600.c) |
21:54.08 | *** join/#gpe idleo (~idleo@dsl-217-155-193-217.zen.co.uk) |
22:07.42 | *** join/#gpe jg (~jg@dialup-63.214.91.243.Dial1.Boston1.Level3.net) |
22:08.21 | dneuer | hi jg |
22:09.36 | jg | dneuer: hi |
22:10.28 | dneuer | jg: what's mwvlan? |
22:11.14 | jg | dneuer: dunno.... |
22:20.21 | pb_ | dneuer: check "cvs log h3600_asic.c" |
22:20.25 | pb_ | revision 1.29 |
22:20.28 | pb_ | date: 2002/06/18 12:41:34; author: andyc; state: dead; lines: +0 -0 |
22:21.02 | dneuer | pb_: well, I decided to just go w/ -hh8, checked that out, trying to build that now |
22:21.24 | spung | pb_: you've got mail |
22:21.34 | pb_ | spung: aha |
22:21.39 | dneuer | pb_: having problems there, too (mwvlan module) |
22:22.02 | pb_ | spung: looks cool, I'll examine it properly in a bit. |
22:23.00 | pb_ | dneuer: never even heard of mwvlan. that's not a typo for wvlan, presumably? |
22:23.38 | *** join/#gpe dc__ (~dc@modem-165-43-60-62.vip.uk.com) |
22:24.32 | dneuer | pb_: judging from the comments at the top of the source, it's a newer version of the wvlan driver, or some variant on it. But it's enabled in the default config. Looks like its for Orinocco cards? |
22:26.54 | dneuer | I'm getting a million warnings during 'make modules' |
22:27.39 | spung | dc__: ping? |
22:28.26 | dneuer | methinks I will leave out mvlan |
22:28.32 | dneuer | mwvlan, that is |
22:29.22 | *** join/#gpe paul_ ([UqFHU5ynH@hibernia.jakma.org) |
22:33.03 | pb_ | dneuer: ah right. |
22:37.13 | *** join/#gpe david_ (~idleo@dsl-217-155-193-217.zen.co.uk) |
22:51.44 | dneuer | pb_ or jg: how does the CF + battery sleeve work: does the batter power the ipaq, or just the card? I think my problem earlier was that the iPAQ battery was out of charge, but the CF sleeve battery was full |
23:03.30 | pb_ | dneuer: I'm not all that familiar with the CF+ sleeve. On the pcmcia sleeve, the battery can power the card, and it can trickle charge the main battery, but it can't actually power the ipaq. |
23:04.40 | pb_ | I'd guess the CF+ sleeve is the same. From what I remember, there is no provision in the ipaq main unit for it to be powered directly from the sleeve battery. |
23:07.10 | dneuer | pb_: so the sleeve battery just helps prevent the card from draining the iPAQ battery faster? |
23:13.18 | spung | jg: ever heard of an X bug, when apps try to hide the pointer they get a pointer the size of a pixel instead? |
23:13.27 | *** join/#gpe walters (walters@216.226.142.129) |
23:14.23 | paul | pb_: hmm... libgpewidget isnt compiling: |
23:14.25 | paul | tap.c:31: parse error before `GdkDisplay' |
23:14.25 | paul | tap.c:31: warning: no semicolon at end of struct or union |
23:14.36 | jg | spung: no. |
23:15.02 | spung | jg: i get that occasionally on the ipaq, and on my desktop as I use x2x |
23:15.39 | PaxAnima | e00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000,, |
23:15.57 | spung | PaxAnima: what does your lib render now? |
23:15.57 | PaxAnima | the 0-key on my keypad got stuck, sorry |
23:16.03 | paul | very odd... tap.c looks fine. |
23:17.26 | PaxAnima | spung: "render" is wrong word, but it can create images from text.. or as I'll use: enables me to draw text in an image... |
23:17.50 | spung | :) |
23:18.20 | PaxAnima | spung: the image library is a bi-product of my diploma work... ;) |
23:19.18 | PaxAnima | spung: and it's getting pretty advanced... |
23:19.35 | spung | cool :) |
23:20.58 | PaxAnima | this is version 2 of the library (created the original for a project last spring semester).. the first one also had image capture from v4l devices and image preview... I'm thinking of adding that to version 2 as well.. |
23:21.49 | spung | jg: should i report that somewhere? X has no bugtracking system i think.. does it make sense to report it with the limited information I have |
23:21.52 | spung | ? |
23:24.56 | PaxAnima | spung: I'm thinking of use the library as basis for an image processing app one day... |
23:26.35 | spung | PaxAnima: I see it's your favourite project :) |
23:27.19 | PaxAnima | well, image processing _is_ fun... ;) |
23:28.10 | *** part/#gpe david_ (~idleo@dsl-217-155-193-217.zen.co.uk) |
23:30.26 | *** join/#gpe HET2 (~diman@chello080110105196.509.15.vie.surfer.at) |
23:32.08 | pb_ | paul: looks like your libgtk might be too old. |
23:32.17 | paul | pb_: hmm.. |
23:32.27 | pb_ | you need 2.2, not 2.0 |
23:32.30 | paul | drat |
23:32.42 | paul | pb_: 2.0.2 wont work? |
23:32.45 | pb_ | no |
23:32.55 | paul | bork |
23:35.01 | paul | hmm... looks like i'll need to nearly upgrade to 8.0 if i go with rpms. :( |
23:37.42 | *** join/#gpe dc___ (~dc@modem-84-62-60-62.vip.uk.com) |
23:49.01 | *** join/#gpe dc_ (~dc@modem-105-57-60-62.vip.uk.com) |
23:50.44 | paul | nope |
23:54.35 | pb_ | heh |
23:54.46 | pb_ | paul: it's not hard to compile gtk 2.2 from source |
23:54.59 | paul | pb_: yeah.. |
23:56.54 | paul | pb_: be quicker than upgrading to RH8 anyway. |
23:57.58 | paul | pb_: the makefiles do `pkg-config gtk-2.0` btw |
23:59.51 | PaxAnima | RH8 is _crap_ |