I have used John Snyders 19.2 IG Cookbook app to test the "Read Only" property after experiencing an issue in one of our own applications. The application I used was titled "Basic Editable IG on Emp", and the 2 columns I used to re-create the scenario in our own app were the SAL column and COMM column. I just wanted to prevent edit in the COMM column if the SAL was < 3000. When I first query the grid, the COMM column was Read Only for all employees with SAL < 3000. I then updated the SAL column for an employee having SAL >= 3000 to 500. I do not expect this action alone to cause the COMM to become "Read Only", since JavaScript can be utilized to do that. When I make this particular change, which will then result in a "true" condition, the COMM column is correctly set to Read Only after I click the grid Save button. However, when I then change the SAL column from 500 to 4000, click Save, the COMM field does not update the column to editable.When I activate the "Debug" from the APEX Developer Toolbar, and then "View Debug", I can see that my "Read Only" condition was being re-evaluated, with the result of "false". In order to get the "Read Only" property to reflect the "false" condition, I have to click the grids "Go" button. So the issue I am reporting, is that the condition of "true" properly locks down the column, while the condition of "false" does not set the column COMM to be editable after clicking grid "Save" button. Both condition tests were tested with a sequence order of query/update/save. If I reload the page or click grids "Go" button the "false" condition shows the COMM as editable.
