No Check Mnemonics in C#???!!!

  • Thread starter Thread starter Julie
  • Start date Start date
In C++/MFC a WIN32 dialog resource is created and compiled by the resource
compiler and bound to the executable. The dialog preview is easy to
implement in this case. With .NET and the FCL a dialog is created at
execution time. While the designer can render a dialog it can't actually
function unless the code is executed. A much harder task.

Since a user might be manipulating the dialog creation code other than
strictly through the designer it is a difficult task to do things like
checking for duplicate mnemonics.

Thomas P. Skinner [MVP]
 
Thomas P. Skinner said:
In C++/MFC a WIN32 dialog resource is created and compiled by the resource
compiler and bound to the executable. The dialog preview is easy to
implement in this case. With .NET and the FCL a dialog is created at
execution time. While the designer can render a dialog it can't actually
function unless the code is executed. A much harder task.
Click to expand...

Checking mnemonics on a statically rendered dialog would be more than suitable
for 99% of the cases, I'm sure.

I'm not asking it to solve the world's energy problems, just tell me if there
are multiple dialog controls w/ the same &[letter] in the name --
 
That was my point. The VS object model extends a parsed view of sorts that you
can use in order to investigate all of the properties of controls and menu items
that
were built within the designer... I'm not sure if I'll have time to get around
to it, but
I'll think about adding this feature. A short term option might be to live with
an initial
run-time version that does the same thing using reflection... At least then you
catch
the problems during testing. I think I might have more time to write that than
the VS
plugin.


--
Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers

Julie said:
Thomas P. Skinner said:
In C++/MFC a WIN32 dialog resource is created and compiled by the resource
compiler and bound to the executable. The dialog preview is easy to
implement in this case. With .NET and the FCL a dialog is created at
execution time. While the designer can render a dialog it can't actually
function unless the code is executed. A much harder task.
Click to expand...

Checking mnemonics on a statically rendered dialog would be more than suitable
for 99% of the cases, I'm sure.

I'm not asking it to solve the world's energy problems, just tell me if there
are multiple dialog controls w/ the same &[letter] in the name --
Since a user might be manipulating the dialog creation code other than
strictly through the designer it is a difficult task to do things like
checking for duplicate mnemonics.

Thomas P. Skinner [MVP]
Click to expand...
Click to expand...
 
There is a "Review Access Keys" feature which is the same in my addin
below...
 
Back
Top