[Andreas Pfeiffer]

Hi Martin,

We just have tested with the latest release (10.2 build 31315) on Windows. It does work after doing a “save window setup”.

Best regards,

Andreas

[Andreas Pfeiffer]

Hi Martin,

changing the font size can also be done using Cmd/Ctr.+ in the IDE. When you then save the windows setup it should remember the new font size.

Here are the keyboard shortcuts: https://www.omnis.net/developers/resources/onlinedocs/index.jsp?detail=Programming/04debug.html#keyboard-shortcuts

I think what you are looking for might be the Debugger interrupt which is Alt-I on Windows and Cmd-Option-I on macOS.

You can change this in the $keys property of your Omnis. Click on the root level in the tree list of the class browser – then onto the Prefs link. That opens the property manager and shows all the properties of your Omnis environment. Then search for “keys”.

Regarding the crashes you should contact Omnis support and send them your library together with a description how to reproduce the problem.

Best regards,

Andreas

[Andreas Pfeiffer]

Great!
Have a great day!
Best,
Andreas

[Andreas Pfeiffer]

Hi Denis,
You may want to remove the libraries from the /Startup folder of your Omnis installation. Note if your installation is split in two locations (Application and AppData) you also want to remove those libraries from the /firstruninstall folder. Otherwise Omnis re-creates the deleted libraries in the /appData
Best,
Andreas

[Andreas Pfeiffer]

Hi Coralie,
I am a little bit confused when you write that the form is launched by the Startup_Task. One can actually do this but normally a remote form is instantiated by either using the html file that points to it or using i.e. $ctask.$changeform or $openform. That said they are using a remote task (not the Startup_Task) as a container for its own instance.
However you could try to find out why the crash happens using the command
Do sys(3000) somewhere in the code. This brings up a message that the code is then traced in a log file. When Omnis crashes you can have a look in that log file and possibly see what command caused the problem.