irclog2html for #gpe on 20030329

00:01.20pigeondoctor says i don't have pneumonia
00:01.31pb_pigeon: phew!
00:01.52pb_well, let's hope he's right.
00:01.54pigeonI had one in 1997, btw :\
00:02.05pb_:-/
00:44.37dc_pigeon: god yes...:}
00:45.01dc_pb_: so, mind if I start this clock thing?
00:45.11dc_pb_: only because it sounds like fun.
00:45.59pb_dc_: no, but...
00:46.13dc_...
00:46.24pb_you might like to take a look at http://handhelds.org/~pb/gpe-clock_0.0_arm.ipk first
00:50.30dc_ah cool
00:50.32dc_nice.
00:50.40dc_pb_: I mean more for gpe-conf time selection
00:51.03pb_dc_: absolutely, go for it.
00:51.14dc_we'll have to see how it turns out :}
00:51.50pb_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.47dc_quite. it'd be nice to have a full size clock be able to replace gpe-ownerinfo if wanted by the user.
00:52.58dc_at the login screen.
00:53.16pb_yes, that's a good idea also.
00:54.50pb_so, how do you plan to arrange things in gpe-conf?
00:55.00dc_the clock...?
00:55.03pb_yeah
00:55.17dc_well, have a button that pops up the clock.
00:55.20dc_to select a time.
00:55.42pb_right, sounds cool
00:55.55pb_I guess that avoids Florian's worry about space in the dialog
00:55.56dc_it could also be used in gpe-calendar if it works okay and is faster than the current method I guess.
00:56.01dc_pb_: indeed.
00:56.15pb_yes, that's a good idea.  I've always hated the way gpe-calendar selects times at the moment.
00:56.38pb_if you can make a popup-clock widget that can be used in many places, that would be great.
00:56.42dc_:}
00:56.58dc_then I can officialy claim position as popup and drawing area master!
00:57.10pb_exactly.
01:04.29*** join/#gpe jg (~jg@dialup-67.30.191.123.Dial.Boston1.Level3.net)
01:04.36pb_hi jg
01:04.49jgpb_: evening...
01:04.51jgpb_: how goes it?
01:05.05pb_jg: yeah, not bad, how's things with you?
01:05.19jgI only today caught up on my inbox for the first time in over a week....
01:05.33jgpb_: well over 1000 messages to deal with....
01:05.41pb_:-/
01:05.47jgpb_: you can guess the topics....
01:06.32pb_yeah, I think I can.
01:06.45mallumjg: 'Urgent Assistance' ?
01:06.57jgmallum: the XFree86 and X.org messes...
01:07.05mallumjg: 'Make Money FAST" ?
01:07.29mallumjg: x.org involved too now ?
01:08.04jgmallum: they managed to insert themselves into things, and had to be told similar messages....
01:08.17jgwhether they will listen is unclear.
01:09.04moraymallum: "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.13mallummoray: hehe
01:09.51mallumjg: it could be ( get?) worse, RMS could be involved ;-)
01:10.23jgmallum: yes, it could.  I had him to deal with a month ago, soaking amazing amounts of time....
01:10.26jgSigh...
01:10.39morayjg: 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.51jgI'd rather get to do some hacking than open source politics.
01:10.55morayindeed.
01:11.24jgmoray: a line got drawn in the sand.  Deadline for fundamental reform is next Thursday.  Only time will tell....
01:12.07mallumjg: I've been hacking a little gnome panel app frontend to xrandr :-)
01:12.11morayjg: ah right, was that the right thing to happen, or someone overdramatising?
01:12.44jgmoray: no, teleconference occurred yesterday: minutes and a copy of the audio shortly forthcoming....
01:12.45moraymallum: do you know if any of the 'normal' drivers have got round to xrandr support yet in 4.3?
01:13.14jgmoray: just size change.  I have to read to my son.  BBL.
01:13.14mallummoray: for resize I think most do, for rotation ( and reflection ) on tinyx
01:13.20mallums/on/only/
01:13.54moraymallum: hm, rotation would be nice for my rotatable TFT occasionally
01:14.09moraymallum: ha
01:14.15mallummoray: what card are you using ?
01:14.39moraymallum: it's a matrox g450 in this box IIRC
01:14.43mallum"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.11mallummoray: you could try an XVesa tinyx server on it
01:15.39dc_mallum: :S
01:15.41dc_mallum: :DD
01:15.42moraytrue, it's not as if I'm doing anything overly graphically intensive anyway...
01:15.44dc_mallum: how fun
01:15.44mallummoray: I have one I can put somewhere public for you if you want
01:15.55moraymallum: ah, might be worth a try
01:16.11mallummoray: I'll upload it tommorow as bedtime in a mo ..
01:16.22moraythanks.
01:16.47mallummoray: on the tablet, performance isn't much off the nv ( open ) driver on the tablet
01:16.54morayah right.
01:17.42mallumokey, Im repeating myself, bedtime I think :-)
01:17.46mallumg'night all
01:17.47moraygood night
01:17.50dc_night
01:30.05*** join/#gpe paul ([sotz7SZWm@hibernia.jakma.org)
01:37.35dc_hey paul
01:37.42paulheya damien
01:37.54pauldc_: up late?
01:37.57dc_paul: how'd the gpe-irc stuff go?
01:38.01dc_paul: yeah, weekend ;)
01:38.28pauldc_: i know why its crashing
01:38.36dc_coolio
01:38.53moraypaul: ah right - buffer overflow, or anything more exciting?
01:39.08paulmoray: dereference of null pointer
01:39.11morayok
01:40.21paulits trying to look up '#gpe ' in a hash-table - returns result, caller doesnt check for null.
01:40.42paulit should be looking up '#gpe'
01:41.06pauli havnt looked at anything gpe related during the week.
01:41.44paulhopefully will get that dillo web page done over the weekend, small gpe-login change phil wanted and, touch wood, gpe-irc :)
01:42.41paulmoray: anything exciting happening?
01:44.02moraypaul: hm, not especially - if I have time tomorrow I might put some startup notification support into keylaunch
01:44.10paulooh.
01:45.16paulsome 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.26paulsame icons, slightly bigger size.
01:47.01pb_paul: sounds like you have lost your gpe-confd database
01:47.08pb_xst write Gtk/ToolbarIconSize int 2
01:47.09paulah
01:47.14pb_(or int 1 if you want them even smaller)
01:48.03paulpb_: methinks i'm an interesting test case... i see problems others dont, because i always ipkg upgrade - i dont reflash.
01:48.20paul(is the impression i get anyway)
01:49.20morayspeaking of which, are there new images out yet?
01:51.48paulpb_: aha, that did the trick.
01:52.15*** join/#gpe dc__ (~dc@modem-58-55-60-62.vip.uk.com)
01:52.22pb_moray: no, no sign of pre7 yet.
01:52.31pb_paul: yeah, that could well be it.
01:59.25dc__sleep :\
02:04.30paulanyone else burning the late night oil?
02:09.53pb_yeah, but I've had about enough now.
02:09.59pb_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.04drknessanyone 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.53dc_morning :D
11:08.20dc_stargirl: up a bit early are we?
11:08.41stargirlhow'd you know I was awake?
11:08.53dc_;-P
11:09.08stargirlare you in cambridge outside my window?
11:09.16dc_oh damn!
11:09.56stargirl:-)
11:10.05stargirldid you hear that I got injured?
11:10.15dc_no :-\
11:10.31stargirlI was cycling and some woman opened her car door without looking
11:10.37stargirland I got viciously attacked by it
11:10.39dc_ouch!
11:10.41dc_:/
11:10.49stargirlfortunately, I totalled her car door ;-)
11:10.58dc_stargirl: what's the damage report then ;]?
11:11.01stargirlbut I am now in lots of pain from bruising and pulled muscles
11:11.09dc_:-{
11:11.16stargirland I have a silly graze on my chin
11:11.20stargirlwhich makes me look silly
11:11.27dc_oww.
11:11.43dc_better stay inside untill it heals then
11:12.13stargirlyes, else I might never live down thte embarassment
11:13.51stargirlI had to go to the hospital last night and everything
11:14.01dc_have to wait long?
11:14.10stargirlbecause I suddenly got worried that I'd broken bones, but it turns out that I hadn't
11:14.15stargirlnah, it was amazingly quiet
11:14.22stargirlthere was no one there apart from me and the doctors
11:14.26dc_thank god.
11:14.36stargirlyeah, well I made sure I went before the pubs closed
11:14.45stargirlso I wouldn't get all the drunk kids
11:14.46dc_I've had to wait 7 hours in a hospital for some little thing...
11:14.53dc_:}
11:14.54stargirlooh that's not fun
11:15.13dc_then I went in, they took one look and handed me some antibiotics..
11:15.21stargirlhehe
11:15.24dc_which took under 3 minutes....that was one boring night.
11:17.16stargirlhehe
11:18.17stargirlhmm all the tube lines in london today are b0rked
11:19.18dc_ack.
11:19.34dc_when I was getting back last week the thameslink was down.
11:19.42dc_and I had to do some funky tube trips.
11:34.17stargirlfun fun fun
11:35.01dc_hehe, you bot.
11:35.04dc_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.41PaxAnimahi, dc_
13:07.56*** join/#gpe dc__ (~dc@modem-251-62-60-62.vip.uk.com)
13:10.23PaxAnimahi, dc__
13:10.50dc__hey PaxAnima
13:10.57pb_dc__: yo
13:11.02dc__pb_: morning...
13:11.32dc__pb_: my clock got as far as a circle and a white background.
13:11.41dc__pb_: I wasted alot of time with gdk_draw_arc
13:11.55pb_dc__: ah, heh
13:12.11pb_dc__: did you look at the code for mine?
13:12.19dc__pb_: gdk seems to want it in 64ths of an angle
13:12.26pb_yeah
13:12.27dc__pb_: gkttimesel?
13:12.36pb_dc__: no, gpe-clock/da-clock.c
13:12.40dc__ah
13:12.43dc__let me see :)
13:13.44PaxAnimapb_: what's the good way of doing utf8, without using glib? any other libraries?
13:13.53pb_what are you trying to do?
13:14.24PaxAnimaplanning to look at libdictionary today, and use utf8 as internal representation
13:14.52pb_well, kind of the whole point about utf8 is that you don't need to "do" it in any serious way.
13:15.47PaxAnimahow?
13:16.42pb_for most things, the standard C string functions will just work.
13:18.42PaxAnimaaren't there functions for dealing with wide chars etc. I'd have to use? and what about indexing char*?
13:18.58PaxAnimae.g., mystring[3] = 'æ'
13:19.05dc__clock.c: In function `update_time':
13:19.05dc__clock.c:44: parse error before `const'
13:19.05dc__clock.c:48: `format' undeclared (first use in this function)
13:19.05dc__clock.c:48: (Each undeclared identifier is reported only once
13:19.05dc__clock.c:48: for each function it appears in.)
13:19.08dc__pb_:
13:19.21pb_dc__: oops
13:19.24pb_C99 strikes again
13:19.37dc__:}
13:19.38pb_dc__: move line 44 up a bit so it is before lines 42 and 43
13:19.47pb_or get a better compiler
13:22.38*** join/#gpe flypiper (~netwinder@12-222-141-210.client.insightBB.com)
13:26.55pb_dc__: I checked that change in, so the code in CVS now should build again.
13:49.47dc__pb_: um...okay...what should gpe-clock actualy do?
13:49.55dc__ah wait..
13:49.57dc__my bad...
13:49.59pb_dc__: it dock itself in the panel bar.
13:50.03dc__hrm
13:50.03pb_er, docks itself
13:50.06dc__damn this gnome2
13:50.14pb_You need to add a "notification area" to the panel under Gnome to make it work.
13:50.37pb_(add to panel -> utility -> notification area)
13:50.48dc__right.
13:51.27dc__pb_: ah great, that's just what I ment :)
13:51.47pb_:-)
13:52.06pb_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.11dc__I'll have a go at making it a wind up clock
13:52.27dc__pb_: yeah, aa would look very nice
13:52.51pb_Maybe we can persuade one of the X Men to help with that.
13:53.10dc__hrm
13:53.23dc__I'm not sure if wind up or grabbable hands is better
13:53.35pb_The grabbable hands seem to work quite well.
13:53.46dc__is it usable with a stylus?
13:53.51pb_Yeah, it seems to be.
13:53.57dc__great
13:54.04pb_I think there's an ipk in unstable now if you want to try it out.
13:54.11dc__ah cool!
13:54.19dc__pb_: you must have been up late last night ;)
13:54.47pb_dc__: heh
13:55.35dc__pb_: we can always put a nice png behind the hands for the background
13:55.42dc__instead of drawing it ourselves.
13:55.52pb_yup, good thinking
13:57.45pb_dc__: want to have a go at making a proper clock widget that we can put in libgpewidget?
13:58.25dc__sure thing
13:58.31pb_great
14:18.49pb_hm, I guess there needs to be an AM/PM radio button on the clock face as well.
14:19.20dc__ah yes!
14:20.14dc__yay. new we have a nice bacground
14:20.19pb_yay
14:20.19dc__s/new/now/
14:21.08dc__umm
14:21.35dc__ah..
14:22.27dc__pb_: what gc do I use when I want the color of the widget's default background?
14:22.55dc__n/m
14:25.32dc__pb_: any idea why it flickers?
14:25.48pb_I think because it's redrawing the whole clock every time.
14:26.11dc__I guess we should use expose->area then
14:26.13pb_It might be possible to make it smarter, by un-drawing the old hands and then drawing the new ones.
14:26.27dc__un-drawing?
14:27.08pb_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.24pb_if it was smart enough to just draw background over where the hand used to be, it would flicker less.  I think.
14:29.30pb_though, I'm not totally convinced that this is the cause of the problem anyway.
14:30.44dc__hrm
14:30.51pb_ah, hm, maybe I see the problem
14:30.55dc__what if we have pixmaps of the hands and rotate then?
14:30.55pb_let me check in a fix
14:31.27dc__okay, um, can you tell me the fix, because my current code is a bit different..
14:31.52pb_do "cvs diff -u -r1.4 -r1.5 da-clock.c"
14:31.55spungpb_: why does gpe-login continue to run after login? ps reports its VmSize is 11M
14:31.59dc__right
14:32.05pb_spung: autolock
14:32.38spungpb_: maybe it should drop the background to save mem?
14:32.49pb_I don't think it loads the background.
14:32.58pb_if it does, yes, that would be a bug.
14:33.17spungpb_: what do you mean?
14:33.35spungisn't gpe-login "transparent" ?
14:33.50pb_yeah
14:34.06spung14:34 <pb_> I don't think it loads the background.
14:34.14spungwell then?
14:34.50pb_well then, gpe-login doesn't actually load the background image, it just allows its parent window to show through.
14:35.11pb_it is also not transparent in autolock mode.
14:35.16spungpb_: i thought X didn't have real transparent?
14:35.34spungtransparency
14:35.53pb_it doesn't, but it has enough transparency for this purpose.
14:36.32spungpb_: i thought librootimage created a new pixmap?
14:37.29pb_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.05dc__pb_: that fix won't work with a pixbuf as the background
14:38.20pb_dc__: oh dear.  why not?
14:38.56pb_ah, I suppose you just don't have those arc calls any more.
14:39.00dc__pb_: because the border isn't drawen anymore.
14:39.02dc__pb_: yes
14:39.06pb_right
14:39.08spungpb_: just checked, yes, you do use librootimage :)
14:39.11dc__let me try and use event->ara
14:39.16dc__s/ara/area/
14:39.19pb_dc__: in that case I guess your flickering must have had a different cause to mine
14:39.35spungpb_: is it being free'd when you change to autolock mode?
14:40.18pb_spung: you don't ever change to autolock mode dynamically.  the mode is set when gpe-login is started, and never changed.
14:40.42pb_it follows a substantially different code path to normal operation.
14:41.18spungpb_: hmmm, I see. does gpe-login restart when you logout?
14:41.23pb_yes
14:41.41pb_it's launched from Xinit.d
14:42.01spungpb_: hmm, then it'd be easier to free librootimage's created pixmap after login no?
14:42.22pb_umm
14:42.37spungpb_: or maybe ps is tricking me?
14:43.04pb_well, unless you have a more advanced ps than me, it doesn't even claim to show you which pixmaps exist.
14:43.34pb_when you log in, gpe-login dies, and its pixmaps ought to go away as well.
14:43.43spungohhh
14:43.58pb_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.12spungpb_: yes, of course..
14:44.17pb_I guess the new XRes extension would allow us to find out though
14:44.30spungpb_: so, gpe-login dies and a new one (with --autolock) is started?
14:44.33pb_yes
14:44.51spungahh, makes no sense what I'm saying then :)
14:45.08pb_:-}
14:45.15spungjust sounded alarming it's VmSize that's all
14:45.22spungprobably doesn't mean anything
14:45.24pb_vmsize doesn't mean a whole lot.
14:45.28spungyeah
14:45.56pb_once you've got libc, libgtk, libx11, libxft and some fonts you are probably up to 9 or 10MB quite easily.
14:46.15spungahhh, I see
14:46.18pb_but, none of this is real RAM, so there is no point in worrying about it too much.
14:46.33spungthat explains why gpe-today has such a big size
14:46.37spungit links to tons of libs
14:46.41pb_you can check in /proc/pid/maps to see what is mapped.
14:49.11dc__pb_: why is there all this x_offset stuff?
14:49.37pb_dc__: to cope with the drawing area not being square
14:49.48dc__and why isn't it squre?
14:50.01pb_gtk can allocate it any size it wants.
14:50.15dc__heh
14:50.49pb_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.03dc__ahh, okay
14:51.21pb_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.54pb_if it winds up packed into a box with EXPAND set, it can get stretched out in one dimension or the other.
15:01.54spungpb_: gpe-calendar2 0.40 seems to have a messed up .desktop
15:02.06pb_oh dear
15:02.08pb_what's wrong with it?
15:02.34spungpb_: well, are you sure an old .destkop didn't get packaged by mistake?
15:02.45spungi remember make clean failing to remove old .desktop's
15:03.08pb_ah.
15:03.16pb_make clean certainly ought to remove the old ones.
15:03.42spungpb_: btw, ipkg installed all gpe-calendar-* translations, is that a known bug?
15:03.53pb_yeah, I think jamey broke it yesterday.
15:03.58spunglol
15:06.18spungpb_: can you try gpe-today out, don't you think that the dragging of the gtkpaned sucks?
15:06.54pb_yeah, I think I tried it before.
15:07.03spungah ok
15:07.22spungit seems that gtk is drawing twice
15:07.36pb_yeah.  did you have any luck asking the gtk folks about that?
15:07.42spungnot really
15:07.46pb_:-/
15:07.51spungi'll try again
15:07.53spung:)
15:08.01pb_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.30pb_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.04dc___oh no, gdk stole my mouse!
15:18.03pb_!
15:18.19pb_hate it when that happens.
15:18.26dc___yes..
15:18.38dc___something isn't right with my code ;)
15:18.44pb_heh
15:18.51pb_suspected as much
15:19.15dc___crashing on my gdk_rectangle_intersect....must be faulty rects.
15:19.26pb_yeah
15:25.04dc___pb_: mind if I commit the broken background code ;}?
15:26.00pb_dc___: sure, go for it.
15:26.06dc___:}
15:26.16pb_it'll make a change from looking at my broken atd code.
15:26.23dc___hehe
15:28.16dc___pb_: right...
15:28.37pb_dc___: so, what seems to be the problem?
15:28.54dc___pb_: compile and run
15:29.08dc___pb_: segfaults at gdk_rectangle_intersect.
15:29.12pb_ok
15:29.17pb_let me run it in Xnest to be safe :-}
15:29.24dc___ah eyah
15:29.26dc___do that too :)
15:29.31pb_ah, I see.
15:29.34pb_nice pixmap though :-)
15:29.42dc___yes...
15:30.31pb_ah, you are not coping with the NULL event you get from adjustment_value_changed ().
15:30.55dan_thello. any ipkg developper here ?
15:31.32pb_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.26dc___pb_: oh I see, for the spin buttons?
15:32.38pb_yeah
15:32.46pb_but that's also the mechanism for moving the hands when you drag.
15:32.58dc___damn...
15:34.11pb_well, let me see what I can come up with
15:35.44pb_dc___: what's the gdk_draw_rectangle (gray_gc) required for?
15:40.20cmarqupb_: Can you make the help tooltips match the color of the ones for the matchbox dock apps?
15:40.34pb_cmarqu: Yeah.
15:41.15*** join/#gpe dc___ (~dc@modem-154-59-60-62.vip.uk.com)
15:52.20pb_dc___: okay, I just checked in some changes.  try that and see if it's better.
15:57.48dc___pb_: much better :)
15:57.55pb_cool
15:59.40dc___now the only problem we have is our ugly hands
15:59.57pb_yeah
16:02.08dc___I have a really cool idea for the AM/PM display
16:02.18dc___that would just make people go 'awww'
16:02.20dc___but..
16:02.42dc___the clock hands need to be slightly transparent for it to work properly
16:02.51pb_well, we could manage that.
16:03.04dc___:)
16:03.21pb_if we can get Render working for the hands, it supports translucent drawing.
16:03.24dc___I'm thinking of having a little wheel in the center of the clock with a sun and moon on it.
16:03.28dc___pb_: ah cool
16:03.35pb_ah, ingenious.
16:03.41cmarquOh, then we could overlay the hands with ownerinfo too maybe?
16:03.55pb_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.06dc___then the bottom half of the wheel is shaded out, and it spins round with the time selected.
16:04.14pb_sounds good
16:04.25dc___plus it'll looks even better ;D
16:04.40pb_:-)
16:04.47*** join/#gpe mallum (~mallum@pc-80-193-218-21-hw.blueyonder.co.uk)
16:04.52dc___he mallum
16:05.29mallumhey dc__________________
16:05.35dc___hehe
16:06.49mallumdc___: whats new ?
16:07.10dc___mallum: gpe/base/gpe-clock
16:07.20dc___mallum: have a look at the 'Alarm...' menu item :)
16:07.41mallumdc___: what is it ?
16:08.10dc___mallum: a clock with draggable hands
16:08.15dc___mallum: to set the time for an alarm
16:08.26mallumdc___: oh cool
16:08.53mallumdc___: a mini analog dock app clock would be cool :-)
16:09.13dc___mallum: well, apart from the lack of space :\
16:09.28dc___mallum: I don't think 16x16 is enough for one
16:10.25mallumdc___: yeah, Im writing a whole new api for the panel apps
16:10.35mallumdc___: so they handle scaling etc
16:10.55mallumdc___: 16x16 apps are just too small on 640x480
16:11.12dc___mallum: ah, maybe when that's finished then :)
16:12.57dc___I find it really amusing that the new gnome2 stock icons look fine without aa.
16:13.10dc___set gnome 1.2 stock looked really bad without aa.
16:13.18dc___like they should be the other way round
16:13.35dc___BBrox: ;)
16:13.49dc___BBrox: wait till we have the sun and moon :D
16:17.24mallumdc___: how do you remove the AA from them ?
16:18.42dc___mallum: well, I was just saying, say the new icon in 1.2.
16:18.58dc___mallum: it's from a perspective, so it looks crap without aa.
16:19.15dc___mallum: whereas all the gnome2 icons are front on with not many curves.
16:20.41chrisimehey all
16:23.51dc___hello chrisime
16:24.39pb_hm, I need to get a better X server.
16:24.44dc___:}
16:24.47dc___don't we all pb_
16:25.00*** join/#gpe TheMasterMind1 (foobar@h-68-166-65-211.MCLNVA23.covad.net)
16:25.10pb_this poxy one on my desktop doesn't seem to do Render properly.
16:25.18dc___eek
16:25.21dc___that does suck
16:25.30pb_4.2.1 :-/
16:27.16mallumpb_: I've been running these 4.3 exp debs on the tablet and they seem ok
16:27.53pb_yeah, I guess that's what I should get.
16:31.29mallumpb_: arg, though it seems its missing all the xrandr headers :(
16:34.05mallumpb_: hmmm forget that
16:34.51spungmallum: have you considered making figment available in debian? i've fallen in love with this outliner thing :)
16:35.26mallumspung: :-)
16:36.08mallumspung: I think its a little broke at the mo ?
16:37.51spungmallum: is it?
16:37.59spungwhy?
16:38.09spungwhy can't I teleport it btw?
16:38.57mallumspung: I though gtk2.2 bust it a bit
16:39.41mallumspung: 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.28spungohh
16:41.39spungmallum: 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.11dc___yy
16:43.12dc___yay
16:43.20dc___behold the wheel of day and night
16:43.38pb_cool
16:43.50BBroxdc___: screenshot :-)
16:44.37dc___be patient ;]
16:44.43dc___pb_: now....my question.
16:44.57dc___pb_: how do we put a transparent box over half of it?
16:45.13pb_I guess I'd have to see the code first.
16:45.21dc___heh right...
16:45.36pb_:-)
16:51.37dc___awwwww
16:51.40dc___it looks so cute :D
16:51.43pb_heh
16:51.56mallumspung: why not grab it from CVS and hack on it a bit ;-)
16:52.33dc___pb_: it might make sense to color the hand blue or something aswell.
16:52.41pb_yep
16:53.54mallumdc___: is there a scap of it ?
16:54.02dc___not yet.
16:54.08dc___pb_: now we need some rotation code :\
16:55.18dc___pb_: checked into cvs btw.
16:55.25pb_great
16:56.10dc___pb_: do you have any ideas for the whereabouts of some rotation code with smoothing aswell?
16:56.43pb_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.58dc___yes
16:57.18pb_the problem I was having earlier turned out to be that it was interacting badly with Gdk's double buffering.
16:57.24dc___pb_: cool, so...yeah, what I plan to do is rotate the little wheel in the center
16:57.30dc___pb_: ah
16:58.13pb_ah yes, looks nice
17:01.41dc___hrm
17:01.56pb_well, I checked in a very rough cut of the render stuff.
17:02.11pb_it will be desperately flickery to start with; I need to put the double buffering back in to stop that.
17:02.12dc___pb_: if we can draw a transparent polygon there will be no need for any rotation code.
17:02.25dc___okay
17:02.42dc___um
17:02.44pb_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.53dc___./gpe-clock: relocation error: /opt/garnome-0.19.3/lib/libXft.so.2: undefined symbol: XRenderQuerySubpixelOrder
17:02.58dc___pb_: oh course :)
17:03.10dc___I ehh...hope that's not my xserver.
17:03.14pb_ah, hm, sucks.  seems your libxrender is out of date.
17:03.22dc___hum
17:03.40mallumpb_, dc___: in case you hadn't already noticed, xclock and xlogo have a lot of xrender code in them
17:03.58dc___doh
17:04.02pb_dc___: but this is most likely a bad path, as if your libxft2 was really broken no gnome program would work
17:06.36dc___pb_: any suggestions?
17:06.57pb_dc___: do "ldd ./gpe-clock", see where it is getting libXrender from.
17:07.05dc___just did...hrm
17:07.11pb_then compare that to some gnome program that works
17:07.42mallumdc___: do you have a /usr/X11R6/lib/libxft.so.2 ?
17:07.43dc___ah okay.
17:07.51dc___now....how do I stop it using the wrong one?
17:08.03pb_check $LD_LIBRARY_PATH, I guess
17:08.26pb_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.44dc__eek
17:09.46dc__well I changed a line in /etc/ld.so.conf
17:09.49dc__and it start now...
17:09.54pb_aha
17:09.56dc__but then I get:
17:10.04dc__Gdk-ERROR **: The program 'gpe-clock' received an X Window System error.
17:10.04dc__This probably reflects a bug in the program.
17:10.04dc__The error was 'BadImplementation (server does not implement operation)'.
17:10.04dc__<PROTECTED>
17:10.04dc__<PROTECTED>
17:10.05dc__<PROTECTED>
17:10.07dc__<PROTECTED>
17:10.09dc__<PROTECTED>
17:10.09pb_oh dear
17:10.11dc__<PROTECTED>
17:10.12pb_your X server sucks too
17:10.13dc__aborting...
17:10.15dc__flood :}
17:10.17pb_that's what mine does.
17:10.30dc__suck.
17:10.51pb_X 4.2.1 doesn't seem to support XRenderCompositeDoublePoly.
17:10.59dc__:(
17:11.00dc__suck
17:11.05pb_try running it with $DISPLAY pointing at the ipaq, that's what I had to do.
17:11.09dc__but my iPAQ should...
17:11.10dc__yeah
17:11.11dc__quite.
17:17.10dc__weird...
17:17.20dc__ssh gone from unstable.
17:17.29pb_oh, I think that's an ipkg bug.
17:17.34dc__yeah
17:17.35dc__I see...
17:17.41dc__it's in the package list
17:17.55pb_you might need to tweak ipkg.conf
17:18.18pb_or get latest ipkg if you haven't already.
17:18.32dc__ahha
17:19.01pigeon...
17:19.09pigeonCan someone tell me what's the time in Sydney now?
17:20.23dc__pigeon: apparently it's march 30th -3:16
17:20.29dc__03:16
17:20.39pigeonDamn it.
17:20.44pigeonDaylight saving.
17:20.51dc__heh
17:20.54pigeonI woke up an hour earlier.
17:21.08dc__pigeon: hehe
17:21.15pigeonAnd I need to go to the airport.
17:21.15pb_heh
17:21.34dc__pigeon: earlier....
17:21.43dc__pigeon: that can't be a bad thing can it?
17:21.57pigeonConsidering I was sick, maybe not :\
17:22.43dc__hrm
17:22.53dc__pb_: the iPAQ doesn't have enough space for the clock :\
17:23.06pb_dc__: yeah, I noticed.
17:23.07pigeonI hope the time of the flight is daylight saving adjusted as well. -.-
17:23.25pigeonI'm going back to bed.
17:23.25pb_dc__: but if the clock is going in a popup window, shouldn't be a problem
17:24.31dc__yeah
17:24.36dc__but man it looks cool.
17:24.49dc__pb_: eek, you've brung back my old problem
17:25.20pb_dc__: which one was that?
17:26.08pb_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.16dc__pb_: right, let me just show you this scap
17:27.23pb_ok
17:27.24dc__pb_: I'm going out in 15 minutes aswell
17:27.58dc__pb_: http://handhelds.org/scap/port.2510.png
17:28.16dc__mallum, BBrox: http://handhelds.org/scap/port.2510.png
17:28.24pb_dc__: scap looks nice.
17:28.36dc__pb_: even though it looks alright, the heavy border around the bottom of the clock isn't supposed to be there.
17:28.46dc__pb_: it's just supposed to be a light shadow.
17:29.26dc__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.31pb_dc__: okay, I'll look at that.
17:29.52pb_dc__: guess I shouldn't have removed that background-clearing line.
17:30.02dc__pb_: quite.
17:30.07pb_doh :-}
17:30.09spungdc__: you should make the pointer darker/wider
17:30.18dc__spung: yeah
17:30.27dc__pb_: step up the opacity a bit.
17:31.13pb_dc__: you can tweak it at line 282.  want to experiment and find a good number?
17:31.24dc__sure
17:32.03pb_we can also experiment with different shaped hands to see if we can find anything that looks a bit prettier.
17:32.17dc__pb_: um, 282 in which file?
17:32.35pb_dc__: da-clock.c
17:32.49pb_oh, I checked in some recent changes, you might need to update.
17:32.52pb_the line should read
17:32.54pb_<PROTECTED>
17:33.44dc__ah, bad emacs.
17:34.27pb_ah
17:35.55mallumdc__: oh, very nice
17:36.31mallumdc__: why not make the arms non transparent so clearer and mybe give them transparent shadows ?
17:40.40dc__mallum: that would look nice :}
17:41.08dc__all the opie people can drool over our clock now
17:41.18PaxAnimadc__: ;)
17:46.17dc__time to go...
17:46.18dc__bbl
18:04.03spungpb_: 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.30spungahh, maybe duration = 0
18:24.16*** join/#gpe dc__ (~dc@modem-200-48-60-62.vip.uk.com)
18:30.21BBroxdc__: well, it's nice.. But it's kinda confusing :-)
18:30.26pb_spung: I think a reminder is just an event with no duration.
18:30.50pb_BBrox: hm, confusing in what way?
18:31.25BBroxpb_: well, the sun up means AM or PM :-) ?
18:31.58pb_ah, yeah, I can see that bit would be confusing.
18:32.03pb_I wonder what to do about it.
18:32.05spungBBrox: good point :)
18:32.24BBroxAs AM is half day, half night and the same for PM :-)
18:32.27pb_it would certainly make no sense to have the sun up at 1am.
18:32.58BBroxIt certainly looks nice though
18:33.09spungpb_: except if you're your in the north pole in that time of the year :)
18:33.56pb_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.09pb_ie 3 o'clock, sun up = 3pm, sun down = 3am
18:34.19pb_7 o'clock, sun up = 7am, sun down = 7pm
18:34.21pb_etc
18:35.15pb_well, that's probably something for dc to worry about.
18:35.22pb_I will fix the drawing code though. :-]
18:35.34BBroxWell, I would see the 'Sun / Moon' stuff rotating also..
18:35.48BBroxIe showing the hour at a 24 hour format instead of 12 hours like the dial
18:36.27BBroxOr 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.52pb_Yeah.  I'm not sure which Damien planned to do.
18:37.22BBroxBTW, played the other day with Motorola's Linux phone
18:37.34BBroxNeed to put X and GPE on it :-)
18:37.40pb_heh, cool
18:38.02BBroxIt's really a nice looking phone...
18:41.12pigeonHey bbrox
18:42.44BBrox'lo pigeon
18:49.49*** join/#gpe chrisime_ (~chrisime@p5080269F.dip0.t-ipconnect.de)
18:57.10mallumspung: btw, figment is in garnome
19:15.47spungpb_: 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.02spungi'm refering to choice of name, of course
19:16.03spung:\
19:16.25pb_spung: best write some docs then
19:16.46spungpb_: what i mean, is I thought it was a gtk function and couldn't find the docs
19:17.02pb_yes, I know what you meant.
19:17.31spungpb_: why not gpe_simple_menu_new() ?
19:17.51pb_no particular reason.
19:18.02spung:\
19:20.00*** join/#gpe dneuer (~smoothie@192.204.192.36)
19:20.07spunganyway, 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.57pb_yeah, it derives from GtkOptionMenu, so those functions should work.
19:21.15spungahh
19:21.23spungcool
19:31.29spungpb_: is gpe-calendar's week_view broken or something?
19:31.38pb_dunno.  what seems to be the problem?
19:31.48spungdoes it require a super up-to-date gtk?
19:31.55pb_dunno
19:32.01spungweek_view.c: In function `draw_expose_event':
19:32.01spungweek_view.c:140: parse error before `*'
19:32.01spungweek_view.c:142: `buffer' undeclared (first use in this function)
19:32.09spungplus a couple of other comile errors
19:32.22pb_oh, that
19:32.26pb_mccarthy had that problem too.
19:32.31pb_you need a newer compiler.
19:32.37spunghmm
19:32.39pb_I'll fix the code.
19:33.56pb_okay, I fixed that one.
19:34.23spungpb_: what's wrong with that code? i don't see anything too weird?
19:34.36spungahhhhh
19:34.37spungnevermind
19:34.44spungC99 stuff
19:34.44spung:)
19:34.51spungthat's evil!!
19:35.09spungdeclaring a var there, that's soooo evil :)
19:35.40dneuerhey all
19:36.02dneuerwhat format are .ipk files in? I thought they were tar.gz's
19:38.55spungdneuer: that's the old format
19:39.20dneuerwhat's the new format?
19:39.24spungdneuer: good question :)
19:39.44spungjust a sec
19:39.45dneuerwell that's a little irritating
19:40.02pb_dneuer: they're ar now, same as .deb.
19:40.12spungdneuer: there you go
19:40.37dneuerar? How do you un-ar something?
19:40.43pb_with ar
19:40.53pb_ar x package.ipk
19:41.03pb_or use dpkg-deb or ipkg-unbuild
19:41.31dneueripkg-unbuild is a script?
19:41.35pb_yep
19:41.35dneueror a binary?
19:41.40dneuerok
19:41.43pb_script.  it's in ipkg-utils cvas
19:41.46pb_cvs
19:43.37dneuerpb_: I assume ipkg-unbuild depends on ar? I dont' have ar on my system
19:43.50pb_dneuer: yeah, probably.  ar is part of binutils, so most people would have it.
19:44.39dneuerok, I do have it, there's just no manpage
19:44.46pb_ah.
19:48.27dneuerpb_: 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.48dneuerno version #s. But there are packages in unstable w/ very weird version #s
19:49.11dneuerlie bluez-utils_2.2-khh2_arm.ipk
19:49.14dneuerlike
19:49.29pb_right
19:49.40dneueror, alternatively, bluez-utils_2.2_kc1_arm.ipk
19:49.51dneueror bluez-utils_2.2-hh2_arm.ipk
19:50.03dneuerwhich is the one that would get installed?
19:50.22dneueror *should* get installed, which is really what I care about
19:50.31pb_not sure.  I'm guessing the latter.  The first one has a malformed version number.
19:51.49dneueranother question: is the kernel which is part of familar .7pre6 known to be completely screwed?
19:52.55pb_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.35dneuerpb_: why, is he putting hh8 in?
19:53.40pb_yeah
19:53.51dneuerok
19:54.04pb_the images are usually built from the latest packages at that time.
19:54.37dneuerI'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.00pb_strange
19:55.05dneuerI agree
19:55.07pb_I've never seen that.
19:55.13pb_what model of ipaq is that on?
19:56.42dneuerpb_: 3650, souped up (extra RAM)
19:57.39pb_did you try hh8?
19:58.39dneuerpb_: not yet. I was going to build cvs today and try that instead
19:59.18dneuerI find it's still easier to forget about ipkg for kernel stuff and just zmodem a kernel and modules tar'd up
19:59.29pb_right
20:00.53dneuerI'm on an obsessive mission to get my Belkin BT card working
20:02.59dneuerdoes MonMotha not have hh commit privs?
20:03.29pb_not sure
20:03.49dneuerI 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.53pb_no, he doesn't.
20:04.01dneuerI can change it, and commit it
20:04.12pb_ok, cool, go for it.
20:04.23pb_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.27dneuerh3600 is the right one, correct?
20:04.32pb_yeah
20:04.37pb_be worth changing h3900 also
20:04.47dneuerok, can do
20:12.18spungpb_: let me know when you're back :)
20:14.05spungdneuer: 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.53PaxAnimayay! my image library can now render (ugly, fixed font) text!...
20:34.11spungyay
20:34.17PaxAnimahttp://v058b.studby.ntnu.no/images/test_font.png
20:35.13spungPaxAnima: I can confirm that it is text
20:35.22PaxAnimaspung: good ;)
20:35.30spunglol :)
20:37.32PaxAnimagood to know it wasn't the coffee that gave me halucinations...
20:37.59spungpb_: ahh, prepare to be flooded
20:38.33spungpb_: after i do a gtk_option_menu_set_history() on a gtk_simple_menu
20:38.56spungpb_: gtk_simple_menu_get_result() and gtk_option_menu_get_history() return different values
20:39.06pb_ah, hm.
20:39.24pb_yeah, we should just make gtk_simple_menu_get_result call gtk_option_menu_get_history.
20:40.21spungpb_: that's a barrier to my fix of the day :\
20:41.41spungpb_: so, we should get rid of guint item in _GtkSimpleMenu
20:42.12spungpb_: and change every instance of sm->item = 0; to gtk_option_menu_set_history() ?
20:43.28pb_well, try the change I just checked in.
20:43.39spungcool
20:45.29dneuerpb_: you understand the IRQ stuff?
20:45.37pb_dneuer: mostly, I guess
20:46.40dneuerpb_: andyc broke the compile yesterday. Specifically, IRQ_H3800_MMC in h600.c is not declared in irqs.h
20:46.56pb_ah, ok, lemme look
20:47.08pb_this is h3600 compile, right?
20:47.23dneuerpb_: I can see where he moved it from, but it was called something else, and it was defined as IRQ_GPIO18
20:47.28dneueryeah
20:48.30pb_well, I guess it should just be defined in irqs.h with all its friends.
20:48.42dneuerpb_: 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.54dneuertaken
20:49.11pb_hm, actually I have EAR_IN at board_start + 11
20:49.21dneueroops, right, just caught that
20:49.37dneuerwhich means nothing to me
20:49.50dneuerI know nothing about the 3800's
20:50.42pb_I think you should just be able to #define IRQ_H3800_MMC IRQ_GPIO18
20:51.20pb_or use IRQ_GPIO_H3800_MMC_INT, defined in h3600_asic.h
20:52.24dneuerpb_: well, sure, but that doesn't fit the scheme in irqs.h for board-specific irqs
20:52.37pb_I don't think it's board-specific in that sense.
20:52.59pb_The "board specific" irqs are ones that are generated by the ASIC and need to be specially demuxed.
20:53.36pb_It sounds like the MMC interrupt arrives directly at a gpio pin on the sa-1110, so no further indirection is required.
20:54.37dneuerhmmm
20:55.00dneuerit was moved from h3600_asic.c
20:55.01pb_this is why the board-specific ones are arranged in two groups, for the GPIO and KPIO blocks in the rosella chip.
20:55.15dneuerrosella chip? is that the asic?
20:55.25pb_yeah, "asic2"
20:55.53pb_there's also an "asic1" in h3800, or "asic3" in h3900.
20:57.09pb_when you say h3600_asic.c, which file do you mean?  h3600_asic.c itself has been dead for months.
20:57.51pb_dinner time, bbl
20:58.13dneuerreally? 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.21dneuerhi jg
22:09.36jgdneuer: hi
22:10.28dneuerjg: what's mwvlan?
22:11.14jgdneuer: dunno....
22:20.21pb_dneuer: check "cvs log h3600_asic.c"
22:20.25pb_revision 1.29
22:20.28pb_date: 2002/06/18 12:41:34;  author: andyc;  state: dead;  lines: +0 -0
22:21.02dneuerpb_: well, I decided to just go w/ -hh8, checked that out, trying to build that now
22:21.24spungpb_: you've got mail
22:21.34pb_spung: aha
22:21.39dneuerpb_: having problems there, too (mwvlan module)
22:22.02pb_spung: looks cool, I'll examine it properly in a bit.
22:23.00pb_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.32dneuerpb_: 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.54dneuerI'm getting a million warnings during 'make modules'
22:27.39spungdc__: ping?
22:28.26dneuermethinks I will leave out mvlan
22:28.32dneuermwvlan, that is
22:29.22*** join/#gpe paul_ ([UqFHU5ynH@hibernia.jakma.org)
22:33.03pb_dneuer: ah right.
22:37.13*** join/#gpe david_ (~idleo@dsl-217-155-193-217.zen.co.uk)
22:51.44dneuerpb_ 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.30pb_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.40pb_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.10dneuerpb_: so the sleeve battery just helps prevent the card from draining the iPAQ battery faster?
23:13.18spungjg: 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.23paulpb_: hmm... libgpewidget isnt compiling:
23:14.25paultap.c:31: parse error before `GdkDisplay'
23:14.25paultap.c:31: warning: no semicolon at end of struct or union
23:14.36jgspung: no.
23:15.02spungjg: i get that occasionally on the ipaq, and on my desktop as I use x2x
23:15.39PaxAnimae00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000,,
23:15.57spungPaxAnima: what does your lib render now?
23:15.57PaxAnimathe 0-key on my keypad got stuck, sorry
23:16.03paulvery odd... tap.c looks fine.
23:17.26PaxAnimaspung: "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.50spung:)
23:18.20PaxAnimaspung: the image library is a bi-product of my diploma work... ;)
23:19.18PaxAnimaspung: and it's getting pretty advanced...
23:19.35spungcool :)
23:20.58PaxAnimathis 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.49spungjg: 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.52spung?
23:24.56PaxAnimaspung: I'm thinking of use the library as basis for an image processing app one day...
23:26.35spungPaxAnima: I see it's your favourite project :)
23:27.19PaxAnimawell, 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.08pb_paul: looks like your libgtk might be too old.
23:32.17paulpb_: hmm..
23:32.27pb_you need 2.2, not 2.0
23:32.30pauldrat
23:32.42paulpb_: 2.0.2 wont work?
23:32.45pb_no
23:32.55paulbork
23:35.01paulhmm... 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.44paulnope
23:54.35pb_heh
23:54.46pb_paul: it's not hard to compile gtk 2.2 from source
23:54.59paulpb_: yeah..
23:56.54paulpb_: be quicker than upgrading to RH8 anyway.
23:57.58paulpb_: the makefiles do `pkg-config gtk-2.0` btw
23:59.51PaxAnimaRH8 is _crap_

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.