OLD FORUM - Use new one: https://www.CaptainCasa.online/forum

Hi,

I have two issues with longtextfield.
The first is that expanding the text does not work if enabled=false. Usually, I use enabled=false to display read-only fields. If I can't use it in a longtextfield, I'll have to put some effort into making it look like the other enabled=false normal fields.

But I could cope with this, since I could use enabled=true; editable=false. The problem here is that editable=false does not have any effect. If you take the demo workplace and click through the longtext popup example, also where editable=false is set the text is still editable.

Do we have a bug here?

Thanks,

Björn

Hi,

no there is no bug.
The feature "view long text" is not part of the component yet.
But...: I agree that it makes sense. We will add it, next update (I believe...).

The setting of editable=false means, that you cannot edit the text through the field but you can only edit it through the popup. This is in synch with all other usages of EDITABLE. E.g. COMBOBOX is "editable=false" (by default): you cannot edit the text in the component, but you can update through the popup. Same with COMBOFIELD.

Regards, Björn

Hi,

are there any news here?

A longtextfield which can be made readonly but still have that longtextpopup-functionality would be great.

Regards,

Björn

Another small question regarding longtextfield: My Development tools complain that I don't provide an action listener on my longtextfield. Why? Can I turn this actionListener off? I think I don't need it in my case.

Thanks,

Björn

Hi,

...the opening of the field if enabled=false is part of next update. (There was no update this week due to logistic problems on Monday and Tuesday - so we decided to skip this week).

...actionListener: this only comes up if e.g. you define FLUSH to be true (or if your provide some DROPRECEIVE or POPUPMENU or ...). If you only refer to a String-property and set width, then there is no actionListener "enforced".

Regards, Björn

PS: in the Layout Editor, directly below the list of attribtues you can see the list of events; so you can see where the actionListener is coming from...