.
BUG: The PB tool can't handle long titles
fgh
Member Posts: 8,948 ✭✭✭
(This is a PB version of the first bug in BUGS 5.1: Custom series, but worse.)
1) Open the PB tool in a not too wide panel and click Add Book.
2) Paste a book title that is longer than the visible part of the title field.
3) Try to add something to the end of the pasted title.
>> You can't, because you can't get there. Neither selection nor arrow keys will get you beyond the last visible letter.
4) Clear the field and start typing 'Xxxxxxxxxxxxxxxxxxxxxxxxxx'.
>> It's impossible to type in a title longer than the visible field.
Very annoying bug when you try to build one PB after another with exceptionally long titles, as I did the other day.
Workaround: use the info field to get the title right, and don't move it to the title field until you're sure it's what you want. Or use a full-screen panel. (Unfortunately I didn't think of the latter until today. At the time I wanted the Library open in the other half.)
Note: I've only checked the title field. All other fields, including the 'hidden' ones, need to be checked for the same bug.
Mac Pro (late 2013) OS 12.6.2
0
Comments
-
.
0 -
Good for you![:D]
Thanks for checking.
Mac Pro (late 2013) OS 12.6.2
0 -
I can reproduce this issue on Mac, not an issue on Windows. I will create a case for Development, and once this issue is fixed this thread will be updated.
0 -
fgh said:
Note: I've only checked the title field. All other fields, including the 'hidden' ones, need to be checked for the same bug.
I also checked the other fields. It's an issue only for the "Title", "Author" and "Copyright" fields (will add these to the case I created). The other 'hidden' fields such as "Abbreviated Title" do not have this issue.
0 -
Thanks.
Mac Pro (late 2013) OS 12.6.2
0 -
Angela Murashov said:
I can reproduce this issue on Mac, not an issue on Windows. I will create a case for Development, and once this issue is fixed this thread will be updated.
This will be fixed in 5.2a Beta 2.
0 -
Not the least bit fixed in RC 1.[:(]
Mac Pro (late 2013) OS 12.6.2
0 -
-
As my signature says, I'm still on 10.6.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
As my signature says, I'm still on 10.6.
I wonder what other bugs will potentially be frozen in 5.2a for users of 10.6 and 10.7 (and possibly Windows Vista)?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I wonder what other bugs will potentially be frozen in 5.2a for users of 10.6 and 10.7 (and possibly Windows Vista)?
Hundreds...
But what bugs me (pun intended) even more in this thread (and the other one with the same series of replies), is that if I make a bug report, they shouldn't claim that it's fixed if it isn't fixed on my operating system!
I shouldn't have to report this many bugs in the first place. I shouldn't have to bump them again and again to even have them recognized. I shouldn't have to wait years to have them fixed. And I definitely shouldn't have to rereport them again after they've been claimed to be fixed! Sometimes more than once.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
As my signature says, I'm still on 10.6.
We've since tested this in 10.6 and still can't reproduce the issue. Both pasted text and typed text scroll to the right, and you can navigate the box with the arrow keys or by drag-selecting. I'm not sure what's causing yours to work incorrectly. [:(]
0 -
Good news: it works in 5.2a, even though it didn't in RC1![:)]
Mac Pro (late 2013) OS 12.6.2
0
