remote form $construct method in design mode vs testing

[Martin Obongita]

 After furthers testing, I noticed that the $construct is being affected by a line of code in the $destruct

Do $cinst.$clientcommand("subformset_remove",row('SubformPanelsSet'))


Has anyone experienced issues with this code affecting the $construct? It could be an Omnis bug.



    On Sunday, September 8, 2024 at 11:52:31 PM GMT+3, Martin Obongita via omnisdev-en <omnisdev-en at lists.omnis-dev.com> wrote:  
 
 Hi everyone,
I'm experiencing a strange problem with the $construct of a remote form. I have created subform object in a secondary remote form. I have also created a primary form where I have buttons to select which subform to open in the secondary remote form. The $classname of the subform is assigned dynamically depending on the button clicked on the primary remote form. If I test the form for the first time, it runs okay and opens the subform. But fails a second test run. I therefore step through the code to catch where it is failing. The stack goes through the $event method of the button in the primary form, opens the secondary form but fails to step into the $construct of the secondary remote form. To assign the $classname property of the subform i run this code:
Do $cinst.$objs.SubFormHorzHeader.$classname.$assign(jsSFAddData)
Why would a stack step into a $construct of a js form in development mode but fail to call the same $construct on testing? Other remote forms work okay.
RegardsMartin.




_____________________________________________________________
Manage your list subscriptions at https://lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com