Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

C/C++

A Video for Windows ActiveX Control


Jun99: Support for Visual C++ 6

Support for Visual C++ 6

Porting this project to Visual C++ 6 was a reminder that new versions of compilers often require code modifications instead of just a simple recompilation. The following issues had to be resolved to get Visual C++ 6 to produce a working control:

  • The Video for Windows macros (found in VFW.H), such as capPreviewScale, utilize the function IsWindow, assuming that this function from the Windows API will be used. Apparently, the ATL base classes now include their own IsWindow method, which has a different parameter list. Since C++ compilers first try to match functions against class methods, each such macro generates a compiler error. I bypassed this problem by adding to my control class an IsWindow method that calls the Windows API function.
  • Some changes were required in order for VC++ 6 to accept the DIID__ oVFWEvents object. These were mostly semantic and location problems (that is, the statement had to take place before oVFW.h was used).

  • Adding events to Visual C++ 6 is much simpler than with earlier versions. An ATL class (object or control) that specifies that it will use events automatically attaches an event interface to the object's class. Now, the event-interface class can be accessed as if it were a standard COM interface (methods can be attached to it, for example). Finally, after VC++ compiles the IDL source to a binary TLB file, right clicking the ATL class and selecting the "Implement Connection Point" menu will create the proxy class and all of the other requirements for the class to fire events.

-- O.L.


Copyright © 1999, Dr. Dobb's Journal

Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.