[Libreoffice-qa] minutes of ESC call ...

[Robert Großkopf]

Hello *,
> 
> 	   2) ListBox has the wrong notion of "current value". Change it to
> 	   the right one incompatibly? Add a new "current *bound* value"
> 	   notion to stay compatible, but make the interesting thing
> 	   accessible in some way?
> 		+ has two lists of key/values pairs.
> 		+ with a one-to-one mapping between the two,
> 		+ values that are displayed; and another that is written.
> 		+ getCurrentValue - shouldn't return string displayed,
> 		  but the value
> 		+ on a date-field; don't get Mon/1st/Jan - but an abstract date.
> 		+ not so clear as all that (Norbert/Eike)
> 		+ value written to field, not exposed at all (Lionel)
> 		+ API is a special exception for this box
> 			+ been there for a while.
> 		+ keeping back-compat there is important (Eike)
> 			+ introduce a new method - getActualCurrentValue
> 			+ or incompatibly extend the existing interface
> 			+ can we put it in a property instead ?

Good idea. I have searched a long time for solving this problem. Only
possibility now is to show a unique key-field as a part of the "current
value", start a query and have a look for the foreign-key, which is
bounded to the table/query of the form.

To keep it back-compat, this "bounded" value should better be reached by
"current bound value".

Regards

Robert