Show error messages in log view and pop up if critical

[dpizetta]

A experienced many problems with unknown characters on sentence view, but when you add, remove ou update the sentence just was shown on terminal if opened, and the sentence was not included.

I think that problems like that in add, remove and update, even import, save and so forth, need to be exhibited to the user.

[tiagocampo]

GOOGLE TRANSlATOR: Um experimentado muitos problemas com caracteres desconhecidos na visão sentença, mas quando você adicionar, remover OU atualização a sentença só foi mostrado no terminal se abriu, ea sentença não foi incluído.

Acho que problemas como esse em adicionar, remover e atualizar, até mesmo a importação, salvar e assim por diante, precisa ser exibido para o usuário.

The second sentence is OK, but the first, I cant decipher. Sorry

On Mon, Jun 16, 2014 at 5:09 PM, Daniel Pizetta notifications@github.com wrote:

A experienced many problems with unknown characters on sentence view, but when you add, remove ou update the sentence just was shown on terminal if opened, and the sentence was not included.

I think that problems like that in add, remove and update, even import, save and so forth, need to be exhibited to the user.

— Reply to this email directly or view it on GitHub https://github.com/zericardo182/sci-corpus/issues/71.

---

Tiago de Campos

[dpizetta]

Sorry, I'm not so good today, I've just seen the problem and put it here.

I experienced many problems with unknown characters on sentence view - like º (degree). When you add, remove or update the sentence, if it has an error this error was just shown on terminal, not in log view or pop up message, and after that the message is not included on db, because of the error.

The user has no feedback.

[tiagocampo]

Yes, this has been around since the beginning of the program. I remember that we couldn't show any message because there weren't a way to send a signal from the container to the main_window. Something like that.

On Mon, Jun 16, 2014 at 5:51 PM, Daniel Pizetta notifications@github.com wrote:

Sorry, I'm not so good today, I've just seen the problem and put it here.

I experienced many problems with unknown characters on sentence view - like º (degree). When you add, remove or update the sentence, if it has an error this error was just shown on terminal, not in log view or pop up message, and after that the message is not included on db, because of the error.

The user has no feedback.

— Reply to this email directly or view it on GitHub https://github.com/zericardo182/sci-corpus/issues/71#issuecomment-46235328 .

---

Tiago de Campos

[dpizetta]

Yes, but if we put the try block on sci_corpus_main when we call the function of container we can get some types of errors. Maybe we need to put some signal on container too.

On Mon, Jun 16, 2014 at 5:56 PM, tiagocampo notifications@github.com wrote:

Yes, this has been around since the beginning of the program. I remember that we couldn't show any message because there weren't a way to send a signal from the container to the main_window. Something like that.

On Mon, Jun 16, 2014 at 5:51 PM, Daniel Pizetta notifications@github.com

wrote:

Sorry, I'm not so good today, I've just seen the problem and put it here.

I experienced many problems with unknown characters on sentence view - like º (degree). When you add, remove or update the sentence, if it has an error this error was just shown on terminal, not in log view or pop up message, and after that the message is not included on db, because of the error.

The user has no feedback.

Reply to this email directly or view it on GitHub < https://github.com/zericardo182/sci-corpus/issues/71#issuecomment-46235328>

.

---

Tiago de Campos

Reply to this email directly or view it on GitHub https://github.com/zericardo182/sci-corpus/issues/71#issuecomment-46236192 .

[dpizetta]

I think that something like this is also good, for uncaught exceptions, that we dont have control in the future:

http://stackoverflow.com/questions/12508752/log-syntax-errors-and-uncaught-exceptions-for-a-python-subprocess-and-print-them

On Mon, Jun 16, 2014 at 6:14 PM, Daniel Pizetta daniel.pizetta@usp.br wrote:

Yes, but if we put the try block on sci_corpus_main when we call the function of container we can get some types of errors. Maybe we need to put some signal on container too.

On Mon, Jun 16, 2014 at 5:56 PM, tiagocampo notifications@github.com wrote:

Yes, this has been around since the beginning of the program. I remember that we couldn't show any message because there weren't a way to send a signal from the container to the main_window. Something like that.

On Mon, Jun 16, 2014 at 5:51 PM, Daniel Pizetta notifications@github.com

wrote:

Sorry, I'm not so good today, I've just seen the problem and put it here.

I experienced many problems with unknown characters on sentence view - like º (degree). When you add, remove or update the sentence, if it has an error this error was just shown on terminal, not in log view or pop up message, and after that the message is not included on db, because of the error.

The user has no feedback.

Reply to this email directly or view it on GitHub < https://github.com/zericardo182/sci-corpus/issues/71#issuecomment-46235328>

.

---

Tiago de Campos

Reply to this email directly or view it on GitHub https://github.com/zericardo182/sci-corpus/issues/71#issuecomment-46236192 .