mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter Kümmel" <syntheticpp@gmx.net>
To: linux-kernel@vger.kernel.org
Cc: "Peter Kümmel" <syntheticpp@gmx.net>
Subject: [PATCH] xconfig: Don't move focus when clicking on the search button
Date: Thu,  6 Nov 2014 13:03:01 +0100	[thread overview]
Message-ID: <1415275383-15301-2-git-send-email-syntheticpp@gmx.net> (raw)
In-Reply-To: <1415275383-15301-1-git-send-email-syntheticpp@gmx.net>

When the search button is clicked the focus moves to the
search button. Changing the search text after such a button
press requires an additional click into the edit field.
With this patch this click is not necessary anymore because
the button is configured to not accept the focus.

Signed-off-by: Peter Kümmel <syntheticpp@gmx.net>
---
 scripts/kconfig/qconf.cc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/kconfig/qconf.cc b/scripts/kconfig/qconf.cc
index 9d3b04b..750a5ff 100644
--- a/scripts/kconfig/qconf.cc
+++ b/scripts/kconfig/qconf.cc
@@ -1198,6 +1198,7 @@ ConfigSearchWindow::ConfigSearchWindow(ConfigMainWindow* parent, const char *nam
 	layout2->addWidget(editField);
 	searchButton = new QPushButton(_("Search"), this);
 	searchButton->setAutoDefault(FALSE);
+	searchButton->setFocusPolicy(Qt::NoFocus);
 	connect(searchButton, SIGNAL(clicked()), SLOT(search()));
 	layout2->addWidget(searchButton);
 	layout1->addLayout(layout2);
-- 
1.9.1


  reply	other threads:[~2014-11-06 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 12:03 [PATCH] kconfig: Fix warning "‘jump’ may be used uninitialized" Peter Kümmel
2014-11-06 12:03 ` Peter Kümmel [this message]
2014-11-06 12:03 ` [PATCH] xconfig: Set configuration strings on focus lost Peter Kümmel
2014-11-06 12:03 ` [PATCH] xconfig: Set keyboard focus to line edit whenever the search dialog opens Peter Kümmel
2014-11-06 12:36 ` [PATCH] kconfig: Fix warning "‘jump’ may be used uninitialized" Paul Bolle
2014-11-06 14:13   ` Aw: " Peter Kuemmel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1415275383-15301-2-git-send-email-syntheticpp@gmx.net \
    --to=syntheticpp@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®