Summary: | Vertical alignment in a field shows opposed properties | ||
---|---|---|---|
Product: | [Applications] KEXI | Reporter: | Albrecht Will <albrecht.will> |
Component: | Reports and Printouts | Assignee: | Kexi Bugs <kexi-bugs> |
Status: | CLOSED NOT A BUG | ||
Severity: | normal | CC: | adam, inksi, staniek |
Priority: | NOR | ||
Version: | 2.9.11 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
field lat_long_zoom
properties lat_long_zoom report lat_long_zoom different alignment in output, while the same vertical alignments in the propertiies excample for space Screenshot fro msqliteman |
Description
Albrecht Will
2016-03-04 13:01:45 UTC
Created attachment 97674 [details]
field lat_long_zoom
Created attachment 97675 [details]
properties lat_long_zoom
Created attachment 97676 [details]
report lat_long_zoom
Changing Component to Reports - please use that precisely. "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. Created attachment 97687 [details]
different alignment in output, while the same vertical alignments in the propertiies
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. 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. Created attachment 97788 [details]
excample for space
I cannot decide, therefore I post the picture
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). 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
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.
It seems you had 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. Added related wishes: https://bugs.kde.org/show_bug.cgi?id=360311 https://bugs.kde.org/show_bug.cgi?id=360312 |