On Wed, 2003-12-17 at 19:58, bulia byak wrote:
> With our discussions being so lively :) perhaps something gets lost. A=20
> couple of my recent questions were not answered, so I'm not reposting the=
> in the hope that they reach knowledgeable people who might have missed th=
> the first time.
I try to keep up with these things, but I have little time lately...
> 2. I want to enable ctrl-click to select within group, but I don't see ho=
> it can be done. I've delved deep into the arena code and found that if a=20
> group is "transparent" then its members can be selected one by one. But h=
> can I do that on ctrl-click? In select-context.c, the handler that checks=
> what button/key was pressed seems to already get a selected item as an=20
> argument from the arena code. Will I have to analyze this preselected ite=
> on my own, or is there a more elegant way?
This is something I'd like to work on personally, as part of the
continuing layers work. I'm still trying to determine what a "clean"
solution would be, though.
> 3. "Black magic": has anyone managed to reproduce this bug:
> and its "fix": add an empty g_print("") to line 204 of=20
> NRRectF *
> nr_rasterfont_generic_glyph_area_get (NRRasterFont *rf, unsigned int glyp=
> NRRectF *area)
> NRRFGlyphSlot *slot;
> glyph =3D CLAMP (glyph, 0, rf->nglyphs);
> slot =3D nr_rasterfont_ensure_glyph_slot (rf, glyph,=20
> NR_RASTERFONT_BBOX_FLAG | NR_RASTERFONT_GMAP_FLAG);
> If I don't hear from anyone I'm going to commit this fix anyway (with=20
> appropriate comments), because, at least, it will not break anything. A=20
> better solution would of course be welcome to replace that temporary fix.
This sounds like a compiler bug. What version of g++ are you using?=20
I've been unable to replicate the problem using g++ 3.3.2.