Issue 111349 - Text field value is not displayed when field is in table control
Summary: Text field value is not displayed when field is in table control
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO320m12
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2010-05-03 18:56 UTC by kjonca
Modified: 2017-05-20 10:47 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Example file (12.37 KB, application/vnd.sun.xml.base)
2010-05-03 18:57 UTC, kjonca
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kjonca 2010-05-03 18:56:46 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.
Comment 1 kjonca 2010-05-03 18:57:40 UTC
Created attachment 69268 [details]
Example file
Comment 2 drewjensen.inbox 2010-05-04 12:06:52 UTC
confirmed w/ OOo3.2, OOO320m_16 and DEV300m_77

set initial target
Comment 3 ocke.janssen 2010-07-07 08:20:52 UTC
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.
Comment 4 drewjensen.inbox 2010-07-07 08:55:24 UTC
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
Comment 5 ocke.janssen 2010-07-07 09:20:33 UTC
Yes. I see. Thanks.
Comment 6 Frank Schönheit 2010-07-07 11:01:54 UTC
"Never has AFAIK" sounds to me as if this is not really a 3.3?
Comment 7 drewjensen.inbox 2010-07-07 21:48:27 UTC
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)


2 - an unbound text control embedded, or control bound to a  in a table grid
control does not accept any input.

Comment 8 drewjensen.inbox 2010-07-07 21:50:07 UTC
sorry for the typo - should of been

2 - an unbound text control in a table grid control does not accept input.
Comment 9 drewjensen.inbox 2010-07-08 00:11:59 UTC
@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.
Comment 10 kjonca 2010-07-08 06:34:48 UTC
 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.
Comment 11 Frank Schönheit 2010-07-08 07:18:18 UTC
@atjensen: I agree that both issues are worth fixing. Just wanted to point out
that we are in *stopper* phase for 3.3 ...
Comment 12 ocke.janssen 2010-07-08 14:34:25 UTC
Yes, a 3.4 target seems to be the right one :-)
Comment 13 ocke.janssen 2010-07-20 11:00:04 UTC
@fs: Armin told me that a PrePaint is needed. He's guessing that you should
already have a duplicate issue.
Comment 14 Frank Schönheit 2010-09-03 16:29:42 UTC
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
Comment 15 Marcus 2017-05-20 10:47:54 UTC
Reset assigne to the default "".