🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.nativeapi
Article #1609

Re: how to resolve conflicts in gdi+ ?

#1609
From: Remy Lebeau (TeamB)
Date: Fri, 06 Jul 2007 01:17
15 lines
1366 bytes
"4N" <xxxx@yyyy.zzz> wrote in message
news:468d6d7e$1@newsgroups.borland.com...

> because the value I assign to the variable is a HANDLE

Then it probably isn't a real HWND to begin with.

> anyway the point isn't that, that was just an example.

Then it was a bad example.  You really do need to make sure that you
are always using proper data types in all operations.


Gambit
Technical Details
Message-ID: <468d9a2b$1@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail
References: <468d2ea0@newsgroups.borland.com> <468d312f$1@newsgroups.borland.com> <468d3c18@newsgroups.borland.com> <468d5566$1@newsgroups.borland.com> <468d6d7e$1@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,42fc4c19e42cbb45
X-Google-Attributes: gid10cc67,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com>
Newsgroups: borland.public.cppbuilder.nativeapi
References: <468d2ea0@newsgroups.borland.com> <468d312f$1@newsgroups.borland.com> <468d3c18@newsgroups.borland.com> <468d5566$1@newsgroups.borland.com> <468d6d7e$1@newsgroups.borland.com>
Subject: Re: how to resolve conflicts in gdi+ ?
Date: Thu, 5 Jul 2007 18:17:21 -0700
Lines: 17
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
NNTP-Posting-Host: 75.82.252.126
Message-ID: <468d9a2b$1@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1183685163 75.82.252.126 (5 Jul 2007 18:26:03 -0700)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail