Hi
Sorry if I do not fully understand this. The proposal is that an ErrorAlert
will be created which must be dismissed by its OK button. Is there any
possibility that a large number of errors can be created, each needing to be
manually dismissed?
> We can improve the helpfulness of this messag
On 14 October 2010 08:50, Mukul Gupta wrote:
> Team,
>
> Wish to have your feedback on the design aspect of the ticket 2063 (Sugar
> should bring up an alert when an unhandled Python exception occurs) - please
> find the git diff attached below. This is an attempt to display an alert
> when an un
David,
Thank you. Appreciate your motivation and feedback.
Regards,
Mukul Gupta
On Thu, Oct 14, 2010 at 1:41 AM, Mukul Gupta wrote:
> Please find my explanations on the code added as comments.
>
> diff --git a/journalactivity.py b/journalactivity.py
> index 44cc018..36a2e2e 100644
> --- a/jo
Please find my explanations on the code added as comments.
diff --git a/journalactivity.py b/journalactivity.py
index 44cc018..36a2e2e 100644
--- a/journalactivity.py
+++ b/journalactivity.py
@@ -358,8 +358,20 @@ class JournalActivity(Window):
self.show_main_view()
self.search_gr
On Wed, Oct 13, 2010 at 2:50 PM, Mukul Gupta wrote:
> Team,
>
> Wish to have your feedback on the design aspect of the ticket 2063 (Sugar
> should bring up an alert when an unhandled Python exception occurs) - please
> find the git diff attached below. This is an attempt to display an alert
> when
Team,
Wish to have your feedback on the design aspect of the ticket 2063 (Sugar
should bring up an alert when an unhandled Python exception occurs) - please
find the git diff attached below. This is an attempt to display an alert
when an unhandled Python exception occurs in the journal. Unfortunat
Team,
I had a discussion with Aleksey this morning at IRC on the feedback
recommended yesterday. Thank you Daniel and Tomeu. Appreciate your ideas and
pointers.
We brainstormed on how the implementation of this functionality could be
done, and found that whenever any uncaught exception is raised,
Tomeu and Daniel,
On Mon, Oct 11, 2010 at 1:50 PM, Tomeu Vizoso wrote:
> On Mon, Oct 11, 2010 at 09:57, Daniel Drake wrote:
> > On 10 October 2010 20:14, Mukul Gupta wrote:
> >> With reference to SL Bug # 2063 which deals with bringing some kind of
> >> notification alert whenever an unhandle
On Mon, Oct 11, 2010 at 09:57, Daniel Drake wrote:
> On 10 October 2010 20:14, Mukul Gupta wrote:
>> With reference to SL Bug # 2063 which deals with bringing some kind of
>> notification alert whenever an unhandled python exception occurs, I had a
>> few doubts. There are two approaches that I c
On 10 October 2010 20:14, Mukul Gupta wrote:
> With reference to SL Bug # 2063 which deals with bringing some kind of
> notification alert whenever an unhandled python exception occurs, I had a
> few doubts. There are two approaches that I can think of.
Neither of these sounds sensible.
What's w
With reference to SL Bug # 2063 which deals with bringing some kind of
notification alert whenever an unhandled python exception occurs, I had a
few doubts. There are two approaches that I can think of.
1. Any unhandled python exception is always logged. Thus, if we can check
whenever logging.ERRO
11 matches
Mail list logo