VC.NET vs VB.NET - C / C++ / MFC Discussion Boards

First Prev Next

Re: Visible area of CDC

Maximilien5-Dec-02 4:18

Maximilien

5-Dec-02 4:18

Huh ?

You normally draw in the client area of a window ( GetClientRect ), should be clipped, for additional clipping, look for them in the CDC help of MSDN.

Max.

Re: Visible area of CDC

Paul M Watt5-Dec-02 5:31

Paul M Watt

5-Dec-02 5:31

Use the function ::GetRandomRgn with the SYSRGN flag. You may need to download the most current SDK headers in order to use this function.

I have written this article on clipping regions:

http://www.codeproject.com/gdi/cliprgnguide.asp[^]

It describes the system region, clipping region and meta region. It also has an example of how to get the imformation that you are asking for.

Good Luck

Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!

Re: Visible area of CDC

S O S5-Dec-02 10:04

S O S

5-Dec-02 10:04

Thanks!

Adding a printer driver programmatically

Adrian von Gunten5-Dec-02 3:53

Adrian von Gunten

5-Dec-02 3:53

I'm trying to add the "Generic / Text Only" printer driver programmatically.

I've used AddPrinterDriver and AdPrinterDriverEx from the API but the driver doesn't work.

Did anybody solve this problem or have anybody some suggestions?

checking a pipe status

Martin Blanc5-Dec-02 3:43

Martin Blanc

5-Dec-02 3:43

I've got a named pipe. One process writes to its (let's call it A) side, and the other process reads from its oposite (B) side. The process at the B side can randomly connect to and disconnect from the pipe. I'd like to prevent the A-side process from even trying to write to the pipe if the B-side process is disconnected. How can A-side process check the B-side pipe status? I have an idea of using PeekNamedPipe() with all its pointer parameters set to NULL and, when I get return value zero, interpret the result of GetLastError(), but this idea by no means seems that smart to me.
Any suggestions? Is GetNamedPipeHandleState() of any use in these situations?

TIA
Martin

Re: checking a pipe status

Alois Kraus5-Dec-02 23:29

Alois Kraus

5-Dec-02 23:29

I did use PeekNamedPipe for this purpose and it worked perfectly.
I use a one byte reciever buffer in the PeekNamedPipe function.
You could of course use WriteFileEx with an completion Routine and wait
for an error to occur.

A live ping always involves sending packets and check if the reciever responds
to it. There is simply no other way to check if somebody has unplugged Your network cable. PeekNamedPipe does exactly this in a transparent way without disturbing
your data transfer.

Re: checking a pipe status

Martin Blanc6-Dec-02 4:54

Martin Blanc

6-Dec-02 4:54

Thanks for your reply. Now I know I'm standing on the firm ground. Sometimes it's better to learn from others' successes instead of my own failures. Smile | :)

Martin

VC.NET vs VB.NET

devvvy5-Dec-02 3:20

devvvy

5-Dec-02 3:20

hi, pretty new to .NET. But just want to make sure that i pick the right tool for a development project.

Project: coporate infrastructure - from scratch. Areas of concern involves: SQL Server 2000 dev/DMO, Active Directory, IIS (web server and FTP), security (Crypto), Exchange Server, Web application/service, WIN 2000 Adv Server.

Why Choose VC?
1. Backward compatibility
2. speed

but since:
1. this is a infrastructure project starting from scratch, we're not really concerned with "backward compatibility"? I presume there'd be no problem integrating COM components into VB.NET code.

2. speed. VB.NET is not any slower than VC.NET.

3. GUI. VB has a much better dialog editor than VC.

Just want to re-confirm my understanding. My preferred development tool for project like this will be VB.NET.

What do u think?

norm