• In Android and iPhone/iPad applications, windows are dequeued by a simple manual sweep.
• In Windows applications, windows are dequeued using the mouse.

Use conditions:
To scroll the internal windows in Android, the "Android Support Library V4" extension is required on the development computer, when generating the Android application. The setup procedure of this extension is available at the following address:
http://developer.android.com/tools/extras/support-library.html#Downloading

The principle for scrolling internal windows is straightforward

• An "Internal window" control is created in the editor. This "Internal window" control supports the swipe.
• Through programming, a list of internal windows is associated with the "Internal window" control.
• At runtime, the different internal windows of the list will be displayed when the user modifies the displayed element (via touch, mouse or specific buttons).

• An internal window is created. The fields in this window are associated with a data file or a query..
• An "Internal window" control is created in the editor. This "Internal window" control supports the swipe and it is associated with the data file or with the query of the internal window.
• At runtime, the data file (or the query) will be browsed and displayed in the internal window when the user modifies the displayed element (via touch, mouse or specific buttons).

Internal window path: Programmed path

1. Create the internal windows that will be displayed during the browse. These internal windows can accept parameters during their opening if necessary.
2. Create an "Internal window" field in your window: under the "Creación" pane, in the "Contenedores" group, click on "Ventana interna"..
3. Display the description window of "Internal window" control. In the "UI" tab:
   • Check "Allow the change of content by swipe".
   • Specify:
     • the cache size. The size of the cache corresponds to the number of internal windows that will be stored in memory (3 by default).
       The cache cannot be used to load windows in advance. Windows are actually loaded when IWListPosition is used or when a window goes before or after the current window.
       The smaller this number is, the smaller the memory consumption will be. On the contrary, the windows will be loaded more frequently.
     • scan orientation: vertical or horizontal.
     • the animation to perform during the swipe (if necessary). Click "Configure the animation".
       The "Style" tab of the control appears positioned on the "Control animation" element. You can select the desired animation and configure its parameters via the "Parameters" button.
       If the option "Defined by the project" is selected, the animation performed will be the one configured in the project options. For more details, see Control animations.
4. Through programming, build the list of internal windows that will be displayed in the "Internal window" control. To do so, use IWListAdd as many times as necessary.

• The windows must be added in the desired browse order.
• The parameters that must be passed to the added internal windows can be specified in IWListAdd.
• The same internal window can be added several times with different parameters.

Internal window browsing: automated browsing of a data file or query

1. Create the internal window that must display the different records. The controls of this internal window must be linked to the items of the file or query being read.
2. Create an "Internal window" field in your window: under the "Creación" pane, in the "Contenedores" group, click on "Ventana interna"..
3. Display the description window of "Internal window" control.
   • On the "General" tab, associate the internal window that was just created with the "Internal window" control.
   • In the "UI" tab:
     • Check "Allow the change of content by swipe".
   • Specify:
     • the cache size. The size of the cache corresponds to the number of internal windows that will be stored in memory (3 by default).
       The cache cannot be used to load windows in advance.
       The smaller this number is, the smaller the memory consumption will be. On the contrary, the windows will be loaded more frequently.
     • scan orientation: vertical or horizontal.
     • the animation to perform during the swipe (if necessary). Click "Configure the animation".
       The "Style" tab of the control appears positioned on the "Control animation" element. You can select the desired animation and configure its parameters via the "Parameters" button.
       If the option "Defined by the project" is selected, the animation performed will be the one configured in the project options. For more details, see Control animations.
     • Check (if necessary) "Position on the current record when opening the internal window". This option is used to automatically position the data of the internal window on the current record. This option is taken into account only if the change of content is performed by swipe and if the content corresponds to a data source (file, query, etc.).
   • In the "Content" tab:
     • Select the mode for filling the internal window: "File/Query".
     • Select the source used: file, query or integrated query.
     • Select the search item.

WLanguage functions for handling internal windows

• During an automatic iteration performed on a data file or on a query, ChangeSourceWindow, IWListAdd, IWListInsert, IWListDelete, IWListDeleteAll cannot be used.
• ChangeSourceWindow is used to modify the window currently displayed. This modification is saved in the list of internal windows to scroll.
• Only the controls found in the internal window currently displayed can be accessed programmatically. For example, the following code is used to change the caption of the button found in the internal window currently displayed:
  

  MyInternalWindowControl.BTN_Button = "New caption"

• The SwipeEnabled property is used to enable or disable the browse of internal windows with the finger. This allows you to temporarily disable the swipe in order to perform a specific operation.
• The VerticalSwipe property gets and sets the swipe gesture orientation.

Events run when scrolling the internal windows

• The internal windows found in the list and corresponding to the number specified in the cache size are loaded. The following events are run for each one:
  • Global declarations of the internal window
  • Initializing the controls found in the internal window
  • Initializing the internal window
  • After loading the internal window.
• When the user changes the contents of the internal window with a swipe gesture, the following events are run:
  • Selection by swipe.
  • Loading the next internal window (the events run are those of the above paragraph).
  • Unloading one of the internal windows (according to the cache size). In this case, the events "Before unloading the internal window" and "Closing" are run.

• The event "Selection by swipe" is not run if the internal window is changed programmatically.
• For a list of events associated with an internal window, see Events associated with an internal window.