diff options
| author | Stephan Bergmann <sbergman@redhat.com> | 2015-06-19 10:11:31 +0200 |
|---|---|---|
| committer | Ashod Nakashian <ashod.nakashian@collabora.co.uk> | 2016-02-06 11:12:22 -0500 |
| commit | 1b1669e430603ae01f593a5019dd6214cded4a33 (patch) | |
| tree | 342260e539361b7464f576c4b016378f17e72af7 /framework | |
| parent | 13d151309343ccd370c185bf69a7570ab218690b (diff) | |
Shall this produce a string representation of a number?
On the one hand, the code had apparently treated nIdx as a sal_Unicode character
value ever since its inception in e718950884fa2db240822e1711f301b39a70ad3e "new
querydesign." On the other hand, the preceding BROW_VIS_ROW case does produce
strings "0" and "1".
Change-Id: Ife6e98ba32146cc469b722fa4f013c12152b5505
(cherry picked from commit e46e8d19458fd64ff20b1013e5eeabd07e62379c)
Diffstat (limited to 'framework')
0 files changed, 0 insertions, 0 deletions