"Edit with Office RibbonX" on the shortcut menu open previous version

[BerendStorm]

Describe the bug
A clear and concise description of what the bug is.
Previous to V1.9 I had V1.7 installed with the addition to the shortcut menu in Explorer.

I updated to V1.9 and used the shortcut as usual.
Oddly enhough this opens V1.7 instead of V1.9.

When I open the app directly it opens as V1.9. This is the expected behaviour.

I cannot find any way to uninstall V1.7 (no longer available in the apps list, nor in a directory I know of)
Nor can I find a way to re-assign the Explorer shortcut menu to V1.9 or to remove it from this menu.

Any suggestions?

Berend Storm

UPDATE:
I followed a hunge and checked the registry.
This was filled with references to "...\Program Files (x86)" instead of "...\Program Files".
Checked the "...\Program Files (x86)" directory. This still contained a version of RibbonX editor.
Deleted the complete directory and now manually modifying/clearing the registry.
Will post again if this is the solution.

UPDATE #2
This seems to work. The shortcut menu now opens V1.9

[fernandreu]

Hi @BerendStorm, sorry for the delay, but glad you managed to make it work in the meantime. There is a couple of things the app is doing wrong here.

First, there is no reason why a previous version should remain installed when installing another one. There was some changes in the installation system back then, so perhaps something got mixed up. Especially if there were installed in different x86/x64 folders; perhaps I made an incorrect assumption on the uninstall logic. I'll have a look.

Those "Edit with Office RibbonX" context menu entries are all set in the settings dialog, independently of the installation process. But then, the entries will appear with a checkbox on the settings dialog if any context menu entry is found in the registry. The app never checks whether the path associated to those registry entries points to the current app, or something entirely different. So, you might think the current app will open your files from the context menu by looking at the settings dialog, when in fact it doesn't. This is quite misleading, so I'll improve that.

[BerendStorm]

Hi Fernando, Thank you for your feedback. No problem with the late reply. I’m glad that I could provide you with enough details to improve this program further. Kind regards, Berend Storm ***@***.*** Telefoon:(050) 309 3568 LinkedIn: Berend Storm WEB: www.sjabloonspecialist.nl<http://www.sjabloonspecialist.nl/> Twitter: @SJABLOONSPECIAL Facebook: SJABLOONSPECIALIST YouTube: SJABLOONSPECIALIST TeamViewer hulp op afstand https://get.teamviewer.com/sjabloonspecialist Dit e-mailbericht is uitsluitend bedoeld voor de geadresseerde(n). Wilt u direct contact met ons opnemen als deze e-mail bij vergissing bij u terecht is gekomen? Wij verzoeken u in dat geval de e-mail te vernietigen, de inhoud ervan niet te gebruiken en niet onder derden te verspreiden, omdat het bericht vertrouwelijke informatie kan bevatten. Van: Fernando Andreu ***@***.***> Verzonden: vrijdag 20 mei 2022 00:39 Aan: fernandreu/office-ribbonx-editor ***@***.***> CC: Berend Storm ***@***.***>; Mention ***@***.***> Onderwerp: Re: [fernandreu/office-ribbonx-editor] "Edit with Office RibbonX" on the shortcut menu open previous version (Issue #207) Hi @BerendStorm<https://github.com/BerendStorm>, sorry for the delay, but glad you managed to make it work in the meantime. There is a couple of things the app is doing wrong here. First, there is no reason why a previous version should remain installed when installing another one. There was some changes in the installation system back then, so perhaps something got mixed up. Especially if there were installed in different x86/x64 folders; perhaps I made an incorrect assumption on the uninstall logic. I'll have a look. Those "Edit with Office RibbonX" context menu entries are all set in the settings dialog, independently of the installation process. But then, the entries will appear with a checkbox on the settings dialog if any context menu entry is found in the registry. The app never checks whether the path associated to those registry entries points to the current app, or something entirely different. So, you might think the current app will open your files from the context menu by looking at the settings dialog, when in fact it doesn't. This is quite misleading, so I'll improve that. — Reply to this email directly, view it on GitHub<#207 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUB4NE7ZHQMPN4QZMELGPCTVK27H7ANCNFSM5VFG4W5A>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#207 (comment)", "url": "#207 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]