From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/3] ui/crumbs/hobprefs: re-enable reloading of data after prefs changes
Date: Mon, 19 Sep 2011 15:41:43 -0700 [thread overview]
Message-ID: <bdbd724e806c9ca69cc1508bac7ec0a2dce95543.1316471892.git.josh@linux.intel.com> (raw)
In-Reply-To: <cover.1316471892.git.josh@linux.intel.com>
In-Reply-To: <cover.1316471892.git.josh@linux.intel.com>
When disabling the toolchain w/ headers checkbox in an early commit I
accidentally disabled too much code. This re-enables adding the custom
response handler to the Preferences dialog which triggeres a reparse of
the metadata when appropriate preference changes are made.
Fixes [YOCTO #1479]
Signed-off-by: Joshua Lock <josh@linux.intel.com>
---
lib/bb/ui/crumbs/hobprefs.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/bb/ui/crumbs/hobprefs.py b/lib/bb/ui/crumbs/hobprefs.py
index 8d148cd..5dfb0e6 100644
--- a/lib/bb/ui/crumbs/hobprefs.py
+++ b/lib/bb/ui/crumbs/hobprefs.py
@@ -331,4 +331,4 @@ class HobPrefs(gtk.Dialog):
# headerscheck.set_active(self.build_toolchain_headers)
# headerscheck.connect("toggled", self.toggle_headers_cb)
# hbox.pack_start(headerscheck, expand=False, fill=False, padding=6)
- # self.connect("response", self.prefs_response_cb)
+ self.connect("response", self.prefs_response_cb)
--
1.7.6.2
next prev parent reply other threads:[~2011-09-19 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 22:41 [PATCH 0/3] Various hob fixes Joshua Lock
2011-09-19 22:41 ` Joshua Lock [this message]
2011-09-19 22:41 ` [PATCH 2/3] hob: fix build again when building packages only Joshua Lock
2011-09-19 22:41 ` [PATCH 3/3] hob: enable package only builds even if an image has been built Joshua Lock
2011-09-20 15:00 ` [PATCH 0/3] Various hob fixes Joshua Lock
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=bdbd724e806c9ca69cc1508bac7ec0a2dce95543.1316471892.git.josh@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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