I have started to use Rio. Therefore I have installed new version of this component as well.
Now I get a problem, if I start context menu several times.
First time it works, but second time it shows a message, which in not related to context menu.
Than I have deinstalled this component and context menu works.
Please look at
[url]https://www.delphipraxis.net/1419904-post187.html[/url]
or
[url]https://en.delphipraxis.net/topic/314-g ... -available[/url]
Problem with Context menu
Problem with Context menu
Last edited by zeras on Sat May 11, 2019 8:24 am, edited 1 time in total.
Maybe this is a consequence of an error (maybe yours), when in Delphi 10.2.x your context menu item doubled ?
That is, in Delphi 10.2.x this error simply leads to a doubling of the context menu item, and in Delphi 10.3.x it causes more serious problems.
See the picture.

This error appears in version TsiLang 7.5.x. and Delphi 10.2.x
That is, in Delphi 10.2.x this error simply leads to a doubling of the context menu item, and in Delphi 10.3.x it causes more serious problems.
See the picture.

This error appears in version TsiLang 7.5.x. and Delphi 10.2.x
Hello,
Thank you for your message. Unfortunately, the duplicating of TsiLang Expert's menu items were caused by other problem which is fixed now, but this still doesn't affect problem with 10.3 editor's popup menu problem.
Actually, it looks like they (IDE's developers) implemented some new functionality that doesn't support custom/3rd party menu items (existing OpenTools API).
We're working on this and may be in next forthcoming version of RAD Studio this will be fixed. We're in touch with developers in respect of this problem.
Thank you for your message. Unfortunately, the duplicating of TsiLang Expert's menu items were caused by other problem which is fixed now, but this still doesn't affect problem with 10.3 editor's popup menu problem.
Actually, it looks like they (IDE's developers) implemented some new functionality that doesn't support custom/3rd party menu items (existing OpenTools API).
We're working on this and may be in next forthcoming version of RAD Studio this will be fixed. We're in touch with developers in respect of this problem.
Best regards,
Igor Siticov.
Igor Siticov.