Tagged: EurOmnis Javascript Controls
This topic contains 1 reply, has 1 voice, and was last updated by Michael Monschau 2 years, 4 months ago.
-
AuthorPosts
-
November 27, 2018 at 12:26 pm #17804
Hi $all,
I am using the Omnis list in the hope that I will at least reach some of you who attended this session. I will also post this message on the Omnis Developer Portal.
In this years Writing JS-Controls session, we encountered some problems with event handling when using the Studio JSON Control Editor. Unfortunately, I was not able to resolve it to a satisfactory end during the session, although I hope that I still have provided everyone with sufficient insight into what’s required. After having communicated with Omnis, I have narrowed down the problem. It appears that custom event constants are correctly encoded in the javascript when used within the $event method, i.e. custom event constants as strings and build-in event constants as integers. But when used in other methods, i.e. the class methods of the remote form, executed on the client, the javascript that is produced does not encode the custom event constants correctly, i.e. custom event constants where encoded as integer value zero. As far as I am aware this applies to Studio 9 beta as well as Studio 8.1.6 and previous versions of Studio.
This issues has been reported (Reference: ST/EM/214). In the meantime, the work-around is to specify the names of the custom events as strings within case statements, if the code is external to the $event method of the control.
I will upload the new example library (which I will modify with the work-around), JSON definition and javascript, to Github, as soon as I have a spare moment.
My apologies again for the issues that we encountered and the time that was wasted. This was entirely my fault as I should have tested the examples more thoroughly prior to the session.
I still have to further investigate the issue whether to specify or not to specify a ‘p’ within event parameters versus method parameters, before reporting any inconsistencies I may find. The ‘pp’ problem was the funniest mishap of any session I have given to date 🙂
Regards,
MichaelMichael Monschau (Director)
Brainy Data LimitedReply To: michael@brainydata.co.uk
Phone: +44 (0)870 474 0708
Web: http://www.brainydata.com the home of Omnis Components and Developer ServicesNovember 27, 2018 at 1:12 pm #17805Sorry the first line should have said…
I am using the Omnis Developer Portal in the hope that I will at least reach some of you who attended this session. I have also posted this message on the Omnis List.
-
AuthorPosts
You must be logged in to reply to this topic.