After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 441343 - AtkValue needs manual proxy methods
AtkValue needs manual proxy methods
Status: RESOLVED OBSOLETE
Product: pygtk
Classification: Bindings
Component: atk
Git Master
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks: atk-proxy
 
 
Reported: 2007-05-26 02:35 UTC by Peter Parente
Modified: 2013-08-26 13:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
manual proxies for all AtkValue methods (8.19 KB, patch)
2007-05-26 02:40 UTC, Peter Parente
reviewed Details | Review

Description Peter Parente 2007-05-26 02:35:45 UTC
The AtkValue interface needs manual proxy overrides to account for the outbound GValue parameters and the fact that AT-SPI only supports doubles in this field anyways.
Comment 1 Peter Parente 2007-05-26 02:40:33 UTC
Created attachment 88831 [details] [review]
manual proxies for all AtkValue methods
Comment 2 Gustavo Carneiro 2007-05-26 11:38:42 UTC
Looks good but PyGtk hasn't branched yet.
Comment 3 Peter Parente 2007-05-26 11:52:06 UTC
Thanks. Again, this patch can wait. I didn't know that svn was frozen.
Comment 4 Johan (not receiving bugmail) Dahlin 2007-05-26 16:11:06 UTC
Feel free to branch of 2.10.x and commit your changes to trunk.
Comment 5 Peter Parente 2007-05-27 00:33:19 UTC
I'm assuming you were talking to Gustavo, not me, the non-pygtk devel, right? :)
Comment 6 Johan (not receiving bugmail) Dahlin 2007-05-28 13:42:58 UTC
(In reply to comment #5)
> I'm assuming you were talking to Gustavo, not me, the non-pygtk devel, right?
> :)
> 

No, both of you. If you have a gnome svn account know how to branch, I don't see why you couldn't do it.
Comment 7 Peter Parente 2007-05-28 20:30:30 UTC
Oh. OK. Then let me make sure I understand what you're saying. 

> Feel free to branch of 2.10.x and commit your changes to trunk.

You want me to create a 2.10 branch, then apply these patches to trunk? Or do you want me to branch from trunk or another existing branch, work in that new branch, and then merge into trunk when done?
Comment 8 Johan (not receiving bugmail) Dahlin 2007-05-28 20:33:50 UTC
(In reply to comment #7)
> Oh. OK. Then let me make sure I understand what you're saying. 
> 
> > Feel free to branch of 2.10.x and commit your changes to trunk.
> 
> You want me to create a 2.10 branch, then apply these patches to trunk? Or do
> you want me to branch from trunk or another existing branch, work in that new
> branch, and then merge into trunk when done?
> 

You can't API to 2.10, which is the current trunk.
So you need to create a new branch which is API compatible in case we want to do another 2.10.x release. Once that is done you can commit your changes to trunk which will be used to release 2.12.x.
Comment 9 Peter Parente 2007-05-31 12:08:54 UTC
What's the preferred naming scheme? pygtk-2-10? Or something specific to the work I'm doing like pygtk-atk?
Comment 10 Johan (not receiving bugmail) Dahlin 2007-05-31 12:19:16 UTC
Since it's for 2.10 and by looking at http://svn.gnome.org/viewcvs/pygtk/branches/, pygtk-2-10.
Comment 11 Gustavo Carneiro 2007-05-31 12:26:56 UTC
I'm tired of silly question:

gjc@nazgul:pygtk$ svn cp -m "branch for 2.10" svn+ssh://gjc@svn.gnome.org/svn/pygtk/trunk svn+ssh://gjc@svn.gnome.org/svn/pygtk/branches/pygtk-2-10

Committed revision 2823.

Now go commit your stuff to trunk :)
Comment 12 Alejandro Piñeiro Iglesias (IRC: infapi00) 2013-08-26 13:08:28 UTC
Closing this bug as obsolete.

In the same way, the patch is wrong as is wrapping AtkValue, but receiving an AtkComponent as *self.