C# UI programming question

[=?Utf-8?B?S2lk?=]

Hi

Is there some good sample about using C# to write MDI or multi-dialog style
app?

How can I get other app window client pixel data like VC++ Win32 sample ?

Is there some sample using C# to send message to other app UI control ?
( I would like to write some screenshot and some auto run tool )

Thank for your kind helping .

[raylopez99]

On Nov 3, 10:08*pm, Kid <K...@discussio ns.microsoft.co mwrote:

Hi

Is there some good sample about using C# to write MDI or multi-dialog style
app?

How can I get other app window client pixel data like VC++ Win32 sample ?

Is there some sample using C# to send message to other app UI control ?
( I would like to write some screenshot and some auto run tool )

Thank for your kind helping .

Why would you want to use MDI for C#? MDI is the past, C# Forms is
the future. Chris Sells in his Win Forms 2.0 Programming book has a
short section on "hosting MFC in Win Forms" but nothing on using C# to
write MDI. As for sending messages to another app UI control, I
assume you don't mean a child form within C#, which is trivially easy,
but another unrelated app. You need to perhaps use COM or equivalent
to pass information between two unrelated apps running in Windows--or
use a low-level driver. Not easy to do I would imagine.

RL

[Jeff Gaines]

On 04/11/2008 in message
<22************ *************** *******@w1g2000 prk.googlegroup s.com>
raylopez99 wrote:

>Why would you want to use MDI for C#? MDI is the past

It's not the past while programmers keep it alive! Worst mistake MSFT made
was making Word SDI.

Anyway, MDI is quite feasible in C#, the OP can do a search on the Code
Project for examples:
http://www.codeproject.com/info/sear...tkw=mdi&sbo=kw

--
Jeff Gaines Damerham Hampshire UK
"Why is it that when we talk to God we're said to be praying,
but when God talks to us we're schizophrenic?"

[Tim Roberts]

"Jeff Gaines" <wh*********@ne wsgroups.nospam wrote:

>
raylopez99 wrote:

>>Why would you want to use MDI for C#? MDI is the past

It's not the past while programmers keep it alive! Worst mistake MSFT made
was making Word SDI.

Microsoft's usability research strongly disagrees with your assertion.
--
Tim Roberts, ti**@probo.com
Providenza & Boekelheide, Inc.

[Jeff Gaines]

On 11/11/2008 in message <qd************ *************** *****@4ax.comTi m
Roberts wrote:

>"Jeff Gaines" <wh*********@ne wsgroups.nospam wrote:

>>
raylopez99 wrote:

>>>Why would you want to use MDI for C#? MDI is the past

It's not the past while programmers keep it alive! Worst mistake MSFT made
was making Word SDI.

Microsoft's usability research strongly disagrees with your assertion.

I disagree with most of their usability 'research' and often wonder who
they speak to, e.g.:
Arranging windows on a multi monitor setup when Word has 6 windows open
instead of only 1 creates a chaotic mess.
Introducing a ribbon that reduces usable screen height when modern
monitors are getting shorter
Opening a DVD drive if you accidentally click on it in Explorer (in Vista)
when it's empty - do none of their usability researchers know that many
PC's have doors on them? I wonder how many drives have burnt out because
of that stupid behaviour.

MSFT need to speak to some real users.

--
Jeff Gaines Damerham Hampshire UK
Indecision is the key to flexibility