Re: [Interest] QLIneEdit Bug still valid ?

2012-07-19 Thread André Somers
Op 17-7-2012 9:45, Tony Rietwyk schreef: Hi, A much easier solution to disconnecting the signals, is to set a flag before calling setText, then check that in the slot. Hope that helps, Tony Or use QObject::blockSignals(true) on the line edit before you set the text, and the same with

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-19 Thread Bo Thorsen
Den 17-07-2012 10:22, André Somers skrev: Op 17-7-2012 9:45, Tony Rietwyk schreef: Hi, A much easier solution to disconnecting the signals, is to set a flag before calling setText, then check that in the slot. Hope that helps, Tony Or use QObject::blockSignals(true) on the line

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-19 Thread André Somers
Op 19-7-2012 11:54, Bo Thorsen schreef: Den 17-07-2012 10:22, André Somers skrev: Op 17-7-2012 9:45, Tony Rietwyk schreef: Hi, A much easier solution to disconnecting the signals, is to set a flag before calling setText, then check that in the slot. Hope that helps, Tony Or use

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-19 Thread Tony Rietwyk
Andre said Sent: Tuesday, 17 July 2012 6:22 PM Op 17-7-2012 9:45, Tony Rietwyk schreef: Hi, A much easier solution to disconnecting the signals, is to set a flag before calling setText, then check that in the slot. Hope that helps, Tony Or use QObject::blockSignals(true) on

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-17 Thread Andre Somers
Op 17-7-2012 2:51, Constantin Makshin schreef: I can't say for sure, but most probably yes. You'd have to check to see if that does not block the emission of the signal then after the user edited the text. Does anyone know what the signal emission order _should_ be in case where a user edits

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-16 Thread Constantin Makshin
Functions you are interested in are (line numbers are taken from the code in the Git repository): src/gui/widgets/qlineedit.cpp, line 383 (QLineEdit::setText) src/gui/widgets/qlinecontrol_p.h, line 213 (QLineControl::setText) src/gui/widgets/qlinecontrol.cpp, line 676

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-16 Thread R. Reucher
On Monday 16 July 2012 09:14:31 Constantin Makshin wrote: Functions you are interested in are (line numbers are taken from the code in the Git repository): src/gui/widgets/qlineedit.cpp, line 383 (QLineEdit::setText) src/gui/widgets/qlinecontrol_p.h, line 213 (QLineControl::setText)

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-16 Thread Petric Frank
Hello René, so patching this location to pass false as additional third parameter should fix the issue, right ? regards Petric Am Dienstag, 17. Juli 2012, 01:06:43 schrieb Constantin Makshin: It works incorrectly only when the validator changes the text. The cause is

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-16 Thread Constantin Makshin
I can't say for sure, but most probably yes. On 07/17/2012 04:10 AM, Petric Frank wrote: Hello René, so patching this location to pass false as additional third parameter should fix the issue, right ? regards Petric Am Dienstag, 17. Juli 2012, 01:06:43 schrieb Constantin Makshin:

Re: [Interest] QLIneEdit Bug still valid ?

2012-07-15 Thread Petric Frank
Hello David, Am Sonntag, 15. Juli 2012, 15:36:19 schrieb David Boosalis: Hi Petric. SInce your changing the text in your code, as a work around why not disconnect the signal, change the text, then reconnect the signal Thats alike what i did currently. It is in my opinion a crude solution.