From: NiQingliang <niqingliang@insigma.com.cn>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: dependency gui problem
Date: Fri, 1 Jul 2011 16:56:42 +0800 [thread overview]
Message-ID: <1309510602.12519.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB6A1FA38BB68@shsmsx502.ccr.corp.intel.com>
according my understanding, the parseXX serials events is used for
"parsing recipes" window, and the cacheXX serials events is used for
"loading cache" window. The two windows is mutual-excluded.
thanks!!!
I will ask the bitbake developer, and will show you if I got the answer.
On Fri, 2011-07-01 at 16:44 +0800, Cui, Dexuan wrote:
> NiQingliang wrote:
> > I have changed that code section, and solved my problem, but I don't
> > know if it is the right way.
> >
> > if isinstance(event, bb.event.CacheLoadCompleted):
> > pbar.hide()
> > continue
> > .......
> > if isinstance(event, bb.event.ParseCompleted):
> > pbar.hide()
> > continue
> >
> > On Fri, 2011-07-01 at 10:45 +0800, NiQingliang wrote:
> >> I have looked the fiel depexp.py, and have some doubt:
> >>
> >> why in "ParseCompleted", the progress bar will hide, but in
> >> "CacheLoadCompleted", it will not???????
> I guess there should be a ParseCompleted event after the CacheLoadCompleted event(?), but on your host, the ParseCompleted doesn't happen somehow?
>
> I'm not sure your change is ok, because if it's a generic issue, why can't I reproduce the issue?
>
> >> I don't think these two events need different process.
> >>
> >> if isinstance(event, bb.event.CacheLoadCompleted):
> >> gtk.gdk.threads_enter()
> >> pbar.update(progress_total, progress_total)
> >> gtk.gdk.threads_leave()
> >> continue
> >> .......
> >> if isinstance(event, bb.event.ParseCompleted):
> >> pbar.hide() continue
> >>
>
> Thanks,
> -- Dexuan
--
倪庆亮
TEL: 13588371863
E-MAIL: niqingliang@insigma.com.cn
BLOG: http://niqingliang2003.wordpress.com
next prev parent reply other threads:[~2011-07-01 8:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 2:12 dependency gui problem NiQingliang
2011-06-30 2:18 ` Cui, Dexuan
2011-06-30 2:29 ` NiQingliang
2011-06-30 2:57 ` Cui, Dexuan
2011-06-30 3:18 ` NiQingliang
2011-06-30 23:55 ` Saul Wold
2011-07-01 1:34 ` NiQingliang
2011-07-01 1:47 ` NiQingliang
2011-07-01 2:45 ` NiQingliang
2011-07-01 3:13 ` NiQingliang
2011-07-01 3:22 ` NiQingliang
2011-07-01 8:46 ` Cui, Dexuan
2011-07-01 8:44 ` Cui, Dexuan
2011-07-01 8:56 ` NiQingliang [this message]
2011-07-05 15:34 ` Richard Purdie
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=1309510602.12519.3.camel@localhost.localdomain \
--to=niqingliang@insigma.com.cn \
--cc=dexuan.cui@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.