When the user has an error, the error form is under all the opened forms and i can't see what is shown in it...

need to know what kind of message you have, please post a screenshot

This is an example, with one simple form, but i had this situation with other errors with many forms on the screen.

which version do you use?

can you move the login form slightly so that we can see the full error message (or get it in developer tool)?

The problem is the position of the error message not the content of the error itself that i created so i can show an error.... every error i have the error message is under all the other forms...is it clear ? This is probably 2.26.0

can we test somewhere?

GO to http://159.8.14.218/acutMobile Select [Accedi] and enter user: demo and password: 1 Ignore the first error and select [Bollettini da attività] At this point a new form is opened and then a new error is shown. This error is under the new form and not always i can read it....

Oops, I get no error on [Bollettini da attività]

Error messages use jQueryUI dialog while your form uses Prototype Window Class (soon deprecated)

Try using jQueryUIdialog instead of Prototype Window Class

See aw\app\progs\xxxServer.prg for more details

Be aware that your windows will look different unless you add some CSS

What do i need to change to have all form.backcolor to White similar to previous settings?

Now it appears like in this image

Which CSS do i need to change ?

change xxxServer.cjQueryUItheme and/or add some CSS in xxx.css

you can see all themes here: http://jqueryui.com/themeroller/ > 'Gallery'

FoxInCloud supports standard themes only

If i set lPrototypeAdd = .F. i have problems with the signature form.... It is shown but without the signature area and other form's control are not correctly filled with values.... like the execution of the form has been interrupted...

The textbox in the form are normally filled with some values...

good catch Michele, we are aware of some remaining PrototypeJS code so you should keep lPrototypeAdd = .T. for now.

we should complete the PrototypeJS deprecation upon version 2.27.

we've used it for so long (13 years) that we can hardly drop it…

But if i came back i still have the problem of the error message form.... it was the object of this message

http://159.8.14.218/acutMobile updated with jQueryUI dialogs but no error, can't test

You have to select the search button

still using Prototype Window Class

please set-up a complete test case, post screenshot and we'll see.

do you want my app set with lPrototypeAdd = .T. or .F. ?

the documentation in xxxServer is clear!

ljQueryUIdialog = .T.
&& {en} In 'classic' mode, use a jQueryUI dialog rather than a legacy 'Prototype Window Class' dialog.
&& {en} /!\ Version 3.x will deprecate Prototype Window Class; make sure to adapt your CSS in time

lPrototypeAdd = .T.

Ok. It's clear for me.... At the moment if i use lPrototypeAdd = .T. i have the problem i described at the begininnig of this message and it is the object of this message: when i have an error the form with the explanation of the error is shown under all the opened forms and not Always is possible to see its content. If i set lPrototypeAdd = .F. the problem with the error message is solved but i have problems with signature forms and you said me to wait for 2.27...

Now you asked me to see on my demo site my app, i suppose to see the first problem so i set lPrototypeAdd = .T. or not ?

please update with these 2 settings:

ljQueryUIdialog = .T.
lPrototypeAdd = .T.

With both values it works... even the signature...

of course, you may want to read more carefully the new version release notification emails and documentation in aw\app\*.*

No comment................

the question is… is it really worth spending time for writing documentation that everyone claims and no one reads?

Good question in deed. Maybe you should add this link to your F1 routine:
https://digitalcommons.utep.edu/cgi/viewcontent.cgi?article=1010&context=cs_papers

Thanks for the link Tore

We've bet that documentation in source code could be more appealing to developers… not sure we met success…

No matter what you choose, some people will prefer another solution. Personally I prefer a separate Help file with detailed info, in addition to shorter in-line comments.

yes, with your peculiarity of reading documentation

Documentation in code is more difficult to see and to read... This way it's too sparse... You have to read it in many different positions and it is easy to loose something... At the moment every time i receive an update i have to look some files for difference or new options.... prg, ini for example....and not Always i see difference in comments....I for example i receive an update... why do i need to open and read xxxserver.prg if i don't need to modify it ? or i think so.... In next updates i'll try... i make a post-it for this...but with a new beta every 2/3 days i'll spend my time reading...

Unless we forget something (and I know we were very cautious for PWC deprecation as it's a serious matter), each beta notification indicates the changes in this beta only, with due references, and the complete version changes matching the roadmap.

In 2.26 released 01/01/2018 we wrote:

New server properties
xxxServer.ljQueryUIdialog = .T. && use jQueryUI dialog instead of legacy 'Prototype Window Class'
xxxServer.lPrototypeAdd = .T. && load Prototype.js (http://prototypejs.org/) and dependent scripts: Scriptaculous, PrototypeWindowClass, event.simulate, etc.
As PrototypeJS will get deprecated, make sure to test these settings in your application! You may want to first set these properties in xxxTestServer.

If we had written these in a help file, no one would have had the idea to go and see what's new; reason why we put a lot of information in release notification emails.

If you keep these emails you can easily search them.

We spend a lot of time writing these information for you users (in several languages), please make sure to value this time!