Changes in behavior (language)

The SET EXTERNAL DATA PATH command no longer creates the file when it does not exist. It simply stores a pathname.

Under Windows, the MAXIMIZE WINDOW command now takes size constraints mentioned on forms into account. Results will thus differ according to sizes specified on the form (in the case of a form window) and the size of the target window (MDI window):

• If the size constraints are greater than the target size: the window is "maximized" as in previous versions of 4D; i.e., it is resized to fit the size of the parent "Multiple Document Interface" (MDI) window; its title bar and borders are hidden and its control buttons (minimize, restore and close) are placed to the right of the application menu bar.

• If at least one of the size constraints is lower than the target size (for example, if the width of the MDI window is 100 and the maximum width of the form window is 80): the window is not "maximized," but simply resized to its maximum allowed size.

In previous versions of 4D, the OBJECT GET COORDINATES command, used on a list box, only returned the coordinates of the list box itself, regardless of the part specified by the object parameter. For example, if the object parameter specified a header, the OBJECT GET COORDINATES command simply returned the list box coordinates.

Beginning with 4D v15, when the object parameter references a list box header, column or footer, this command returns the coordinates of the object specified.

Remember to modify your code if you want to get the coordinates of the list box itself.

For reasons of consistency, the point of origin for coordinates remains unchanged, i.e., the top left corner of the form containing the object. For more information about the results obtained with list box sub-objects, see the documentation for the OBJECT GET COORDINATES command.

See also the new command added in 4D v15: LISTBOX GET CELL COORDINATES.

In previous versions of 4D, local variables defined in the calling context could be accessed in the PROCESS 4D TAGS execution context in interpreted mode. This is no longer the case.

The PROCESS 4D TAGS command now accepts an undefined number of parameters that can be of any type (text, date, time, longint, real, etc.). Arrays can also be used by means of array pointers. Just like in 4D methods, these parameters are available through regular arguments ($1, $2, etc.).

(Other new changes: a new 4DEVAL tag is available and the 4DLOOP tag now accepts pointers).

The WA SET PREFERENCE and WA GET PREFERENCE commands accept a new selector that allows a URL or file to be dropped in the Web area (to be set before the URL is loaded, thus, for instance, in the On Load form event).

For security reasons, changing the contents of a Web area by dropping a file or a URL in the area is now disallowed by default.

The mouse cursor displays a forbidden icon when a user tries to drop a file or URL in the area.
(In previous versions, you had to install a specific filter, using WA SET URL FILTERS for example, to prevent such actions).

If you want to allow this feature, you need to use the new WA enable URL drop Web area preference.