Thanks Kalle(s)
Sounds like lots of fun, but now the Console.log to QtCreator thing
has been fixed, best left alone ...
Ciao
Chris
Zitat von "Kalle Vahlman" :
2013/12/17 Kalle Jokiniemi :
Hi,
On Mon, 2013-12-16 at 22:29 +0200, Kalle Vahlman wrote:
2013/12/16 :
> Hi All
>
> As reported
2013/12/17 Kalle Jokiniemi :
> Hi,
>
> On Mon, 2013-12-16 at 22:29 +0200, Kalle Vahlman wrote:
>> 2013/12/16 :
>> > Hi All
>> >
>> > As reported in a previous thread, the latest SDK release does not spool
>> > console.log output to the QtCreator application output. journalctl has
>> > been
>> >
Hi,
On Mon, 2013-12-16 at 22:29 +0200, Kalle Vahlman wrote:
> 2013/12/16 :
> > Hi All
> >
> > As reported in a previous thread, the latest SDK release does not spool
> > console.log output to the QtCreator application output. journalctl has been
> > suggested as a workaround.
> >
> > Having expe
Hi Kalle
I was playing around with a SilicaListView with a 100 items, with
console.log output on Component.onCompletion and onDestruction, and
was scrolling up and down (in the Emulator).
What we really need is console.log back in the QtCreator application
output where it belongs. This sh
2013/12/16 :
> Hi All
>
> As reported in a previous thread, the latest SDK release does not spool
> console.log output to the QtCreator application output. journalctl has been
> suggested as a workaround.
>
> Having experimented with journalctl, Is it possible that console.log output
> to journal
Hi All
As reported in a previous thread, the latest SDK release does not
spool console.log output to the QtCreator application output.
journalctl has been suggested as a workaround.
Having experimented with journalctl, Is it possible that console.log
output to journalctl either gets lost
