fix 19.7

docs/WebServer/qodly-studio.md

@@ -154,7 +154,7 @@ You will then be prompted to enter the [access key](../Admin/webAdmin.md#access-
 
 ## Using Qodly Studio
 
-The official Qodly Studio documentation is available on the [Qodly documentation website](developer.qodly.com/docs/studio/overview.md).
+The official Qodly Studio documentation is available on the [Qodly documentation website](https://developer.qodly.com/docs/studio/overview).
 
 You can rely on this documentation and its associated resources for developing web applications powered by webforms. However, depending on implementation stage, 4D developers will either use Qodly Studio or 4D IDE.
 

i18n/de/docusaurus-plugin-content-docs/current/API/CollectionClass.md

@@ -57,6 +57,7 @@ A collection is initialized with:
 | [<!-- INCLUDE #collection.map().Syntax -->](#map)&nbsp;&nbsp;&nbsp;&nbsp;<!-- INCLUDE #collection.map().Summary -->|
 | [<!-- INCLUDE #collection.max().Syntax -->](#max)&nbsp;&nbsp;&nbsp;&nbsp;<!-- INCLUDE #collection.max().Summary -->|
 | [<!-- INCLUDE #collection.min().Syntax -->](#min)&nbsp;&nbsp;&nbsp;&nbsp;<!-- INCLUDE #collection.min().Summary -->|
+| [<!-- INCLUDE #collection.multiSort().Syntax -->](#multisort)&nbsp;&nbsp;&nbsp;&nbsp;<!-- INCLUDE #collection.multiSort().Summary -->|
 | [<!-- INCLUDE #collection.orderBy().Syntax -->](#orderby)&nbsp;&nbsp;&nbsp;&nbsp;<!-- INCLUDE #collection.orderBy().Summary -->|
 | [<!-- INCLUDE #collection.orderByMethod().Syntax -->](#orderbymethod)&nbsp;&nbsp;&nbsp;&nbsp;<!-- INCLUDE #collection.orderByMethod().Summary -->|
 | [<!-- INCLUDE #collection.pop().Syntax -->](#pop)&nbsp;&nbsp;&nbsp;&nbsp;<!-- INCLUDE #collection.pop().Summary -->|
@@ -2195,6 +2196,144 @@ If the collection is empty, `.min()` returns *Undefined*.
 <!-- END REF -->
 
 
+<!-- REF collection.multiSort().Desc -->
+## .multiSort()
+
+<details><summary>History</summary>
+
+| Version | Changes |
+| ------- | ------- |
+| v20 R3  | Added   |
+
+</details>
+
+<!-- REF #collection.multiSort().Syntax -->**.multiSort**() : Collection<br/>**.multiSort**( *colsToSort* : Collection ) : Collection<br/>**.multiSort**( *formula* : 4D.Function ; *colsToSort* : Collection ) : Collection<!-- END REF -->
+
+
+<!-- REF #collection.multiSort().Params -->
+| Parameter  | Typ         |    | Beschreibung                                                                                                                  |
+| ---------- | ----------- |:--:| ----------------------------------------------------------------------------------------------------------------------------- |
+| formula    | 4D.Function | -> | Formula object                                                                                                                |
+| colsToSort | Collection  | -> | Collection of collections and/or objects with {`collection`:*colToSort*;`order`:`ck ascending` or `ck descending`} properties |
+| Ergebnis   | Collection  | <- | Original collection sorted|<!-- END REF -->
+
+
+|
+
+
+#### Beschreibung
+
+The `.multiSort()` function <!-- REF #collection.multiSort().Summary -->enables you to carry out a multi-level synchronized sort on a set of collections<!-- END REF -->.
+> This function modifies the original collection as well as all collections used in *colsToSort* parameter.
+
+If `.multiSort()` is called with no parameters, the function has the same effect as the [`.sort()`](#sort) function: the collection is sorted (only scalar values) in ascending order by default, according to their type. If the collection contains values of different types, they are first grouped by type and sorted afterwards. Types are returned in the following order:
+
+1. Null
+2. booleans
+3. strings
+4. numbers
+5. objekte
+6. collections
+7. dates
+
+
+**Single-level synchronized sort**
+
+To sort several collections synchronously, just pass in *colsToSort* a collection of collections to sort. You can pass an unlimited number of collections. The original collection will be sorted in ascending order and all *colsToSort* collections will be sorted in a synchronized manner.
+
+:::note
+
+All *colsToSort* collections must have the same number of elements, otherwise an error is returned.
+
+:::
+
+If you want to sort the collections in some other order than ascending, you must supply a *formula* ([Formula object](FunctionClass.md#formula) that defines the sort order. The return value should be a boolean that indicates the relative order of the two elements: **True** if *$1.value* is less than *$1.value2*, **False** if *$1.value* is greater than *$1.value2*. You can provide additional parameters to the formula if necessary.
+
+The formula receives the following parameters:
+
+- $1 (object), where:
+    - *$1.value* (any type): first element value to be compared
+    - *$1.value2* (any type): second element value to be compared
+- $2...$N (any type): extra parameters
+
+**Multi-level synchronized sort**
+
+Defining a multi-level synchronized sort requires that you pass an object containing {`collection`:*colToSort*;`order`:`ck ascending` or `ck descending`} properties instead of the *colToSort* itself for every collection to use as sub-level.
+
+The sort levels are determined by the order in which the collections are passed in the *colsToSort* parameter: the position of a `collection`/`order` object in the syntax determines its sort level.
+
+:::note
+
+The `.multiSort()` function uses a [stable](https://en.wikipedia.org/wiki/Sorting_algorithm#Stability) sort algorithm.
+
+:::
+
+#### Beispiel 1
+
+A simple synchronized sort of collections with different value types:
+
+```4d
+var $col;$col2;$col3 : Collection
+$col:=["A"; "C"; "B"]
+$col2:=[1; 2; 3]
+$col3:=[["Jim"; "Philip"; "Maria"]; ["blue"; "green"]; ["11"; 22; "33"]]
+
+$col.multiSort([$col2; $col3])
+//$col=["A","B","C"]
+//$col2=[1,3,2]
+//$col3[0]=["Jim","Philip","Maria"]
+//$col3[1]=["11",22,"33"]
+//$col3[2]=["blue","green"]
+
+```
+
+#### Beispiel 2
+
+You want to sort three synchronized collections: city, country, and continent. You want an ascending sort of the first and the third collections, and synchronization for the second collection:
+
+```4d
+var $city : Collection
+var $country : Collection
+var $continent : Collection
+
+$city:=["Paris"; "Lyon"; "Rabat"; "Eching"; "San Diego"]
+$country:=["France"; "France"; "Morocco"; "Germany"; "US"]
+$continent:=["Europe"; "Europe"; "Africa"; "Europe"; "America"]
+
+$continent.multiSort($country; {collection: $city; order: ck ascending})
+//$continent=["Africa", "America","Europe","Europe","Europe"]
+//$country=["Morocco", "US","Germany","France","France"]
+//$city=["Rabat","San Diego","Eching","Lyon","Paris"]
+
+```
+
+#### Beispiel 3
+
+You can also synchronize collections of objects.
+
+```4d
+var $name : Collection
+var $address : Collection
+$name:=[]
+$name.push({firstname: "John"; lastname: "Smith"})
+$name.push({firstname: "Alain"; lastname: "Martin"})
+$name.push({firstname: "Jane"; lastname: "Doe"})
+$name.push({firstname: "John"; lastname: "Doe"})
+$address:=[]
+$address.push({city: "Paris"; country: "France"})
+$address.push({city: "Lyon"; country: "France"})
+$address.push({city: "Eching"; country: "Germany"})
+$address.push({city: "Berlin"; country: "Germany"})
+
+$name.multiSort(Formula($1.value.firstname<$1.value2.firstname); $address)
+//["Alain Martin","Jane Doe","John Smith","John Doe"]
+//["Lyon France","Eching Germany","Paris France","Berlin Germany"]
+
+```
+
+
+<!-- END REF -->
+
 
 
 <!-- REF collection.orderBy().Desc -->
@@ -2326,6 +2465,7 @@ Ordering a collection of objects using a collection of criteria objects:
 Ordering with a property path:
 
 ```4d
+
  var $crit; $c; $c2 : Collection
  $c:=New collection
  $c.push(New object("name";"Cleveland";"phones";New object("p1";"01";"p2";"02")))
@@ -3010,6 +3150,7 @@ By default, new elements are filled will **null** values. You can specify the va
 
 
 <!-- REF #collection.reverse().Params -->
+
 | Parameter | Typ        |    | Beschreibung                                               |
 | --------- | ---------- |:--:| ---------------------------------------------------------- |
 | Ergebnis  | Collection | <- | Inverted copy of the collection|<!-- END REF -->
@@ -3194,6 +3335,7 @@ It can set the following parameter(s):
 *   (mandatory if you used a method) *$1.result* (boolean): **true** if the element value evaluation is successful, **false** otherwise.
 *   *$1.stop* (boolean, optional): **true** to stop the method callback. The returned value is the last calculated.
 
+
 In any case, at the point where `.some()` function encounters the first collection element returning true, it stops calling the callback and returns **true**.
 
 By default, `.some()` tests the whole collection. Optionally, you can pass the index of an element from which to start the test in *startFrom*.

i18n/de/docusaurus-plugin-content-docs/current/API/FileHandleClass.md

@@ -267,13 +267,31 @@ This property is **read-only**.
 
 The `.offset` property returns <!-- REF #FileHandleClass.offset.Summary -->the current offset of the data stream (position inside the document)<!-- END REF -->. The offset value is automatically updated after read and write operations.
 
-Setting the `.offset` will change its current value.
+Setting the `.offset` will change its current value at the moment of the next read or write operation.
 
 - If the passed value is negative, the `.offset` is set to the start of the file (zero).
 - If the passed value is higher than the size of the file,  the `.offset` is set to the end of the file (size of file).
 
 This property is **read/write**.
 
+:::caution
+
+The unit of offset measurement differs according to the reading function: with [`readBlob()`](#readblob), `.offset` is a number of bytes, whereas with [`readText()`](#readtext)/[`readLine()`](#readline) it is a number of characters. Depending on the file's character set, a character corresponds to one or more bytes. So, if you start reading with `readBlob()` and then call `readText()`, text reading will start at an inconsistent position. It is therefore essential to set the `.offset` property yourself if you switch from reading/writing blob to reading/writing text in the same filehandle. Beispiel:
+
+```4d
+  // Open a european text file using utf-16 encoding (two bytes per character)
+  // We want to read the first 10 characters as bytes, then the remaining as text.
+$fh:=File("/RESOURCES/sample_utf_16.txt").open()
+  // read the 20 first bytes (i.e. 10 characters)
+$b:=$fh.readBlob(20) // $fh.offset=20
+  // then read all text skipping the first 10 characters we just read in previous blob
+  // because we are now reading text instead of bytes, the meaning of 'offset' is not the same.
+  // We need to translate it from bytes to characters.
+$fh.offset:=10 // ask to skip 10 utf-16 characters (20 bytes)
+$s:=$fh.readText()
+```
+
+:::
 
 <!-- END REF -->
 
@@ -310,6 +328,8 @@ The `.readBlob()` function <!-- REF #FileHandleClass.readBlob().Summary -->retur
 
 When this function is executed, the current position ([.offset](#offset)) is updated after the last byte read.
 
+
+
 #### See also
 
 [.writeBlob()](#writeblob)
@@ -485,6 +505,7 @@ When this function is executed, the current position ([.offset](#offset)) is upd
 <!--REF #FileHandleClass.writeLine().Syntax -->**.writeLine**( *lineOfText* : Text ) <!-- END REF -->
 
 
+
 <!--REF #FileHandleClass.writeLine().Params -->
 | Parameter    | Typ  |    | Beschreibung                             |
 | ------------ | ---- | -- | ---------------------------------------- |

i18n/de/docusaurus-plugin-content-docs/current/Notes/updates.md

@@ -11,6 +11,7 @@ Read [**What’s new in 4D v20 R3**](https://blog.4d.com/en-whats-new-in-4d-v20-
 
 #### Highlights
 
+- New [`collection.multiSort`](../API/CollectionClass.md#multisort) function.
 - Support of *context* parameter in [`Formula from string`](../API/FunctionClass.md#formula-from-string).
 - Support of `headers` property in *connectionHandler* parameter of [4D.WebSocket.new](../API/WebSocketClass.md#4dwebsocketnew).
 - 4D Language commands: [What's new page](https://doc.4d.com/4Dv20R2/4D/20-R2/What-s-new.901-6398284.en.html) on doc.4d.com.
@@ -39,6 +40,10 @@ Read [**What’s new in 4D v20 R2**](https://blog.4d.com/en-whats-new-in-4d-v20-
 - [**Fixed bug list**](https://bugs.4d.fr/fixedbugslist?version=20_R2): list of all bugs that have been fixed in 4D v20 R2.
 
 
+#### Behavior changes
+
+- **Warning**: the starting [`offset`](../API/FileHandleClass.md#offset) value of [4D.FileHandle](../API/FileHandleClass.md) objects was incorrectly set to 1 instead of 0. A fix has been done and the value is now 0.
+
 
 ## 4D v20.x
 
@@ -89,6 +94,7 @@ Read [**What’s new in 4D v20**](https://blog.4d.com/en-whats-new-in-4d-v20/),
 
 #### Behavior changes
 
+- **Warning**: the starting [`offset`](../API/FileHandleClass.md#offset) value of [4D.FileHandle](../API/FileHandleClass.md) objects was incorrectly set to 1 instead of 0. A fix has been done and the value is now 0.
 - For HTTP RFC compliance, [`HTTPRequestClass.response.headers`](../API/HTTPRequestClass.md#response) property now returns all header names **in lowercase**. If you want your code to continue working as before, use the new [`HTTPRequestClass.response.rawHeaders`](../API/HTTPRequestClass.md#response) property.
 - TLS certificates are now automatically validated by 4D when sending HTTP requests with [`4D.HTTPRequest.new()`](../API/HTTPRequestClass.md#new), and rejected with an error if they are invalid. A new *option* property allows you to control this validation.
 - TLS v1.0 and TLS v1.1 are deprecated, they are no longer supported as `Min TLS version` on 4D Server. Version 1.3 is now selected by default and is automatically used if `_o_TLSv1_0` or `_o_TLSv1_1` constants are set with [`SET DATABASE PARAMETER`](https://doc.4d.com/4dv20/help/command/en/page642.html).

i18n/de/docusaurus-plugin-content-docs/current/REST/authUsers.md

@@ -19,6 +19,15 @@ When [scalable sessions are enabled](WebServer/sessions.md#enabling-sessions) (r
 If the `On REST Authentication` database method has not been defined, a `guest` session is opened.
 
 
+## Preemptive mode
+
+On 4D Server, REST requests are automatically handled through preemptive processes, **even in interpreted mode**. You need to make sure that your code is [compliant with a preemptive execution](../WebServer/preemptiveWeb.md#writing-thread-safe-web-server-code).
+
+> To debug interpreted web code on the server machine, make sure the debugger is [attached to the server](../Debugging/debugging-remote.md) or [to a remote machine](../Debugging/debugging-remote.md#attaching-the-debugger-to-a-remote-4d-client). Web processes then switch to cooperative mode and the web server code can be debugged.
+
+With 4D single-user, interpreted code always runs in cooperative mode.
+
+
 ## Beispiel
 
 In this example, the user enters their email and password in an html page that requests [`$directory/login`]($directory.md#directorylogin) in a POST (it is recommended to use an HTTPS connection to send the html page). The `On REST Authentication` database method is called to validate the credentials and to set the session.

i18n/de/docusaurus-plugin-content-docs/current/WebServer/preemptiveWeb.md

@@ -15,8 +15,8 @@ The following table indicates whether the preemptive mode is used or is availabl
 | 4D Server           | Interpreted ([debugger attached](../Debugging/debugging-remote.md)) | Interpreted (debugger detached) | Kompiliert    |
 | ------------------- | ------------------------------------------------------------------- | ------------------------------- | ------------- |
 | REST Server         | cooperative                                                         | preemptive                      | preemptive    |
-| Web Server          | cooperative                                                         | *web setting*                   | *web setting* |
-| Web Services Server | cooperative                                                         | *web setting*                   | *web setting* |
+| Web Server          | cooperative                                                         | cooperative                     | *web setting* |
+| Web Services Server | cooperative                                                         | cooperative                     | *web setting* |
 
 | 4D remote/single-user | Interpretiert | Kompiliert    |
 | --------------------- | ------------- | ------------- |

i18n/de/docusaurus-plugin-content-docs/current/WebServer/qodly-studio.md

@@ -123,16 +123,10 @@ For deployment, the WebAdmin server is not necessary. End-user access to your we
 
 ### Using project methods
 
-We recommend using class functions over methods, but you can still use your project methods as REST functions in the studio.
-
-To be used in Qodly Studio, project methods must be defined as Datastore, Dataclass, Entity or Entity selection class functions.
-
-To check if a method is available as REST function:
-1. In the Explorer of your 4D application, **right-click a project method** > **Edit Properties...** to open the Method Properties dialog.
-2. Check that the **REST Server** option is checked.
-
-Selecting **Scope** > **Catalog** designates the project method as a function of the Datastore class. No table (dataclass) is assigned in this case.
+We recommend using class functions over project methods. Only class functions can be called from components. However, you can still use your project methods in Qodly Studio in two ways:
 
+- You can call your methods from class functions.
+- You can directly [execute your methods](https://developer.qodly.com/docs/studio/coding#methods-and-classes) from the Qodly Explorer.
 
 ## Opening Qodly Studio
 

i18n/de/docusaurus-plugin-content-docs/current/WebServer/sessions.md

@@ -53,14 +53,6 @@ The current `Session` object can then be accessed through the [`Session`](API/Se
 
 Web processes usually do not end, they are recycled in a pool for efficiency. When a process finishes executing a request, it is put back in the pool and made available for the next request. Since a web process can be reused by any session, [process variables](Concepts/variables.md#process-variables) must be cleared by your code at the end of its execution (using [`CLEAR VARIABLE`](https://doc.4d.com/4dv18/help/command/en/page89.html) for example). This cleanup is necessary for any process related information, such as a reference to an opened file. This is the reason why **it is recommended** to use the [Session](API/SessionClass.md) object when you want to keep session related information.
 
-### Preemptive mode
-
-On 4D Server, Web server sessions are automatically handled through preemptive processes, **even in interpreted mode**. You need to make sure that your web server code is [compliant with a preemptive execution](preemptiveWeb.md#writing-thread-safe-web-server-code).
-
-> To debug interpreted web code on the server machine, make sure the debugger is [attached to the server](Debugging/debugging-remote.md) or [to a remote machine](Debugging/debugging-remote.md#attaching-the-debugger-to-a-remote-4d-client). Web processes then switch to cooperative mode and the web server code can be debugged.
-
-With 4D single-user, interpreted code always runs in cooperative mode.
-
 
 ## Sharing information
 

i18n/de/docusaurus-plugin-content-docs/version-19/REST/authUsers.md

@@ -17,6 +17,14 @@ When [scalable sessions are enabled](WebServer/sessions.md#enabling-sessions) (r
 
 If the `On REST Authentication` database method has not been defined, a `guest` session is opened.
 
+
+## Preemptive mode
+
+On 4D Server, REST requests are automatically handled through preemptive processes, **even in interpreted mode**. You need to make sure that your code is [compliant with a preemptive execution](../WebServer/preemptiveWeb.md#writing-thread-safe-web-server-code).
+
+With 4D single-user, interpreted code always runs in cooperative mode.
+
+
 ## Beispiel
 
 In this example, the user enters their email and password in an html page that requests [`$directory/login`]($directory.md#directorylogin) in a POST (it is recommended to use an HTTPS connection to send the html page). The `On REST Authentication` database method is called to validate the credentials and to set the session.
@@ -43,6 +51,7 @@ Login
 function sendData(data) {
   var XHR = new XMLHttpRequest();
 
+
   XHR.onreadystatechange = function() {
     if (this.status == 200) {      
       window.location = "authenticationOK.shtml";