Re: GSeal bugs in GtkAccelLabel hampering flexibility
- From: Behdad Esfahbod <behdad behdad org>
- To: Peter Clifton <pcjc2 cam ac uk>
- Cc: gtk-devel-list gnome org
- Subject: Re: GSeal bugs in GtkAccelLabel hampering flexibility
- Date: Mon, 26 Jan 2009 16:34:27 -0500
Peter Clifton wrote:
>> If you want a workaround for now, just access the member as
>> GSEAL(member_name). I told them the GSEAL macro should use __line__, they
>> didn't listen :P.
>
> Ok - didn't know I could do that. I had presumed the sealed members we
> not available for prodding outside GTK's codebase.
It's a bad hack. I'm sure the GTK3 guys will find me and hunt me for letting
this out.
> (BTW.. what would __line__ do exactly?)
It expands to the line number. If the GSEAL macro used that to include the
line number in the mangled name you couldn't use this trick.
> If this lets me work around the problem, perhaps I can help prepare a
> more complete fix for GTK 3.0, whilst not being stuck in limbo waiting
> for users to move onto some as-yet unreleased GTK version. I'm not event
> sure whether all the fixes can even be made without breaking ABI. (GTK
> 3.0 will break ABI right?)
Correct. But the idea is to make transition as straightforward as possible.
> I presume accessing members with GSEAL(member_name) carries a big
> "Caveat Emptor", that you're now relying on implementation details.
Well, one is not supposed to use the GSEAL'ed members. But given your
situation, well, why not...
Cheers,
behdad
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]