|
Rank: Advanced Member Groups: Member
Joined: 3/23/2010 Posts: 35
|
Hello, We've been struggling to find a solution or at least a workaround for menu flickering when expanded over ActiveX controls. Did you ever run into similar problem before? Maybe there are some workarounds that we can apply without changing the ActiveX control itself? I have attached a test page (any pdf file can be used in place of Embed.pdf) that displays this problem with Adobe's Acrobat Reader plugin for Internet Explorer. The flickering in this control is less noticeable, but it is extremely annoying in other ActiveX that we are using in our product. Thanks in advance, Laurynas
Code: HTML/ASPX
<%@ Page Language="C#" %>
<%@ Register TagPrefix="eo" Assembly="EO.Web" Namespace="EO.Web" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html>
<head runat="server">
<title>Flicker</title>
</head>
<body>
<form runat="server" action="flicker.aspx" method="post">
<div style="width: 300px; height: 300px">
<eo:Menu runat="server" ControlSkinID="Office2003">
<TopGroup>
<Items>
<eo:MenuItem Text-Html="item">
<SubMenu>
<Items>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
<eo:MenuItem Text-Html="item">
</eo:MenuItem>
</Items>
</SubMenu>
</eo:MenuItem>
</Items>
</TopGroup>
</eo:Menu>
<object data="Embed.pdf" style="width: 100%">
</object>
</div>
</form>
</body>
</html>
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi,
There is very little we can do on this on our side. Usually the ActiveX control needs to take care it. For example, a Flash object's wmmode need to be set to "transparent" in order to use with our menu. However such settings are on the ActiveX control thus depends on the ActiveX control.
Thanks!
|
|
Rank: Advanced Member Groups: Member
Joined: 3/23/2010 Posts: 35
|
Thanks. The issue is that we cannot change the ActiveX control. And we cannot release the way it works currently - at least not as a long term solution. We're stuck and see no way out currently.
What exactly would that "very little" be that you could do on your side? :)
Thanks, Laurynas
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi,
"Very little" is actually "nothing" put in a nicer way. When it comes to ActiveX control, it is impossible for us to do anything to workaround it because first ActiveX control has access to every system level API and we don't; and second there are millions of ActiveX control out there. So it is not possible for us to do anything based on the behavior of any particular ActiveX control. To put it in plain word, we will not change our product in order to "workaround" any issue on an ActiveX control.
Thanks!
|
|