4 Problems need fixing ASAP

1. Drop down lists in the property editor of events available, IList items etc. are not alphabetized. They should be. IT's a major pain in the ass to have to search and search through a list of possibly hundreds looking for one entry.

2. If you have a form that uses visual inheritence the property grid in event listing mode (C#) doesn't list event constructs that are in the parent form.

I.e.

In the parent:

protected void ChangeEvent(object sender, EventArgs e){//Do change stuff here}

If you inherit and then add a button to your inherited form, and go to events and choose click and click on the drop down arrow so that you can wire it to an existing handler, it will not show up. You have to create a new one with the same name, and then delete it. VS.net 2003's autocomplete for doing the same in code doesn't notice that the event already exists either and adds a new one unless you cancel it.

3. If you have an mdi child form, and you open a window and set the owner, then close the new window, the mdi-child form will not fire the activate or enter events.

(i.e.)

SomeForm theForm = new SomeForm();
theForm.Owner = this;
theForm.Show(); //(Also happens if you do a .ShowDialog, but I can live with that)

Once you've created a window like that, and then close it, the owner mdi child that gets the focus back doesn't get an Activate or Enter event. It should. It should also be intelligent enough to not give activate/enter events for windows that are spawned and owned from controls that are on the form. (i.e. a drop down control that drops down a form as it's drop down)

4. If you have an MDI child form open a form that it owns, and then open another form on that owned form and then close the 3rd window, the application will lose focus to whatever is next in the task manager order.

(i.e.)

SomeForm theForm = new SomeForm();
theForm.Owner = mdiChildForm;
theForm.Show() //Also happens with .ShowDialog();

On theForm: (a button click for example)

SomeForm2 theFormDialog2 = new SomeForm2();
theFormDialog2.ShowDialog(this);

Now if you close theFormDialog2, your application will lose focus.

Yes, the work around is to put in a this.Focus() right after the .ShowDialog() line, but that doesn't work if for instance you have hosted a WebControl or something based on MSHTML (like Tim's excellent control) because it creates a new window on theForm and causes the problem to happen when you close theForm.

This has been a bug in windows since V3.1 (that I know of, it's probably from before that) and desparately needs to be fixed. Now's your opertunity to fix it in the .net framework.

Bugs 3 and 4 are so severe that I think they should be scheduled for the next service pack of the .NET Framework because they effectively prevent you from doing serveral things that users absolutely demand (i.e. modeless dialogs that refresh lists that they are changing when they close and the window gets the focus back)

#1 is an anoyance that should be scheduled for a service pack of VS.net because it's gotta be no big deal to fix.

Answer this question

4 Problems need fixing ASAP

highlycaffeinated
Sorry I misinterpreted the question here. Yes, all these lists should be sorted in some meaningful order. Hopefully, those in charge are listening...
Silverblade2005
<quote>
Similarily, if you click on the lightening bolt in C#'s property browser on an item and go to an event that has params like sender, eventargs) and click on the drop down list, you'll notice that those are out of order too.
</quote>

That's the one that got fixed in VB.NET 2003, but I guess not in C# 2003! :~
Broomandan
Well, if we're talking about the same thing, it was fixed long before RC3. So perhaps I was thinking of something different In any case, the list of event-raising items is now alphabetized in the left-hand dropdown list in the Visual Basic .NET code editor.
Krishnaraj Varma
Ok, so it needs to be fixed in C#, the Datasources list needs to be fixed to be in Alpha order as well, same with DataMember.

Further, if you right click on a data adapter and choose generate dataset and choose existing and click on the drop down, it is in file name sorted order, which isn't necessarily the actual data set name and can get really confusing. It should be in the real data set name's order.
JoshLindenmuth
Ok, definately not talking about the same thing and it is still broken:

In the property editor, if you click on a DataSource drop down for say a DataGrid the sources listed are not in alpha order.

Similarily, if you click on the lightening bolt in C#'s property browser on an item and go to an event that has params like sender, eventargs) and click on the drop down list, you'll notice that those are out of order too.

End result: Madening on large forms when you're looking for one event handler out of hundreds.
Raatjetoe
FWIW, #1 is fixed in the 1.1 release, due out this week. At least, the list of event-raising objects is alphabetized, and the selection of the one of these is intelligent--selecting an event handler in the code editor window selects the corresponding object in the list.
HelpMePl0x
And here I thought that there wouldn't be much difference between RC3 and final so I haven't installed it yet! (Vs.net 2003 I mean).

Thanks for the tip!

How about the others
4 Problems need fixing ASAP

Answer this question