Re: [Interest] Segmentation fault on exiting Qt event loop

2019-01-03 Thread Thiago Macieira
On Thursday, 3 January 2019 11:29:14 -02 Roland Hughes wrote: > Or you architect out everything which could be a security issue. There > is no command line or terminal. The few medical devices I know of > removed all support for inbound connections. The only method of > accessing them is to take th

Re: [Interest] Interest Digest, Vol 88, Issue 2

2019-01-03 Thread Roland Hughes
On 1/3/2019 4:00 AM, Konstantin Shegunov wrote: Yes QApplication destructor is invoked last..Does it makes sense to use deleteLater() in the widget destructors instead of existing delete if it could be cleaned up as part of qApp-quit()? Your example code clearly shows otherwise. You have a QOb

Re: [Interest] Segmentation fault on exiting Qt event loop

2019-01-03 Thread Roland Hughes
On 1/3/2019 4:00 AM, Thiago Macieira wrote: On 1/2/2019 4:00 AM, Thiago Macieira wrote: I understand you're working with 4.8. I don't care. That would by why there are hundreds, possibly thousands of companies all supporting their own fork of Qt and even more moving away from Qt. They choose

Re: [Interest] Interest Digest, Vol 88, Issue 2

2019-01-03 Thread Roland Hughes
+1 On 1/3/2019 4:00 AM, Jason H wrote: I often find that when generating a minimal example, I find the true nature of the bug. Sometimes, it's my fault, other times it's really a bug. While no one wants to actually do the exercise of creating the minimal test case (because it should "just wor

Re: [Interest] Segmentation fault on exiting Qt event loop

2019-01-03 Thread Roland Hughes
On 1/3/2019 12:22 AM, Konstantin Shegunov wrote: On Wed, Jan 2, 2019 at 5:55 PM Roland Hughes mailto:rol...@logikalsolutions.com>> wrote: By then, Qt has abandon them. Yeah, recently I had worked on a couple of projects for one such company (in aviation meteorology). They were "abandoned

Re: [Interest] Changes to Javascript runtime in 5.12

2019-01-03 Thread René Hansen
That's what I've resorted to for now, but yeah, as you say, it's definitely not as nice. Luckily, this time, there wasn't too many libs that needed rewriting. I haven't specifically seen any documentation regarding "this" and the global scope of JS libs, so I guess it might be my own fault for rel

Re: [Interest] Changes to Javascript runtime in 5.12

2019-01-03 Thread Ulf Hermann
Hi René, > In JS libs before 5.12, I've always used a closure approach to not > leak a bunch of private variables onto the global module object. This > results in a layout much like so: > > (function(lib) { > ... closed vars can be declared here ... > > lib.bar = function() { > return "b