[Götz Krija]

Dear Uwe,

This sounds like a known fault: ST/JS/3417 – JS Datagrid with Droplist field doesn’t allow you to scroll

Looks like the issue is present in Chrome and Edge. Firefox works fine for me.

Götz

[Götz Krija]

This works for me:

JavaScript: var x = 0xff
Do $cinst.$objs.Top.$backcolor.$assign(x)

Götz

[Götz Krija]

It is not clear to me what your question is here and why you cannot change colors via Omnis Properties or via user.css.

If you really need to change the colors via CSS and via Javascript: command, then for example, the following would change the color of your button controls to red:

JavaScript:$(‘<style>.omnis-button {background-color: red !important;}</style> ‘).appendTo(“head”);

Götz

[Götz Krija]

Is this a Headed Listbox in a thick-client window? If so, you can probably use the approach mentioned in the technical note: https://www.omnis.net/developers/resources/technotes/tngi0029.jsp

Something like this should work:

On evClick
Calculate hrzPos as (mouseover(kMHorz)-$cobj.$left)+($cobj.$hscroll-1)*8
Calculate columnWidths as $cobj.$columnwidths
Repeat
Calculate colNum as colNum+1
Calculate colRight as colRight+strtok(‘columnWidths’,”,”)
Until colRight>hrzPos
OK message {Value in clicked cell: [iList.[con(‘c’,colNum)]]}

Götz

[Götz Krija]

Hi Thomas,

I think the message is caused by the Remote Debug Server. The specified port is probably used by another (Omnis) process.

You can enable the RemoteDebug menu in the Omnis Server by executing the following (e.g. in the $construct of the Startup_Task in your library):

Do $root.$prefs.$showremotedebugmenu.$assign(kTrue)

If you then open the menu item in the Omnis Server, you can set a different port in the configuration window. After restarting Omnis, the message should no longer appear in the trace log.

Alternatively, you can specify the debugPort in the remote_debug_server_config.json file in your Omnis Server installation (C:\Users\[USER]\AppData\Local\Omnis Software\OS 10.22 31896 SVR\clientserver\server\remotedebug\remote_debug_server_config.json).

When Omnis Server is running as a Windows service, the remote_debug_server_config.json file is in the system profile’s AppData area. See Technical Note: https://www.omnis.net/developers/resources/technotes/tnwi0002.jsp

Götz

[Götz Krija]

Hallo Herr Köhler,

ich verstehe leider nicht, was genau geändert werden soll. Grundsätzlich können die Farben aber in $root.$prefs.$appearance und $root.$prefs.$windowoptions angepasst werden (z.B. im Property Manager).

Details dazu finden Sie hier: https://www.omnis.net/developers/resources/onlinedocs/Programming/01omnistools.html#color-themes-and-appearance

Götz

• This reply was modified 1 year, 10 months ago by  Götz Krija.

[Götz Krija]

Hi Nathanaël,

I do not have much experience with Python, but the manual says you can import omnis_calls in your main.py and use sendResponse or sendError if required. So you are probably right and the oPyWorker.$methoderror() method should receive the error in this case.

I have put in a fault for engineering to investigate further. The reference is ST/EC/1804

As a workaround you can probably raise an exception in the Python script:

raise Exception(“this is an error”)

Götz

[Götz Krija]

Hello Nathanaël,

Did you test the demo library in the Omnis Studio HUB > Samples > Python Worker

The library works fine for me on Windows 11:

1. Installed Python 3.11.4 (in the installer checked the box ‘Add python.exe to PATH’)

2. In command line executed: pip install -r “C:\Users\[USER]\AppData\Local\OS 11 35439 x64\pyworker\requirements.txt”

3. Tested the Python Worker sample in HUB and the result was successfully returned in the $pyWorkerComplete method

Götz

[Götz Krija]

Okay, danke.

Folgendes funktioniert bei mir mit einem Label.

1. In der Remoteform-Klasse, die $backalpha Property des Labels (mit $name=Top) im Property Manager auf 255 stellen

2. In der clientseitigen Methode eine lokale Variable mit dem Namen x anlegen (Type: Var)

3. In der clientseitigen Methode den Code ausführen:

JavaScript: var x = 0xff
Do $cinst.$objs.Top.$backcolor.$assign(x)

Götz

[Götz Krija]

Ich hatte es wie gesagt mit einem Transbutton Control getestet und dort $backcolor gesetzt. Andere Controls haben vermutlich andere Properties, die geändert werden müssen.

Deshalb nochmal die Frage: Um was für ein Control handelt es sich bzw. was steht in $componentctrl im Property Manager wenn das Control in der Remoteform-Klasse ausgewählt ist?

[Götz Krija]

Um welches Control handelt es sich?

Ich hatte es mit einem TransButton getestet und das funktionierte einwandfrei.

Götz

[Götz Krija]

Hi Uwe,

You can override the Remoteform’s $event method and use evLayoutChanged which has a parameter pBreakpoint that contains the integer value of the (new) layout break point:

On evLayoutChanged
If pBreakpoint=320
Do $cinst.$objs.native_list.$width.$assign(10)
Else If pBreakpoint=768
Do $cinst.$objs.native_list.$width.$assign(200)
Else
Do $cinst.$objs.native_list.$width.$assign(0)
End If

Götz

• This reply was modified 1 year, 8 months ago by  Götz Krija.

[Götz Krija]

Hallo Heiko,

das sollte so auch auf mobilen Platformen funktionieren.

Götz

[Götz Krija]

Okay, das Bild zeigt ein JS SubFormSetPanel. Das Paged Pane dient hier nur als Container.

Um die Title-Farbe der Panels in Studio 11 zu ändern, kann man z.B. Folgendes einfügen in die user.css Datei (in C:\Users\[USER]\AppData\Local\Omnis Software\OS 11 35439 x64\html\css\) :

.subformSetPanelTitleBackColor .omnis-wf-title-text {
background-color: lightblue !important;
}

Anschließend muss die Property $cssclassname des Paged Pane’s im Remoteform entsprechend gesetzt werden auf: subformSetPanelTitleBackColor

Götz (kein Pseudonym)

[Götz Krija]

Hallo Heiko,

ich bin mir leider immer noch nicht sicher, was gemeint ist. Ein Paged Pane Control hat keinen oberen Teil.

Zum Umschalten zwischen den Panes wird normalerweise ein separates Tab Strip Control (im Thick-Client) oder ein Tab Bar Control (im JS-Client) verwendet.

Götz