<whine>Why is DotNet so difficult to work with?</whine>

  • Thread starter Thread starter Grahammer
  • Start date Start date
G

Grahammer

Sorry for the whining, but I'm getty VERY frustrated trying to do some very
simple jobs with DotNet and finding out that they are just impossible or
involve a LOT of work.

- Print a RichTextBox - five pages of code and it MIGHT work
- Limit a RichTextBox to 4000 characters? Nope, but you can have one that
holds 18446744073709551616 characters.
- Create a non-box shaped custom control - Can't use transparency so you
better know the shape you need BEFORE you bother with the control. Ever try
to define the region for snowflake shaped controls? Remember - each on is
different!!!
- Maintain the look of a form - You're expected to buffer, re-parse and
recalculate ALL of your data every time the PAINT method is called. A form
can't remember what it looks like.

I had enough trouble with VB6. Finally ended up taking part time courses and
they close the course before I can finish it!

I'm not a newbie programmer... I could program 6809 assembler in my sleep at
16 years old, I've worked in dBase III, Clipper, QBasic, z-80 assembly...

Why does M$ feel the need to convolute everything so much, then make the
help files even worse?
 
Grahammer said:
Sorry for the whining, but I'm getty VERY frustrated trying to do some very
simple jobs with DotNet and finding out that they are just impossible or
involve a LOT of work.

- Print a RichTextBox - five pages of code and it MIGHT work
Click to expand...

I haven't tried printing personally, but I doubt it's really that bad.
- Limit a RichTextBox to 4000 characters? Nope, but you can have one that
holds 18446744073709551616 characters.
Click to expand...

I believe you could handle the Validating event and cancel it if the
length is already 4000.
- Create a non-box shaped custom control - Can't use transparency so you
better know the shape you need BEFORE you bother with the control. Ever try
to define the region for snowflake shaped controls? Remember - each on is
different!!!
Click to expand...

No, I haven't tried to define the region for a snowflake-shaped
control. Do you believe this is a common requirement that MS should be
concerned with? I'd rather they focused on conventional, consistent
user interfaces.
- Maintain the look of a form - You're expected to buffer, re-parse and
recalculate ALL of your data every time the PAINT method is called. A form
can't remember what it looks like.
Click to expand...

That's standard GUI practice. Anything *should* be able to redraw
itself at any time.
 
- Create a non-box shaped custom control - Can't use transparency so you
better know the shape you need BEFORE you bother with the control. Ever try
to define the region for snowflake shaped controls? Remember - each on is
different!!!
Click to expand...

I,m sure I answered this one before. I expect since you are not going to
define a Region at runtime, that you are going to supply an Image. The steps
required to complete this task are outlined below.

Define a TransparentColor Property.
Store the Transparent Color in a Variable.

Define a GetRegion Method.
Create New Region (Rectangle of Image Size)
Process Image Pixels and any that match the TransparentColor variable
remove from the region.
Store the Region in a Region Variable.

At the OnImageChanged method resize your control to fit the image and run
the GetRegion and Invalidate Methods.

At the OnPaint method Set the Region of your control to the Region variable.

Seems pretty simple to me and not that much work.
 
Hey.

Just to add to Mick's post, try adding in the constructor
of an inherited control:
SetStyleControlStyles.SupportsTransparentBackColor, true)

This allows you to use transparent back colours.. Might
help..

Just a side note, I'd like to see you do all of the tasks
you mentioned in dBase III, Clipper, QBasic, z-80 assembly
I'm sure it would take far more code than in .net.

HTH
 
Grahammer said:
Sorry for the whining, but I'm getty VERY frustrated trying to do some very
simple jobs with DotNet and finding out that they are just impossible or
involve a LOT of work.

- Print a RichTextBox - five pages of code and it MIGHT work
- Limit a RichTextBox to 4000 characters? Nope, but you can have one that
holds 18446744073709551616 characters.
- Create a non-box shaped custom control - Can't use transparency so you
better know the shape you need BEFORE you bother with the control. Ever try
to define the region for snowflake shaped controls? Remember - each on is
different!!!
- Maintain the look of a form - You're expected to buffer, re-parse and
recalculate ALL of your data every time the PAINT method is called. A form
can't remember what it looks like.

I had enough trouble with VB6. Finally ended up taking part time courses and
they close the course before I can finish it!

I'm not a newbie programmer... I could program 6809 assembler in my sleep at
16 years old, I've worked in dBase III, Clipper, QBasic, z-80 assembly...

Why does M$ feel the need to convolute everything so much, then make the
help files even worse?
Click to expand...

You're a stupid ****.

Go back to playing with CD's and watching MTV in your mom's basement you
wanker.
 
Back
Top