[Octave-bug-tracker] [bug #52853] Broken ui dialogs by ampersands inserted into button texts (KDE)

[Torsten]

URL:
  <http://savannah.gnu.org/bugs/?52853>

                 Summary: Broken ui dialogs by ampersands inserted into button
texts (KDE)
                 Project: GNU Octave
            Submitted by: ttl
            Submitted on: Wed 10 Jan 2018 07:34:25 AM CET
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: ttl
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

KDE inserts an amersand somewhere into the button texts of octaves ui dialogs
if the text does not already contain one. The text of the clicked button is
returned by the dialog for determining which button was clicked. Since the
returned text now differs from the text initially passed to the dialog
function, the analysis of the dialog's result fails.

I see two general approaches here:
0 An ampersand has to be inserted into the button texts each time a dialog is
called. This leads to exactly known strings for comparing the dialog's results
after a button was clicked. This would not really fixe the issue but requires
some sort of discipline by the programmer.
0 Any ampersand, which is directly followed by a digit or letter, is removed
from the clicked button text before it is returned by the dialog. This only
requires some attention by the programmer if the button texts passed to the
dialog are already containing ampersand for enabling access via <Alt>+<Char>.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52853>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/