Hello All,

I have MFC-based application featuring:
1) Flow of "Screens" where screens are implemented as a MFC's
CDialog-inherited classes loading PNG or BMP images.
2) Dialog's child controls also loads PNG or BMP images.

What is the best practice to handle the same functionality in .NET/C#?


Thanks,

Re: Best practices for GUI of what called in MFC custom controls by PvdG42

PvdG42
Wed May 07 09:33:48 CDT 2008

"Leon P." <moi5imail@gmail.com> wrote in message
news:ONMfzF1rIHA.3780@TK2MSFTNGP03.phx.gbl...
> Hello All,
>
> I have MFC-based application featuring:
> 1) Flow of "Screens" where screens are implemented as a MFC's
> CDialog-inherited classes loading PNG or BMP images.
> 2) Dialog's child controls also loads PNG or BMP images.
>
> What is the best practice to handle the same functionality in .NET/C#?
>
>
> Thanks,
>
>

While you may get useful answers here, in these .NET programming groups,
you'd be better served in the newsgroup dedicated to MFC:

microsoft.public.vc.mfc


Re: Best practices for GUI of what called in MFC custom controls by Leon

Leon
Sun May 11 08:51:06 CDT 2008

It's multidiciplinary quesion.
However, it's more about .NET. The MFC is just referenced.

Let me re-formulate this quesion:

I'm looking for inductry way of:
1) Define flowchart of screens.
2) Translation of this chart(written most desirably) in form of
sciprt/xml/whatever to .NET implementation.
3) Each screen is supposed to have it's own graphics(bitmaps).

Regards,


"PvdG42" <pvdg@toadstool.edu> wrote in message
news:OQ4kf9EsIHA.4912@TK2MSFTNGP03.phx.gbl...
> "Leon P." <moi5imail@gmail.com> wrote in message
> news:ONMfzF1rIHA.3780@TK2MSFTNGP03.phx.gbl...
>> Hello All,
>>
>> I have MFC-based application featuring:
>> 1) Flow of "Screens" where screens are implemented as a MFC's
>> CDialog-inherited classes loading PNG or BMP images.
>> 2) Dialog's child controls also loads PNG or BMP images.
>>
>> What is the best practice to handle the same functionality in .NET/C#?
>>
>>
>> Thanks,
>>
>>
>
> While you may get useful answers here, in these .NET programming groups,
> you'd be better served in the newsgroup dedicated to MFC:
>
> microsoft.public.vc.mfc
>