When creating a document, you need to define the page size, orientation, and margins. Starting with v17 R3, you can do all this by programming. And for that, new attributes are at your disposal.
Your forms may need to be changed depending on your customer or user needs. For example, the color black might be perfect for one user but not so much for another user (who sees blue as the ultimate perfection). Luckily, dynamic forms (introduced with 4D v16 R6) are here to help you handle your users’ preferences. But rewriting an existing form to a dynamic form could be a difficult task, and it’s not always easy to start with a blank page. Ideally, it’d be best to have a draft that can be modified and improved. With 4D v17 R3, it’s now possible to easily convert a classic 4D form (stored in .4DB file) to a dynamic form.
Since v16 R5, it’s been possible to access and modify an existing header and footer by programming. If you want to add a header and footer to your 4D Write Pro document, you use a template to do so!
If you’re not a fan of templates, good news! With 4D v17 R3, you can create a header and a footer by programming for a given section.
Want a different background per section? Or maybe a different margin per section? How about a different number of columns per section? Want to do all this with code?
With 4D v17 R3, you can manipulate sections with code to create complex and beautiful documents!
Developing an application is often a very collaborative job, involving many people. In this case, you may want store your development in a source control repository, or have a history of the work done during the day, or send your database to a colleague and see the changes when they’re done working on it.
All of the above scenarios are now possible! Beginning with v17 R3, you can export the .4DB file into multiple text files. This offers you many new possibilities.
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.
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!
* Your privacy is very important to us. Please click here to view our Policy