This update enables Kig Python 3 scripting support and updates Kig to the latest upstream release, version 19.08.3, which includes a few bug fixes, see: https://cgit.kde.org/kig.git/log/?h=Applications%2F19.08
It also fixes:
pykig
to actually work with Python 3,Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2019-cd4008c5ce
Please login to add feedback.
This update has been submitted for testing by kkofler.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
python script can now be created but kig crashes as soon as an object is moved in the kig window.
Details:
I created a Point, then asked for its x-coordinate, then created a python scripting with the numeric value of the x coordinate as an argument and the following script:
def calc( arg1 ): # Calculate whatever you want to show here, and return it. # For example, to return one half of the input number, # you would put this code here: # return DoubleObject( arg1.value()/ 2 ) # Please refer to the manual for more information.
Forgot to mention. The error showing up upon kig crash is:
$ kig org.kde.ksyntaxhighlighting: Rule: Unknown format "Normal" in context "Normal" of definition "Python-Kig" org.kde.ksyntaxhighlighting: Rule: Unknown format "Normal" in context "parenthesised" of definition "Python-Kig"
Do you have a backtrace for the crash? I don't think the warnings you see on the console are related.
kig: /usr/include/boost/python/object_core.hpp:422: boost::python::api::object_base::~object_base(): Assertion `Py_REFCNT(m_ptr) > 0' failed. Aborted (core dumped)
So I suspect that this is related to the same bug that I reported upstream as https://bugs.kde.org/show_bug.cgi?id=388241
Sorry this seems something that has to be fixed upstream as I get
I reopened your downstream report https://bugzilla.redhat.com/show_bug.cgi?id=1778000 but I cannot promise anything at this time.
Thanks... sorry, I mangled my comment above. The error appearing there comes from a kig compiled from source, I don't know how to help you. To get a backtrace I need help; is the problem present in fedora 32?
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
kkofler edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by kkofler.
Just tested and it seems working fine. Regarding the coordinate precision dialog: now the panel works fine; however the new value does not seem to affect the number of decimal digits printed. This is by sure an upstream issue and I will open a report there.
This update's test gating status has been changed to 'greenwave_failed'.
This update's test gating status has been changed to 'ignored'.
FEDORA-2019-cd4008c5ce ejected from the push because "Cannot find relevant tag for kig-19.08.3-3.fc31. None of ['f31-updates-testing', 'f31-updates-testing-pending'] are in ['dist-6E-epel-testing-candidate', 'epel7-testing-candidate', 'dist-5E-epel-testing-candidate', 'f27-modular-updates-candidate', 'f30-modular-updates-candidate', 'f30-container-updates-candidate', 'f30-flatpak-updates-candidate', 'f28-modular-updates-candidate', 'f28-container-updates-candidate', 'epel8-testing-candidate', 'f31-modular-updates-candidate', 'f32-container-updates-candidate', 'f31-container-updates-candidate', 'f31-flatpak-updates-candidate', 'f29-modular-updates-candidate', 'f29-container-updates-candidate', 'f29-flatpak-updates-candidate', 'f22-updates-candidate', 'f21-updates-candidate', 'f25-updates-candidate', 'f24-updates-candidate', 'f23-updates-candidate', 'f26-updates-candidate', 'f27-updates-candidate', 'f30-updates-candidate', 'f28-updates-candidate', 'f31-updates-candidate', 'f32-updates-candidate', 'f29-updates-candidate', 'el8-modular-updates-candidate']."
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
I still don't see an upstream report for that…
I am a bit confused... I still do not see the 'ok' button in the coordinate precision dialog when I compile from git sources. Moreover: actually a change in the coordinate precision WORKS! Only it works only on the "Coordinates" of a point when obtained right-clicking on a point -> Add Text Label -> Coordinate. This could actually make sense.
That's because the fix is only in the release/19.12 branch and was not merged to master yet.
I am sending this one to stable now, it is definitely an improvement over the status quo. I will be pushing a fix for #416037 to testing soon. If there are any fixes needed for coordinate precision, please point me to those so that I can apply those, too.
This update has been submitted for stable by kkofler.
This update has been pushed to stable.