I have a very simple method that looks for records with today’s date and shows them. I have two fields on the layout that are text areas, and whenever this method is triggered the two fields act like they are read only. I can’t get them to not do this. And once the fields are triggered is this state, it is impossible to get them out of it.
And an even stranger twist to this is if the user clicks on one of these two text areas so it has gained focus and then trigger the method, both fields will work correctly. Data can be entered without any problems. The fields don’t appear to be locked up.
I assume this is some kind of bug since it makes no sense why this would happen.
Here is my method:
There seems to be some difference between the Servoy User’s Guide and the Reference Guide.
On Page 389 of the Reference Guide under dateFormat it shows the example as:
var parsedDate = utils.dateFormat(datestring,'EEE, d MMM yyyy HH:mm:ss');
var formattedDateString = utils.dateFormat(dateobject,'EEE, d MMM yyyy HH:mm:ss');
However is the User’s Guide on page 223 and 231 it talks about using a pipe character.
Even with all of that, it still does not explain why only the text area fields suddenly shutdown like they are read only when they are not.
First the formatted data (like you did in your first posting) than the pipe and than the format.
When you do that, you add a data with a specific format and after the pipe you tell what format it is. That explains also the, what you called, difference in the manuals.
Even with all of that, it still does not explain why only the text area fields suddenly shutdown like they are read only when they are not.
Jim,
I tried your method and couldn’t reproduce the problem.
Can you try it in 3.1 as well?
Rob
I can confirm this behaviour on at least one of my apps (on 3.0.2): try putting the form on an empty tabpanel and load it, triggering readOnly true and false. Text Area fields don’t become editable.
If I do the same on the form itself (not loading it via a tabpanel), the trigger seems to work.