.Net TRIVIA TIME!!!

  • Thread starter Thread starter lover
  • Start date Start date
L

lover

Q:
The visual aspects of .Net FX UI elements were designed by:
A) someone who is totally incompetent, lacks any 'quality of work'
ethic, and works under managers who operate the same way
B) a blind person
C) nobody - they haven't been _designed_ at all!

A:
I DON'T KNOW! I HONESTLY CAN'T TELL BY LOOKING AT THEM, AND MY CUSTOMERS
CAN'T EITHER. (I'm pretty sure it's either A, B, or C, though... =P)


*- datagridcolumnstyle with right-aligned text aligns the text WRONG -
portions of it are cut off/can't be seen.

*- multiple label controls with right-aligned text ... the text doesn't line
up!

IT'S A FRIGGING JOKE.

extremely disappointed.


-------------
PS - M$ fanbois/sufferers of Stockholm Syndrome, this is where you step up
to bat and say something clever like "Hey - you can get around this by using
owner draw! These tools are actually really powerful!" Then stroll on down
to your local tattoo parlor and get one on your forehead that says "I miss
the point entirely."
 
*- multiple label controls with right-aligned text ... the text doesn't
line
up!
Click to expand...

Does placing "\r\n" at the end of the text string(s) fix this?
IT'S A FRIGGING JOKE.
Click to expand...

I love humor.
PS - M$ fanbois/sufferers
Click to expand...

Is "fanboi" a cousin of Avril Levin's "sk8er boi?"
to bat and say something clever like "Hey - you can get around this by using
owner draw!
Yuck!

to your local tattoo parlor and get one on your forehead that says "I miss
the point entirely."
Click to expand...

That would make a cool tatoo.... but really a tatoo should contain a
picture, not just words. What does MSDN say about this?
 
Similar to their old VB products, I believe MS is purposely leaving a large
void to be filled by custom control vendors. MS has likely determined that
the quality of the supplied controls has little, if any, effect on Visual
Studio sales.

-Roger
 
The radio in my new car isn't all that good, but hey... it came with the
car.

Should I complain that it doesn't tune all the stations or pick up really
faint ones,
or reproduce symphony broadcasts accurately... I could... or I could buy an
aftermarket radio and throw away the one that came with the car.

Same thing works here. Economics 101

I'm sorry that you are having problems. Some of them may be simple coding
errors, but you didn't post your code, so we can't help.

There are already some good third-party controls that will help you out of
your bind. The third-party market is full of good products for demanding
consumers.

I hope this helps,
Next time, if you have a specific coding issue, I'll try my best to help
with that one too.

Even if I did miss the point.

--- Nick
 
good replies, all.

i am aware of the 3rd party controls market (although i am a bit poor to
participate in it as much as i would like), BUT, these flaws i'm talking
about -- at least in the case of the Label control -- are downright
INTEGRAL!!

I mean - what would you do if the default S.W.F.TextBox didn't ... oh ...
let's say ... _process text_ ....????

A) Buy/develop a user-made control and hope that your refusal to use the
built-in .Net FX version suffices as mute protest, guilting the dev team
into fixing these omissions out of sheer concern for 'Standards of Quality',
'Ease of Use', and 'Developer Well-Being'...

B) Use the broken controls, but only with tooltips attached that disclaim
"Blame it on M$!"

C) (my personal fave) Fire up the flamethrower and head for the
newsgroups, realizing that hoping for a fix is futile, but you may as well
try to publicly expose the incompetence of those responsible...
 
lover said:
good replies, all.

i am aware of the 3rd party controls market (although i am a bit poor to
participate in it as much as i would like), BUT, these flaws i'm talking
about -- at least in the case of the Label control -- are downright
INTEGRAL!!

I mean - what would you do if the default S.W.F.TextBox didn't ... oh ...
let's say ... _process text_ ....????

A) Buy/develop a user-made control and hope that your refusal to use the
built-in .Net FX version suffices as mute protest, guilting the dev team
into fixing these omissions out of sheer concern for 'Standards of Quality',
'Ease of Use', and 'Developer Well-Being'...

B) Use the broken controls, but only with tooltips attached that disclaim
"Blame it on M$!"

C) (my personal fave) Fire up the flamethrower and head for the
newsgroups, realizing that hoping for a fix is futile, but you may as well
try to publicly expose the incompetence of those responsible...
Click to expand...

Which results in you looking a little nuts and nothing being changed. Firing
flames will get you nothing, except perhaps ignored. Since you've calmed
down a bit(and just a bit) I figured I'd respond, although I imagine you are
already marked as "idiot" in alot of peoples minds.

Anyway, there are some obvious problems with a few controls. Although I've
never had your problem with labels(unless, of course, you don't have YOUR
labels lined up correctly on the form). That is frankly a reality in early
products. I've personaly never seen a great system provided grid(the
VB6\activex ones sorta sucked too).

Anyway, if you really want to effect change, start posting sample code(or
atleast steps to reproduce) showing your problems instead of spouting off
like a moron. It will get you further and will actually illustrate your
problem more accuratly. You should realize that there are people here who
are on the various alpha\beta teams and can provide feedback more directly
as well as people who can point out if YOU are making a mistake, but
behaviour like this isn't going to motivate anyone to help you.
 
Back
Top