Permanent readonly after search

On RC9 (MacOS 10.3.3) if you set a form (record view) to readonly and then perform a search (via method or not) all fields stay readonly. Buttons and tab panels don’t seem to be affected.

Ronnie

that is currently the way it works.. ReadOnly can only be converted back by setting it in a script..

Buttons can’t be readonly so they are unaffected by that property..
ReadOnly only applies to data entry fields..

.. ReadOnly can only be converted back by setting it in a script..

All my readonly settings are done from methods. It works fine (on and off) until I perform a find/search while true, then it doesn’t matter if readonly is true or false the fields are greyed-out.

Buttons can’t be readonly so they are unaffected by that property..

Buttons in a tab panel are affected by the main form’s readonly state.

Ronnie

First you say if it is readonly then fields are getting grayed out when doing search. And then you say it doesn’t matter if readonly it true or false.
I just made a quick mockup with a main form (recordview) and a tab in listview. And the main form i have a button that toggles the readonly.. I only see one small problem and that is when you are in readonly and then do a search the main tab does go into find mode (all fields are editable) But the tab still stays in readonly, I will look if i can fix that for 2.0 final.
But i can’t seem to get youre problem. So i need an example

Buttons in a tabpanel will be affected when the tabpanel is in a list or table view.. Because with a table or listview we set the complete panel to readonly. So all the fields are perfectly readable.. (main form in list or tableview does have the same affect)

Ok with more digging i fixed 2 bugs (>2.0RC10)

1> list and table views will be editable when doing find..

2> after find you couldn’t get out readonly mode anymore if find was started in readonly mode.

I hope that this wil fix youre problems.

2> after find you couldn’t get out readonly mode anymore if find was started in readonly mode.

That’s it. Glad it’s fixed for RC10. Thanks for being so quick about it. Now… when do we get RC10? :D

Ronnie

I think Johan meant it will be fixed after rc10 since rc10 is released… You can have it via autoupdate or the ‘check for new version’ under the help menu when you have your betanotification set to true…