Bug 360067 - Vertical alignment in a field shows opposed properties
Summary: Vertical alignment in a field shows opposed properties
Status: CLOSED NOT A BUG
Alias: None
Product: KEXI
Classification: Applications
Component: Reports and Printouts (show other bugs)
Version: 2.9.11
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-04 13:01 UTC by Albrecht Will
Modified: 2016-03-09 15:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
field lat_long_zoom (11.90 KB, image/png)
2016-03-04 13:02 UTC, Albrecht Will
Details
properties lat_long_zoom (22.75 KB, image/png)
2016-03-04 13:03 UTC, Albrecht Will
Details
report lat_long_zoom (16.79 KB, image/png)
2016-03-04 13:03 UTC, Albrecht Will
Details
different alignment in output, while the same vertical alignments in the propertiies (427.59 KB, application/pdf)
2016-03-05 08:26 UTC, Albrecht Will
Details
excample for space (7.72 KB, image/png)
2016-03-09 13:27 UTC, Albrecht Will
Details
Screenshot fro msqliteman (30.42 KB, image/png)
2016-03-09 14:21 UTC, Jarosław Staniek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Albrecht Will 2016-03-04 13:01:45 UTC
The problem appears in worling with report. It concerns only one field.

The vertical alignment of the field  (picture: Field lat_long_zoom.png) does not do, what i set.

I tried some different vertical alignments. The best that was "above". Then representation was nearly ok. If I try "center", then the fonts are up. 

The pict. "Properties latid_long_zoom.png" shows the properties, when I set "down".
The result is picture "report lat_long_zoom.png", where the fonts are on top.

Reproducible: Always
Comment 1 Albrecht Will 2016-03-04 13:02:34 UTC
Created attachment 97674 [details]
field lat_long_zoom
Comment 2 Albrecht Will 2016-03-04 13:03:22 UTC
Created attachment 97675 [details]
properties lat_long_zoom
Comment 3 Albrecht Will 2016-03-04 13:03:48 UTC
Created attachment 97676 [details]
report lat_long_zoom
Comment 4 Jarosław Staniek 2016-03-04 17:10:00 UTC
Changing Component to Reports - please use that precisely.
Comment 5 Albrecht Will 2016-03-05 08:24:48 UTC
"Changing Component to Reports - please use that precisely." -  I don't understand what you mean, sorry.

But I give you a new sreenshot to make the problem better understandable: pdf_alignment in headers.pdf

All the marked fields got the same vertikal alignment.
Comment 6 Albrecht Will 2016-03-05 08:26:12 UTC
Created attachment 97687 [details]
different alignment in output, while the same vertical alignments in the propertiies
Comment 7 Albrecht Will 2016-03-09 13:04:43 UTC
May be I found the reason for the displacement shown in the file "alignment in headers.pdf".
I searched in the affected fields. There were spaces at the end by insert & paste from fields in another table.
When I deleted them, the alignment was o.k.
Comment 8 Jarosław Staniek 2016-03-09 13:14:59 UTC
Interesting, thanks for sharing Albrecht. 
Do you mean really spaces or end-of-line characters? I have no idea how spaces may affect the vertical alignment. End-of-line character can, since if it's present there are two rows.
Comment 9 Albrecht Will 2016-03-09 13:27:03 UTC
Created attachment 97788 [details]
excample for space

I cannot decide, therefore I post the picture
Comment 10 Jarosław Staniek 2016-03-09 13:31:22 UTC
Maybe you can export the table to CSV and look at the file? Or send me a sample .kexi file (tell me what table it is).
Comment 11 Albrecht Will 2016-03-09 13:43:12 UTC
Am Mittwoch, 9. März 2016, 13:31:22 CET schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=360067
> 
> --- Comment #10 from Jarosław Staniek <staniek@kde.org> ---
> Maybe you can export the table to CSV and look at the file? Or send me a
> sample .kexi file (tell me what table it is).

appended is my current db. I changed field Stationierung_1 to the earlier 
content. Then the alignment is wrong.

(for the moment I cannot import from csv due to the "object"-issue)
Albrecht
Comment 12 Jarosław Staniek 2016-03-09 14:21:50 UTC
Created attachment 97791 [details]
Screenshot fro msqliteman

OK, not a bug but annoyance. Look e.g. using the sqliteman program: the value contains new-line at the end.
Comment 13 Jarosław Staniek 2016-03-09 15:19:59 UTC
It seems you ha​d no way to know the text is multi-line.

I think we don't display tool tips when moving mouse over the text then it cannot fit in the cell (vertically or horizontally). This is a thing to add. (We had this in Kexi 1.x)

Setting this bug as Invalid then.
Comment 14 Jarosław Staniek 2016-03-09 15:25:27 UTC
Added related wishes:
https://bugs.kde.org/show_bug.cgi?id=360311
https://bugs.kde.org/show_bug.cgi?id=360312