Bug 313075 - Accessible should not use VARIANT struct for 64-bit VT_DISPATCH values
Summary: Accessible should not use VARIANT struct for 64-bit VT_DISPATCH values
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-17 02:47 EDT by Carolyn MacLeod CLA
Modified: 2021-11-12 11:31 EST (History)
2 users (show)

See Also:

Attachments
patch to fix 64-bit VARIANT problems (3.03 KB, patch)
2010-05-17 02:47 EDT, Carolyn MacLeod CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carolyn MacLeod CLA 2010-05-17 02:47:05 EDT 
Created attachment 168688 [details]
patch to fix 64-bit VARIANT problems

If a VARIANT parameter has a variant type of VT_DISPATCH, need to get the interface pointer using MoveMemory(..., ..., OS.PTR_SIZEOF), rather than just accessing the VARIANT's lVal field. This is because lVal is an int, but we need an int /*long*/ value so that the pointer is the correct size on 64-bit platforms.
Comment 1 Carolyn MacLeod CLA 2010-05-17 02:52:17 EDT 
Should also fix Acessible.getNumberVARIANT() using the same pattern. See setNumberVARIANT() for the valid types.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:38:27 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.