R
Rob R. Ainscough
So I can assume you have seen the issue with slow .NET control/form paints?
Commenting on my user base without knowing what user base is certainly
looses some credibility on your part. My user base is probably at the level
of McDonalds operator, a button for each Reg Coke, Med Coke, Large Coke --
in fact my user base doesn't know that buttons are single click not double
click and they often double click everything. To provide a "please wait
message" while a form loads doesn't sit well with them and most of my
clients/users are running old out dated hardware (PIII's with 128MB).
I don't live in a glass bubble as some of you obviously do. Slow screen/GUI
responses have a very negative impact and can and does move potential
customers to look at other competitors (and this is NOT even a web based
app). My clients don't care what I used to development the tool they plan
to buy & use -- they just want the tool to be fast.
If you want to be constructive and provide specific links or samples on how
to speed up a .NET WinForm, please do.
Rob.
Commenting on my user base without knowing what user base is certainly
looses some credibility on your part. My user base is probably at the level
of McDonalds operator, a button for each Reg Coke, Med Coke, Large Coke --
in fact my user base doesn't know that buttons are single click not double
click and they often double click everything. To provide a "please wait
message" while a form loads doesn't sit well with them and most of my
clients/users are running old out dated hardware (PIII's with 128MB).
I don't live in a glass bubble as some of you obviously do. Slow screen/GUI
responses have a very negative impact and can and does move potential
customers to look at other competitors (and this is NOT even a web based
app). My clients don't care what I used to development the tool they plan
to buy & use -- they just want the tool to be fast.
If you want to be constructive and provide specific links or samples on how
to speed up a .NET WinForm, please do.
Rob.