4D View Pro is getting more feature-rich with every R-release and 4D v17 R6 is no exception! A new command is available which allows you to specify a 4D method’s parameters, name, type, and a summary. Now your methods can be more informative and descriptive, helping end users to use them correctly.
Do you want to declare a date or time? What about giving a short description to help users understand what the method does? It can now be done with VP SET ALLOWED METHODS command!
In a previous blog post, you learned how to build sophisticated and complex search criteria by applying formulas in an ORDA query. To further provide you with complete and powerful development tools, a new ORDA method available: orderByFormula(). With the help of formulas, you can now order an entity selection using complex criteria in a project method or 4D expression.
Improved and simplified 4D commands just keep coming. Now you can set colors in your form objects using CSS strings instead of numeric values. Previously CSS colors for objects were declared with a 4-byte longint (e.g., 0x00RRGGBB). But if you feel more comfortable writing BLUE instead of its numeric equivalent 255 (0xFF), we’ve got good news … 4D v17 R6 makes it possible!
With 4D v17 R6, you can programmatically customize the style of your 4D View Pro documents. There’s three ways to go about it, you can: 1) use the default style commands to define the general style of a sheet, 2) use the stylesheet commands to define frequently used custom styles, and finally 3) use the cell style commands to define the style of specific cells.
In 4D v17 R6, ORDA queries are becoming increasingly more powerful and concise. This blog post is for those of you who need more sophisticated search criteria than just a simple syntax like “name = Smith‘”. With this R-release, you can use any project method or 4D expression in the query() member method by using formulas.
What better way to explain this feature than with an example? Let’s dig into the details.
With 4D v17 R5, we’ve improved the debug logs by adding methods and allowing each process to be traced independently. With this R-release, we’ve gone a step further by shipping a debug logs analyzer tool to help you monitor process execution. You’ll be able to see which processes are the most consuming, the call chain with the corresponding running time, and much more.
CRUD (Create, Read, Update, Delete), a pillar of database actions, makes its debut in 4D for iOS in 4D v17 R6.
In 4D v17 R5, we introduced actions so you could better interact with your 4D for iOS apps. This included the ability to create actions to execute 4D code from your iOS apps. Things are getting even more interesting with this R-release, now you can easily manage and edit your app content using parameters.
If you need to read or write hundreds of different values or formulas, you can do it faster, easier, and at the same time by using collections. New commands are available for this: VP SET VALUES, VP Get values, VP SET FORMULAS, and VP Get formulas.
When programming an application, you may need to know where you are in your code, especially when one method calls other methods, which may then call other methods. That’s why it’s very helpful to see the chain of methods, or the call chain, during the debugging process. For this, 4D v17 R6 provides the new Get call chain command to give you an insight into the executed code. Now you won’t have to worry about getting lost anymore!
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