Apache OpenOffice (AOO) Bugzilla – Issue 111349
Text field value is not displayed when field is in table control
Last modified: 2017-05-20 10:47:54 UTC
I have table control based on table. Then I add text column to fill from dictionary (for example). Unfortunately, value is not displayed although set. 1. Open attached file 2. Run Form1 (by double clicking on it) 3. Double click on "Notes" field in first, and second record. 4. See macro associated with "Form1" and with field "Notes" in this form.
Created attachment 69268 [details] Example file
confirmed w/ OOo3.2, OOO320m_16 and DEV300m_77 set initial target
May be I didn't understand the issue. When I double click on the field a message box pop up with the value + Test That should be correct or. I tested windows and linux as well on a DEV300_m83.
I took the context of the issue to be: display a string in the column named 'Test' of the table grid control, setting the string with this line from the basic macro assigned - tbl.Test.text=tbl.getByName("Notes").text+" Test" The user is correct, that will not display a string in the column, of the grid control, on the form. Never has AFAIK
Yes. I see. Thanks.
"Never has AFAIK" sounds to me as if this is not really a 3.3?
Well, I suppose a real target would first require a decision as to what (which) is the error this issue will deal with: 1 - setting the text property of a data bound control, embedded in a table grid control does not update the UI (and therefore does not update the bound field, setting the dataforms dirty flag) or 2 - an unbound text control embedded, or control bound to a in a table grid control does not accept any input.
sorry for the typo - should of been 2 - an unbound text control in a table grid control does not accept input.
@kjonca - Hello. looking at the 2 questions from the last update - if you are planning on binding the column in the the grid to a table field then all you need do is change your basic code, using updateString on the bound field. A work around for, IMO, a defect but it does everything you need. So I would recommend the issue be opened, but set to ooLater, which you can take to be..way later :) On the other hand if you actually want to use the column in the Form UI only, no storage, then I don't think there is a way. So the question becomes, is that something that should be supported. I think so.
I needed this functionality to print dictionary description for column (although this is not the case in example attachment). So this column rather won't be bind to a table field (in the database), only UI. BTW. A workaround for this is use combo list bound to table field.
@atjensen: I agree that both issues are worth fixing. Just wanted to point out that we are in *stopper* phase for 3.3 ...
Yes, a 3.4 target seems to be the right one :-)
@fs: Armin told me that a PrePaint is needed. He's guessing that you should already have a duplicate issue.
oj's previous comment doesn't belong into this issue, /me thinks, this problem here has nothing to do with the drawing layer ... Targeting to Later
Reset assigne to the default "issues@openoffice.apache.org".