Re: [Interest] 80 column enforcement under Linux

2019-01-18 Thread Roland Hughes
You Da Man! Can't wait to try that this weekend. Thanks! On 1/18/19 4:56 PM, Furkan Üzümcü wrote: I’m not 100% sure if this is what you are looking for but astyle has a max-code-length option you can use. It does the job for me. http://astyle.sourceforge.net/astyle.html#_max-code-length Reg

Re: [Interest] 80 column enforcement under Linux

2019-01-18 Thread Furkan Üzümcü
I’m not 100% sure if this is what you are looking for but astyle has a max-code-length option you can use. It does the job for me. http://astyle.sourceforge.net/astyle.html#_max-code-length Regards, Furkan Üzümcü On Jan 18, 2019, 17:53 -0500, rol...@logikalsolutions.com, wrote: > Thanks for the

Re: [Interest] 80 column enforcement under Linux

2019-01-18 Thread roland
Thanks for the feedback gentleman. I was unaware Artistic Style is dead. Haven't found a line length thing in it anyway. I am using Artistic Style for formatting because the default QtCreator coding style and a project level .astylerc of this: # If you have astyle installed on your Linux

Re: [Interest] 80 column enforcement under Linux

2019-01-18 Thread Matthew Woehlke
On 18/01/2019 13.54, Michael Jackson wrote: > I would think that clang-format should be able to help you out with this. It > is part of the LLVM download. Ugh... clang-format... Be warned: clang-format's version of line length enforcement is *very* draconian. There is exactly one, and *only* one

Re: [Interest] 80 column enforcement under Linux

2019-01-18 Thread Michael Jackson
I would think that clang-format should be able to help you out with this. It is part of the LLVM download. -- Michael Jackson | Owner, President BlueQuartz Software [e] mike.jack...@bluequartz.net [w] www.bluequartz.net On 1/17/19, 11:32 AM, "interest-boun...@q

Re: [Interest] Destroy all queued events on QObject::disconnect?

2019-01-18 Thread Nikos Chantziaras
On 18/01/2019 11:06, Alexander Dyagilev wrote: The previous problem I recently wrote about was caused by me thinking that QObject::disconnect also destroys all queued events caused by this connection. This was obviously wrong. But, I still want Qt to behave so. Is there a way to achieve such b

Re: [Interest] Destroy all queued events on QObject::disconnect?

2019-01-18 Thread Thiago Macieira
On Friday, 18 January 2019 01:06:58 PST Alexander Dyagilev wrote: > Hello again, > > The previous problem I recently wrote about was caused by me thinking > that QObject::disconnect also destroys all queued events caused by this > connection. This was obviously wrong. > > But, I still want Qt to

Re: [Interest] Destroy all queued events on QObject::disconnect?

2019-01-18 Thread Jason H
> Sent: Friday, January 18, 2019 at 4:06 AM > From: "Alexander Dyagilev" > To: "interest@qt-project.org Interest" > Subject: [Interest] Destroy all queued events on QObject::disconnect? > > Hello again, > > The previous problem I recently wrote about was caused by me thinking > that QObject::

[Interest] Destroy all queued events on QObject::disconnect?

2019-01-18 Thread Alexander Dyagilev
Hello again, The previous problem I recently wrote about was caused by me thinking that QObject::disconnect also destroys all queued events caused by this connection. This was obviously wrong. But, I still want Qt to behave so. Is there a way to achieve such behavior? ___