We know that sometimes you want to change the properties of multiple methods without having to open the property dialog for each method.
For example, you want to set all methods to “Can be run in preemptive mode” status, then compile your database. So with compilation errors, you get an overview of the methods to modify to be preemptive.
Using the METHOD GET NAMES command to retrieve the list of methods from your database, and then using the METHOD SET ATTRIBUTES command to modify the attributes, lets you modify them all at the same time!
Humans have different taste preferences. For instance, some people prefer white over all other colors, while others find black to be more majestic … hence any new color trend tagged as ‘the new black’!
In order to accommodate different preferences, 4D enables you to personalize the method editor theme!
In the 4D preferences dialog, you can set several parameters for the editor such as the color of the background or each type of code element (i.e., commands and comments).
Thanks to these different options, you can completely customize the method editor to your taste. Whether you’re a fan of light or dark themes, 4D’s got you covered!
Here’s what a dark theme looks like:
Starting with 4D v17, the content of a multilevel collection can easily be displayed in different list boxes. Meaning that you can bind several list boxes to display nested details … without a single line of code! This can be achieved by simply using an object or a collection as the data source for another list box!
With the new list box collection type, the “Current item” and “Selected items” properties have been added. Keep in mind that the “Current item” property allows you to get an object, while the “Selected item” property returns a collection.
Imagine that your database contains several tables of types or categories. These tables are very simple, often with only an identifier and a text field. For demonstration purposes, let’s say it’s a shoe management database. To qualify the products, we need to define their type, color, pattern, material, season and so on.
It’s cumbersome to manage each of these tables in a list form and an input form and associated methods. In this case, the use of a generic form is essential to avoid duplication and simplify maintenance.
4D v17 introduces a new concept: ORDA. If you’re not familiar with ORDA yet, we’ve created a series of blog posts to explain how to use and take advantage of ORDA. When working with ORDA, you’re going to use entity selections, which are basically objects containing references to entities belonging to the same dataclass (i.e. table). One of the main benefits of ORDA, is the very simple and powerful ability of binding with forms.
In this blog post, you’ll learn how to display an entity selection in a list box. In fact, it’s very simple.
4D v17 includes dynamic forms, initially introduced in 4D v16 R6, a powerful and flexible way to dynamically build forms fully adapted to your end users’ needs. The possibilities of dynamic forms are tremendous. In this post, we’ll see a concrete example of what you can do with these new forms.
Recently, 4D introduced of a new type of variable: collections, as well as a large set of methods to manipulate them. With 4D v17, the possibilities of collections is becoming larger by being able to easily display the content of a collection. How? List boxes of collection type!
Sometimes the information you include in your document is best displayed in columns. Not only can columns help improve readability, but some types of documents – newspaper articles, newsletters, flyers, etc. – are often written in column format. The good news is that with 4D v17, you can henceforth create multi-column documents with 4D Write Pro! And beyond document creation, you can also convert your existing 4D Write documents containing multiple columns.
As in the 4D Write plugin, it’s possible to define the number of columns for an entire document. But here’s a good example where 4D Write Pro exceeds 4D Write: you can also set a different number of columns … per section!
While icons may seem insignificant in the grand scheme of design, they actually play a crucial role in improving human-software interactions by offering a method of communication beyond just text.
With 4D v16 R6, we have modernized the look of the Form Editor and the User Form Editor icons to improve readability and clarity.
Log files can be extremely useful for troubleshooting. They’re also a big help for finding the root cause of an incident. Logs let us track of where a problem occurred, and when. Before, with the Get 4D folder command, you could easily access the folder containing all the logs. Now, 4D v16 R6 makes easy to find a particular log file, thanks to the enhancement of the Get 4D file command.
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!