Replies: 3 comments
-
That's a good question. I don't see a reason for it to segfault. Only because the fields other_1 and other_2 are often modified and read by the contest plugins. They serve different purposes based on the contest chosen. You could nest it in code that makes sure it's running the general logging plugin. something like:
But back to the original question.... I really don't know. |
Beta Was this translation helpful? Give feedback.
-
hmmmm. five lines deeper i use nick, too. no probs there. only if i settext to other_1 -- and i guess tabbing to name field (other_1) and focussing it. to me it makes no sense to xtract name/nickname and dont set it to other_1 (general logging). because of typing it manually from a to b ;) |
Beta Was this translation helpful? Give feedback.
-
Yeah it's not the nick variable. I inserted: print(f"{type(self.other_1)}")
self.other_1.setText("test") which resulted in:
So at the time self.other_1 is still a valid QLineEdit object, and I'm just passing in a plain vanilla string object. |
Beta Was this translation helpful? Give feedback.
-
I added this line (green):
But it creates a fine segmentation fault. Uhm... Why?
Beta Was this translation helpful? Give feedback.
All reactions