[Andreas Pfeiffer]

Hi Martin,

There is no difference in the instance if the code is in the inherited form or in its superclass. The instance is the same.

Maybe I understand this wrongly. What exactly do you get back when you debug the code and look at the item reference variable?

Best,

Andreas

[Andreas Pfeiffer]

Awesome! Glad to help.

Best,

Andreas

[Andreas Pfeiffer]

Hello Khanh,

You cannot use the Queue commands as those would simply try to do this on the server. But the users cursor is on the client. Instead try this command:

Do $cinst.$setcurfield(fieldRef)

You can pass in the name of the field, the reference or the id. You can also pass in a 2nd parameter if you want to make the content selected.

Hope this helps.

Best,

Andreas

[Andreas Pfeiffer]

If you want to use Omnis Studio 11 please do not replace the HTM file as described in the readme.txt file.

Best,

Andreas

[Andreas Pfeiffer]

Hallo Herr Köhler,

Ist das ein doppel Post?

Mit freundlichen Grüßen

Andreas

[Andreas Pfeiffer]

Awesome. Great.

Best,

Andreas

[Andreas Pfeiffer]

Hi Martin,

$cando() is an inbuilt method that proves if a certain method is available. In this specific case it checks if the $getID() of the container can be executed.

The container can be either the container form that contains the subform instance or it can be the form that opened the popup form.

So the $load will be called with an argument that is the id from the container.

I hope that makes sense.

Best,

Andreas

[Andreas Pfeiffer]

Hi Khanh,

Check out Client Preferences: https://www.omnis.net/developers/resources/onlinedocs/WebDev/02jsremoteforms.html#client-preferences

Best,

Andreas

• This reply was modified 2 years, 2 months ago by  Andreas Pfeiffer.
• This reply was modified 2 years, 2 months ago by  Andreas Pfeiffer.

[Andreas Pfeiffer]

Hi Khanh,

Again not really recommendable. However under certain circumstances it might be necessary and it is possible.

For example you can have the following code behind a button. When the button is clicked it will generate a copy of the button:

On evClick
    Do $cinst.$objs.$add('newButton',$cfield) Returns lNewButtonRef
        If lNewButtonRef
            Do lNewButtonRef.$top.$assign(30)
            Do lNewButtonRef.$left.$assign(250)
            Do lNewButtonRef.$text.$assign('I am new')
    End If

Note that $cfield is the reference to the field where this code is actually located. In this case it is the button you have clicked on. You can also refer to another object by using this notation:

$cinst.$objs.myOtherField

“lNewButtonRef” is a local variable of type item reference. This is a pointer to the new field and can be checked with the IF statement. It can also be used to assign other properties such as $top, $left, $text etc.

So in theory you could dynamically create your UI but then you will lose the advantage of having a graphical design tool etc. This is one of the strength of Omnis development.

So why not simply drag the desired object from the component store onto the form?

Best,

Andreas

• This reply was modified 2 years, 2 months ago by  Andreas Pfeiffer.

[Andreas Pfeiffer]

Hi Khanh,

with this technique you can copy objects in a remote form.

However the question is if this is a good approach. Designing the remote form by adding objects dynamically will be slow and is not using the remote form class as it has been designed. The class is a kind of a database record that is holding its fields. The whole library is the database that holds the UI and the functions.

If you still need an example how to copy objects in a remote form let me know. I will send some code how to achieve this. I am just afraid that Omnis is then kind of misused by storing the field information somewhere else. I have seen this in other projects which makes things unnecessary complex.

Best,

Andreas

[Andreas Pfeiffer]

Hi,

There are color schemes that you can use. Here is the documentation: https://www.omnis.net/developers/resources/onlinedocs/WebDev/03jscomps.html#js-themes

For fat client please see here: https://www.omnis.net/developers/resources/onlinedocs/Programming/01omnistools.html#color-themes-and-appearance

I hope this helps.

Best,

Andreas

[Andreas Pfeiffer]

Hello Khanh,

There is a typo in your code. You would need $designcols (with the “s”).

Best,

Andreas

[Andreas Pfeiffer]

Thank you Martin,

Have fun.

Best,

Andreas

[Andreas Pfeiffer]

Reading properties might only be possible in client methods. You may be able to read $name or $id from a server side method but some code might have changed a color on the client, so how would the server read such a property.

Therefore this can only be done from a client executed method.

Best,

Andreas

[Andreas Pfeiffer]

Hi Martin,

I do not see anything wrong in the reference. It points to the grid component in the instance.

However $designcols is a property that is not accessible in the instance. That is why it is called $designcols.

Best,

Andreas

• This reply was modified 2 years, 1 month ago by  Andreas Pfeiffer.
• This reply was modified 2 years, 1 month ago by  Andreas Pfeiffer.