Hello!
I keep receiving the following warning upon starting KNIME 4.7.6:
“Keybinding conflicts occurred. They may interfere with normal accelerator operation.” Along with
“A conflict occurred for CTRL++:”
We have a defect registered for a previous edition with this same error (AP-11438); I have linked your case to that defect and am inquiring internally about workarounds/resolutions for the issue (e.g. if deleting the workspace would resolve or not.) I will keep you posted as I receive more information about potential resolutions.
If possible, can you clarify any steps that you may have taken that preceded this occurring? Any upgrades or other extensions installations, etc? Anything that may help us develop repro steps may be helpful.
As always, unless there is some reason to stay on a specific older version, my first advice is usually to Update to Latest and see if that resolves the issue.
One other workaround you may look at is to go into the File>Preferences and change one of the keybindings, and see if this error message goes away.
I’d say it’s largely academic; depends on which, if any, you’re using currently and whether you find them intriguing to use now that you’re aware of their existence.
If you’re not using them and don’t plan to, then unbind away and restart AP.
After unbinding the “Zoom In / Ctrl ++” (When In Windows) the error disappears.
The other command (when Editing Text) is fine.
One thing is strange (at least for me): In my installation (meanwhile updated to 4.7.7) the Command “Zoom In / Ctrl ++” (When In Windows)" always come up twice.
So, changing the preferences as a workaround works for me.
I will report the situation after upgrading to 5.1
Hi @BPU , I would urge caution before simply upgrading to 5.1 from 4.7.x. It is a major change although incompatibilities are reducing over time.
I’d recommend doing a side by side installation and take a backup of your 4.x workspace first so you that you can revert if you have issues. 5.1 has some nice features but there is still a way to go and you may also find yourself using the classic UI a lot from 5.1 (I do) as there are still quite a lot of restrictions in the modern UI if you are a long-term “classic UI” user.
Thx for the recommendation. But this raises another question.
I use KNIME in the class room and assume that students will download 5.1 in October.
Or is there an option to still use / download 4.7xx?
Hi @BPU, if you are using it in the classroom environment, then I guess it depends on what you are teaching as to which version you would wish to use. I feel that training material for 4.7.x would need to be significantly updated for 5.1 if it were not to cause confusion, as the general look has changed (although using the classic ui would make this less of an issue), and some of the node names have changed, and even if using Classic UI, some of the node configurations have now moved to the “web ui” so it is something of a hybrid between old and new.
btw, I am not trying to dissuade you from moving to the new version, as there are some good new features and nodes there and it is the future(!) but there are still things that I find I cannot do without reverting to Classic UI and certainly to me it would sound like a big step assuming you have course material to be updated by October!
If you need to use AP installations of multiple versions, you can download the .zip files, unzip them into separate directories, and when you start them, point them at their own separate workspaces.
For example, I have Downloads/knime_4.7.6 and Downloads/knime_5.1.0 and they each have their own workspace.
This is useful for working on different versions, or even just for testing out the new version before making it your every day application.
I will try to install both versions parallel to check my options.
One more questions, regarding this scenario: When I want to transfer an old workflow from my 4.7 workspace to the new / addtional 5.1 workspace: Do I always need to export and import the workflow or is there a quicker way?
That’s probably safest. You could also just try copying the workflow folder from one workspace to another, but I haven’t verified myself that it works across versions 4 and 5.
Hello!
Just tested what happens with 5.1.
The errors are the same - unbinding works as a workaround again.
As long, as this causes no other issues, fine with me.
By the way: I had to switch to the old UI, to open the error log. Could find the log in the new look.