inconsistant behaviour

Scriptcase 7 Bugs
#1

I’m reporting this as a bug as I don’t get the picture of it. I have a field from a database and I set the radiobutton to label. Then I expect the field to be a label. Sometimes it does, sometimes it don’t and the field remains editable. If I disable the field, sometimes it does, sometimes it remains editable. I realy don’t get it. I can also set the field type to label. This seems to work. But it’s total unclear to me what the difference is, exept that if I set the fieldtype to label all other fields disappear and I can only edit it’s css properties.

Perhaps it has to do with being part of the (primary) key or not, but I see this as inconsistant behaviour.

#2

Re: inconsistant behaviour

Hello,

I have reported this issue to our bugs team for further testing.

regards,
Bernhard Bernsmann

#3

Hello,

This problem still persists?

#4

[QUOTE=John L. Santos;19442]Hello,

This problem still persists?[/QUOTE]

Yes. In fact there’s a combination of factors that decides behaviour and I still don’t have a good picture of it. There are several ways to make fields read-only and that’s very confusing. I useually stick to one option: unset the keyfield checkbox and set field property label to true.

#5

Hello,

I performed several tests locally and could not identify your problem.
Please try to be more specific, tell me more details about your problem, a step by step as is happening or even a picture.

#6

Allow me some time, I’ll make a movie from this one too.

#7

Ok, if you look at the movie you see that I do a lot of things to get my keyfield display only. What I want to achieve is that when I add a record that a part of the primary key is readonly and cannot be changed. It’s a very odd combination of settings to get this done. See http://www.scriptcase.eu/BugKeyReadonly.mp4

#8

Hello,

I was informed that this is a default behavior for primary keys.
All primary keys comes with a option “read-only” enabled in editing fields, and this can only be changed there.

#9

John, look again at the video. This field you mention does nothing. If that’s default behaviour then you can remove it. I’m talking about inconsistant working. This answer does not comply with my remarks and video.