[Götz Krija]

Hello Franco,

Unfortunately, this seems to be a bug, so I have raised a fault for it under the reference ST/HE/1912

As a workaround you can change the keyboard shortcuts directly in the keys.json file in the Omnis data folder (e.g. on Windows: C:\Users\[USER]\AppData\Local\Omnis Software\OS 11 x64\studio\).

Götz

[Götz Krija]

Hi,

You would need to setup the RESTful Web server plugin. See: https://www.omnis.net/developers/resources/onlinedocs/WebDev/02jsremoteforms.html#push-connections

[…] if you are using a Web server to pass JavaScript client requests to the
Omnis server, you need both the standard Web server plugin, and the
RESTful Web server plugin to be installed with the Web server […]

Götz

[Götz Krija]

Hi,

I do not think that PDF files can be displayed in the picture control. Instead you could use the HTML control in the JS Client and the oBrowser control in the Thick Client.

Götz

[Götz Krija]

Hi Felipe,

You need to add the tooltip by code, e.g.:

Do $classes.myRemoteForm.$objs.myEditControl.$tooltip.$assign(con(‘tooltip line 1′,kCr,’tooltip line 2’))

Götz

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

[Götz Krija]

Hi Joel,

On Windows platform you can use:

Register DLL (‘user32′,’GetKeyState’,’JJ’)
Call DLL (‘user32′,’GetKeyState’,20) Returns lCapsLock
If lCapsLock
OK message {Caps Lock pressed}
End If

Götz

[Götz Krija]

Hi Tom,

This error is probably caused by using non-unicode data with an Omnis unicode version.

I could imagine that you are using a report class with non-unicode page setup data in $pagesetupdata. Clearing $pagesetupdata should solve the issue.

Götz

• This reply was modified 2 years, 10 months ago by  Götz Krija.

[Götz Krija]

Hi,

You can probably use the “Do async method” command for this purpose: https://www.omnis.net/developers/resources/technotes/tnwe0014.jsp

Götz

[Götz Krija]

Hello Franco,

I think the keys.json file is only created when you change any keyboard shortcut in the Property Manager for the very first time (in $root.$prefs.$keys). The file should then be created in: /Users/[USER]/Library/Application\ Support/Omnis/Omnis\ Studio\ 11/studio/

Götz

[Götz Krija]

Hi Uwe,

So the PDF file is stored as binary? In this case you probably need to create the PDF file temporarily in the web server’s file system (e.g. by using FileOps.$createtmpfile if the Omnis server and the web server are running on the same computer).

You can then display the PDF in the HTML control using the assignpdf $clientcommand or getpdf command.

Please note that the pdf folder must be specified in getpdfFolders config.json item. See here: https://www.omnis.net/developers/resources/onlinedocs/WebDev/02jsremoteforms.html#setting-pdf-folders