Product blank

New possibilities to customize the code editor

When it comes to customizing the code editor, everyone thinks of the font and colors of the code. But it is also possible to customize the code editor window and some interactions with the code. Everyone has their own preferences and ways of working.

Moreover, the most essential part of a code editor is the writing code area. With 4D v19 R4, we have redesigned the editor to highlight your code and give it as much space as possible.

This is precisely why 4D v19 R4 enables you to show or hide the ten clipboards. If you don’t use all ten clipboards, you can lighten the toolbar with the “Show clipboard” preference.

Product blank

Saving project source code without tokens

Commands, constants, tables and fields are stored with their tokens in the project source code files (4dm files). This allows 4D to rename them automatically. But sometimes, you would like these source code files to be stored without tokens for a better readability with a version control system or an external code editor, or for better code sharing between projects. Let’s see how to make 4D store source code without these tokens.

Product blank

Tag your comments, a feature by developers for developers

Comments are essential in a developer’s life. When we work on a new feature, we often add comments that are reminders. For example:

  • to validate a part of code with a colleague,
  • to refactor a function,
  • to fix code that is slowing down the performance,
  • to split a method or a class into sections,
  • to prepare the skeleton of a class and add a todo comment inside each function.


Even if you write some straightforward code, try reading it months or years later. Will it still seem simple, or would you wish you’d added comments?

4D v19 R4 takes comments to a whole new level with comment tags that enables you to better organize your comments.

Product blank

Improved productivity with Object check syntax

Auto-completion for classes is available since 4D v18 R4. This feature simplifies code writing and limits errors in function names, for example. But it doesn’t avoid them entirely; it’s easy to reverse two letters or to forget a capital letter, and then have to spend time looking for why your code doesn’t work.

So what better way than to ask 4D to check if the classes or functions already exist?

Starting with 4D v19 R4, a warning is displayed in the code editor if you call a function that does not exist.