Cursor not visible

[wysota]

While user enters the date, this validate method tests & corrects user input. But when he presses ENTER or TAB key, even if the date is a valid one, Business Logic may decide it's not a valid date ( i.e a day before today for a payment )

Not really. You can fetch the "possible valid" state from the logic and cache it somehow and use an intermediate state when you suspect the input to be incomplete.

And here becomes the problem. I cannot assume a call to Business Logic EVERY time a date is Acceptable, because that call could be very time-expensive.

I think I just answered that as well

OK, I accept perhaps is an "strange approach", but is working. And it's quick and efficient. Sometimes we must break "programming-guidelines" to obtain a better performance...

What happens if you just keep pressing tab (possibly inside an invalid field)?

And I repeat that the problem is not in the validation style but in the fact that everything is working OK, but the cursor dissapears when between the focusout and the focusin I show a message on an external StatusBar. But when i show a modal message, all is running OK

As I said in the previous post, you're manipulating with the focus too much. Remember that focusOut causes a focusIn elsewhere and then you force the focus back which again causes a focusOut and focusIn. What does your focusOutEvent look like anyway?

But you will agree with me that I will have the same problem. When I emit the signal, I receive a "invalid" response and move the focus, "I'm fuc***"

Sure, but this is easily overcomable. Check if calling selectAll() on the line edit helps.

I agree with you that StatusBar is stealing the focus, But I don't understand why...

I'm calling a method like this in the focusout event ( pseudo-code )

I think you should just reject the focus out event.

Yes, a QlineEdit. But not a QComboBox, or QRadioButton... And I do need to control that kind of widgets too

Maybe you should just use a QDataWidgetMapper? Most of the things you require are already there, I think... Anyway, you can repair the tab order with a simple function, as I mentioned before.

[jpujolf]

As I said in the previous post, you're manipulating with the focus too much. Remember that focusOut causes a focusIn elsewhere and then you force the focus back which again causes a focusOut and focusIn. What does your focusOutEvent look like anyway?

Just calls my form's FieldExit method...

Sure, but this is easily overcomable. Check if calling selectAll() on the line edit helps.

I'm doing it... And it doesn't helps me...

I think you should just reject the focus out event.

You mean calling QEvent::ignore () ? Is the only test I've not done...

Maybe you should just use a QDataWidgetMapper? Most of the things you require are already there, I think...

QDataWidgetMapper could be a solution if I was using it against a model. Is not the case...

Anyway, thanks for wasting your time answering me. You helped me a lot !!

[wysota]

Just calls my form's FieldExit method...

I don't think that's enough.

I'm doing it... And it doesn't helps me...

Then probably the widget doesn't have focus after all...

You mean calling QEvent::ignore () ? Is the only test I've not done...

Yes.

QDataWidgetMapper could be a solution if I was using it against a model. Is not the case...

So it's only a matter of implementing a model It has all you need including the validation inside QAbstractItemModel::setData()

Anyway, thanks for wasting your time answering me. You helped me a lot !!

If I felt like wasting my time, I wouldn't be here.