diff options
| author | Anderson Lizardo <anderson.lizardo@openbossa.org> | 2010-03-29 14:24:27 -0400 |
|---|---|---|
| committer | Anderson Lizardo <anderson.lizardo@openbossa.org> | 2010-03-31 14:33:21 -0400 |
| commit | 96e7b2db77552e1b322427125a9044381f778182 (patch) | |
| tree | 56b6a849e5ae2bbea55009ee7687726b24fa43e0 /PySide/QtCore | |
| parent | bf8b1e7d38dd849a6cd22005fcfb0668007915f3 (diff) | |
QEasingCurve::setCustomType typesystem workaround
Due to bug #201, typesystem signatures that take pointer to function
types are incorrectly expanded.
To workaround this bug, the typesystem signature for
QEasingCurve::setCustomType removal is:
<modify-function signature="setCustomType(double)" remove="all"/>
But for ARM, this same workaround does not work, and has to be:
<modify-function signature="setCustomType(float)" remove="all"/>
This is probably due to how apiextractor/shiboken is incorrectly
expanding the pointer to function signature. To remove setCustomType on
ARM (and thus allow the build to succeed), this commit adds both
signatures.
This is a temporary fix just while bug #201 is not fixed.
Reviewed-by: Lauro Moura <lauro.neto@openbossa.org>
Reviewed-by: Bruno Araujo <bruno.araujo@openbossa.org>
Diffstat (limited to 'PySide/QtCore')
| -rw-r--r-- | PySide/QtCore/typesystem_core.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/PySide/QtCore/typesystem_core.xml b/PySide/QtCore/typesystem_core.xml index 67d48f79f..1f50621cd 100644 --- a/PySide/QtCore/typesystem_core.xml +++ b/PySide/QtCore/typesystem_core.xml @@ -2836,6 +2836,10 @@ <value-type name="QEasingCurve"> <modify-function signature="customType() const" remove="all"/> + <!-- FIXME: setCustomType() actually takes a pointer to function type + (EasingFunction), but for some reason apiextractor thinks it is a float/double: + http://bugs.openbossa.org/show_bug.cgi?id=201 --> + <modify-function signature="setCustomType(float)" remove="all"/> <modify-function signature="setCustomType(double)" remove="all"/> </value-type> |