https://bugs.kde.org/show_bug.cgi?id=417210
--- Comment #8 from glyphi...@gmail.com ---
(In reply to Thomas Fischer from comment #7)
> New forced push to test repository/branch.
>
> > Tested. All appear resolved except (d). Current behavior on Plain
> > Text/Reference/Source Code dropdown menus is:
> >
> > - dropdown menu changes do trigger the discard dialog, but...
> >
> > - when the attached text field is blank, the dropdown menu's value is
> > "saved" whether the user discarded or saved
> That should be fixed. Issue was for blank values the reset of the widget was
> skipped, ignoring that the type (plain/reference) may have been changed.
>
> > - but I think the menu value only gets saved to the dialog window. Example:
> > I have 2 elements, both w/ a blank Abstract. The pulldown menu for both
> > elements' Abstracts are set to Plain Text. I edit element 1 and change its
> > Abstract's dropdown from Plain to Source. Whether I discard the change or
> > not, if I then re-open element 1, the Abstract dropdown is still set to
> > Source. If I view the 2nd element, its Abstract's dropdown also shows
> > Source.
> This is mostly a GUI glitch. I think I fixed that now.
>
> > - in contrast, when the Abstract field isn't blank, the pulldown menu always
> > says Plain Text -- if I change it to Source and click OK, then re-open, it
> > still says Plain.
> > - ... however, even if the field says Plain Text, TeX commands are
> > interpreted correctly in e.g. the Reference Preview. In effect, maybe Source
> > Code is really always set, but the dropdown always shows Plain Text.
> Actually, there are just two types in most cases:
> 1. plain text like title={Hello} which just shows the text inside the
> curly brackets. For deeper-nested curly brackets like title={{A}bc {D}ef}
> just the outer pair is hidden, and {A}bc {D}ef is shown
> 2. reference like title=Hello which refers to a string macro with key
> Hello
> Source is just showing how the value would look like in a BibTeX file,
> meaning for plain text it would include the outer curly brackets. However,
> it is no type on its own and only meant for inspection or manual editing. As
> you can easily shoot yourself into the foot by entering invalid BibTeX code,
> this mode should be used with care.
>
> Please test the latest code and let me know if that fixes all problems. I
> was trying to follow your explanation, but I cannot rule out that I missed
> something.
Everything looks good.
--
You are receiving this mail because:
You are watching all bug changes.
