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 652596 - atspi_value_set_current_value does not work
atspi_value_set_current_value does not work
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Li Yuan
Depends on:
Blocks:
 
 
Reported: 2011-06-14 20:42 UTC by José Millán Soto
Modified: 2011-06-22 16:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description José Millán Soto 2011-06-14 20:42:24 UTC 
atspi_value_set_current_value calls the method SetCurrentValue instead of writing the "CurrentValue" property.
As a result, it does set the current value.
Comment 1 Mike Gorse 2011-06-14 22:44:55 UTC 
I assume you're using QT-AT-SPI.  The original code was intended to set the property, and Mario reported that it did not work and gave me a patch that made it call SetCurrentValue and added a SetCurrentValue method to at-spi2-atk.  I applied it since it was something like two hours before code freeze went into effect and I didn't have time to investigate the underlying issue.  Anyway, now would be an okay time to revisit it since we're in a new cycle, and I think the right fix would be to do as you described and have it set the property, ensuring that it also works with at-spi2-atk.
Comment 2 José Millán Soto 2011-06-15 11:17:52 UTC 
Yes, I was using qt-at-spi.
I added a method called SetCurrentValue to the Value adaptor, so it works while the property is not being set.
Comment 3 Mike Gorse 2011-06-22 16:45:50 UTC 
I've just re-added the property setter in at-spi2-atk and modified at-spi2-core to use the DBus property rather than the SetCurrentValue method.

I've left the SetCurrentValue method in at-spi2-atk for backwards compatibility; it might eventually make sense to remove it, since it is basically redundant.