Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / September 2005

Tip: Looking for answers? Try searching our database.

Dialog editor problem with VS .NET 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jonathan Potter - 04 Sep 2005 07:56 GMT
Hi,

We have just recently switched to VS .NET 2003 from VS 6 and have found what
appears to be a problem with the dialog editor.

It appears that in some situations the editor incorrectly formats CONTROL
statements. This only seems to happen when the control has a Help ID, but it
does not always happen even then.

An example:

CONTROL  "",IDC_CFG_LISTER_ITEM_COLOUR_FG,"dopus.dropdown.button",
                   0x5,137,16,30,13,0,0,HIDC_CFG_LISTER_ITEM_COLOUR_FG

In this example, there is one too many parameters. The ",0,0" preceding the
HIDC_xxx should only be ",0", eg:

CONTROL  "",IDC_CFG_LISTER_ITEM_COLOUR_FG,"dopus.dropdown.button",
                   0x5,137,16,30,13,0,HIDC_CFG_LISTER_ITEM_COLOUR_FG

When this resource script is complied it produces the following errors:

Compiling resources...
.\language.rc(290) : error RC2111 : invalid control type
.\language.rc(290) : error RC2113 : END expected in dialog
.\language.rc(291) : error RC2135 : file not found:
.\language.rc(292) : error RC2135 : file not found:
.\language.rc(294) : error RC2108 : expected numerical dialog constant

Removing the erroneous ",0" fixes the problem, however the next time any
dialog in the resource file is edited, the ",0"s are all put back in.

This was not a problem under Visual Studio 6.

Is there a work-around to this problem other than having to turn off help
for all custom controls?

Thanks,
Jonathan Potter
GP Software
Rhett Gong [MSFT] - 05 Sep 2005 08:37 GMT
Hello Jonathan,
We are are currently researching on it. We will update you ASAP. Thanks for your patience!

Best regards,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn

This posting is provided "AS IS" with no warranties and confers no rights.
"Gary Chang[MSFT]" - 06 Sep 2005 04:09 GMT
Hi Jonathan,

>Is there a work-around to this problem other than having to
>turn off help for all custom controls?

I am afraid this is a known issue to the MFC7.1's dialog editor, the MFC
7.1 application resource file may get corrupted when HELP ID properties of
some controls(e.g. Tab Control of the Toolbox) in the dialog box is changed
to "True".

The problem here is the control format is different based on whether it is
a predefined class like button control etc. In these cased style and
exstyles are added at the end before helpid ...

CONTROL text, id, class, x, y, width, height [style, extended-style],
[helpid]

while predefined control:

CONTROL text, id, class, style, x, y, width, height [, extended-style],
[helpid]

We have already fixed this issue in the next version of the VS.NET
IDE(VS2005), but currently we don't have a workarounfd for VS2003, so at
the current stage, this issue would be a product limitation, if you need a
solution to work around this problem in VS2003 , it is better for you if
one of our PSS support engineers could work with you. This may need you
submit a support incident in Microsoft PSS (Product Support Service). As a
MSDN subscriber, you have two free support incidents.

By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.

For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-(800)936-5800 or by
choosing one of the options listed at
http://support.microsoft.com/d-efault.aspx?scid=fh;EN-US;Offe-rProPhone

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.