Why is QDialog.show() overriding my lineEdit text?

[tescrin]

Actually, until I messed with it a bit (later) and then combined that with your reply I didn't realize it was working like that. It does make sense I guess. I was thinking of any int value as merely a... means to deal with spinning and such more easily and not the... "head honcho" of the information. It made sense to me that the display value would be the real information and that anything that changed it would refer to *it* for accuracy.

In this case then it IS still OOP (I'm now agreeing with you) because it's not resetting a value, it's... dynamically acquiring it. Had I known that I bet I could've just overridden the double they use to just display with a single decimal digit eh? (If you come back around I'd really like to know actually.)

I guess this means I'll re-implement this in the real version so it's not working against itself. Thank you for the information!


p.s. As another question, did you learn all this from the source code or are you just intimately familiar or..? I ask because I was really digging through the source trying to figure out why setVisible was doing this. I got into some code I couldn't hardly recognize (something recursively calling d_func() to it's child members, and documentation on that is little as it seems that's a Qt programmer tool and not something the users should be using [from what I gathered].)

[wysota]

Had I known that I bet I could've just overridden the double they use to just display with a single decimal digit eh? (If you come back around I'd really like to know actually.)

What is displayed is totally controlled by what textFromValue() returns.

p.s. As another question, did you learn all this from the source code or are you just intimately familiar or..?

A lot of experience with how Qt works and how Qt developers think and a lot of time spent on reading the source code of Qt and implementing my own widgets (including spinboxes -- have a look at the link in my signature).