Windows application certain GUI elements do not work / display as expected
-
Hi, I have developed a windows application that is used on a bunch of PC's on our network. I distribute it with click-once deployment. On a couple of PC's certain GUI elements do not display / work as expected. For example, one of the forms contains a DataGridView, that has been set to not allow adding new rows. On one of the PC's mentioned however, the new row is visible, it does allow adding new rows. On another PC a form's title and a label on a StatusBar do not display at all. Has anyone else ever come across this phenomenon ? Where should I look to fix this ? Any help appreciated. Regards, Johan
My advice is free, and you may get what you paid for.
-
Hi, I have developed a windows application that is used on a bunch of PC's on our network. I distribute it with click-once deployment. On a couple of PC's certain GUI elements do not display / work as expected. For example, one of the forms contains a DataGridView, that has been set to not allow adding new rows. On one of the PC's mentioned however, the new row is visible, it does allow adding new rows. On another PC a form's title and a label on a StatusBar do not display at all. Has anyone else ever come across this phenomenon ? Where should I look to fix this ? Any help appreciated. Regards, Johan
My advice is free, and you may get what you paid for.
Is it "a datagridview" that displays said behaviour, or do all dgvs in the application show the extra row? If there's only one form in your app that's using the dgv, I'd try to write a small app to reproduce the behaviour to confirm it using the minimal code. If it is "one" control that is misbehaving, then the problem is probably in handling the control, not the control itself. I'd be checking the application for any constructs to swallow exceptions. Different ways of displaying a control, yes, that I would expect - since there have been multiple versions of the common controls, with flat controls introduced later.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
Is it "a datagridview" that displays said behaviour, or do all dgvs in the application show the extra row? If there's only one form in your app that's using the dgv, I'd try to write a small app to reproduce the behaviour to confirm it using the minimal code. If it is "one" control that is misbehaving, then the problem is probably in handling the control, not the control itself. I'd be checking the application for any constructs to swallow exceptions. Different ways of displaying a control, yes, that I would expect - since there have been multiple versions of the common controls, with flat controls introduced later.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
Hi Eddy,
Eddy Vluggen wrote:
...I'd try to write a small app to reproduce the behaviour to confirm it using the minimal code.
Thanks, I will try that
Eddy Vluggen wrote:
If it is "one" control that is misbehaving, then the problem is probably in handling the control, not the control itself. I'd be checking the application for any constructs to swallow exceptions.
I will check this. As the behavior is not happening on other PCs though, could it be possible that one PC (or .net framework) handles events and such in a different manner / order than another ?
Eddy Vluggen wrote:
Different ways of displaying a control, yes, that I would expect - since there have been multiple versions of the common controls, with flat controls introduced later.
Again, could that be dependent on the .net framework version ? Regards, Johan
My advice is free, and you may get what you paid for.
-
Hi Eddy,
Eddy Vluggen wrote:
...I'd try to write a small app to reproduce the behaviour to confirm it using the minimal code.
Thanks, I will try that
Eddy Vluggen wrote:
If it is "one" control that is misbehaving, then the problem is probably in handling the control, not the control itself. I'd be checking the application for any constructs to swallow exceptions.
I will check this. As the behavior is not happening on other PCs though, could it be possible that one PC (or .net framework) handles events and such in a different manner / order than another ?
Eddy Vluggen wrote:
Different ways of displaying a control, yes, that I would expect - since there have been multiple versions of the common controls, with flat controls introduced later.
Again, could that be dependent on the .net framework version ? Regards, Johan
My advice is free, and you may get what you paid for.
Johan Hakkesteegt wrote:
could it be possible that one PC (or .net framework) handles events and such in a different manner / order than another ?
Highly unlikely, as it would break a lot of applications.
Johan Hakkesteegt wrote:
could that be dependent on the .net framework version
There's a change in NET 4.5 for resizing[^], but haven't seen anything specific in the other "what's new" articles. Even if there's a manifest saying to use the "new" common controls, I would not expect very different behaviour - a different look, yes, but changing the behaviour breaks existing apps. There's a list on the versions here[^].
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]