BUG: Embedded Object's Size Changes When it Is Run

 Last reviewed: May 17, 1995
Article ID: Q110872
The information in this article applies to:
  • Microsoft OLE Libraries for Windows and Win32s, version 2.01
  • Microsoft OLE Libraries, included with: 

        - Microsoft Windows NT, versions 3.5 and 3.51
    - Microsoft Windows 95

SYMPTOMS

A non-running embedded object is resized in an OLE 2.01 container application. The next time the object is run, it snaps back to its previous size.

CAUSE

The container application failed to call IOleObject::SetExtent() after calling OleRun().

RESOLUTION

IOleObject::SetExtent() can be called only when an object is running. If an object is resized while it is not running, the container application should take note of this. When the object is subsequently run, the container should then inform the object of its new size by calling IOleObject::SetExtent().

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base when it becomes available.

Additional reference words: 2.01 3.50 4.00
KBCategory: kbole kbbuglist
KBSubcategory: LeTwoCdt

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 17, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.