as far as the window type is concerned, ALERT is like any DIALOG, you can pass the constant Movable dialog box to Open window to get similar effect.
http://doc.4d.com/4Dv16/4D/16.3/Window-Types-compatibility.300-3651740.en.html note that this kind of window is not available for Open form window. http://doc.4d.com/4Dv16/4D/16.3/Window-Types.300-3651761.en.html --- an app should really try to use the appropriate window type the way they are intended. basically, a window should be one of 3 classes; document, dialog or tool. a list form or a detail form or form that displays some settings is actually a "document". put another way, if a forms has a "save" button, it must be a document. modal windows should only be reserved for "dialogs", where the app stops and waits for the user to give directions. only a "tool" that accompanies a "document" should use a palette or toolbar window. (floating is different to modal, in that it never become the key window that accepts keyboard input. it is allowed to have a focusable text input but ideally it should mainly consist of clickable widgets) an app can have many UX problems such as the infamous "window order flipped" icon, or a modal window being displayed behind another modal window, when it uses a window type intended for dialogs or tools to display documents. what is special about ALERT, in my opinion, is that it is a UI command yet thread safe. http://doc.4d.com/4Dv16/4D/16.3/ALERT.301-3651314.en.html this is intentional, but again, because it is a developer tool. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
