Hi,
I am not able to resize the frame properly if one of frame has a JAVA Applet (100% Height, Width). This is code structure that splits the page.
I am not able to resize the frame properly if one of frame has a JAVA Applet (100% Height, Width). This is code structure that splits the page.
<
telerik:RadSplitter id="splitter" FullScreenMode=true runat="server" height="100%" width="100%" ResizeMode="AdjacentPane">
<telerik:RadPane id="panel_Normal_HTMLPage" runat="server" width="48%" >
</telerik:RadPane>
<telerik:RadSplitBar id="splitterBar" runat="server" collapsemode="Both" style="z-index:999999" />
<telerik:RadPane id="panel_JAVAApplet_FullPage" runat="server"></telerik:RadPane>
</telerik:RadSplitter>
It seems that splitter's drag drop doesn't work properly if dropping is over Java Applet.
Please help.
Kind Regards,
Abhi Rohila
3 Answers, 1 is accepted
0
Hello Abhi,
This behavior is expected - unfortunately it is not possible to detect mouse events over Java applets as they are never fired by the browser in the first place. That is why the RadSplitBar never receives the mouseup event and thus you cannot release it over the applet.
The plugin browser architecture works in the following manner:
- A rectangular portion of the page is "given" to the plugin to display a document.
- All events are managed by the plugin and no event communication or propagation occurs from the plugin area to the browser.
The RadSplitter control supports a property LiveResize, and if you set it to true and test it, you will see that when moving the mouse slowly, everything seems to work. But a fast move over the applet would cause the events to get 'lost'.
Greetings,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
This behavior is expected - unfortunately it is not possible to detect mouse events over Java applets as they are never fired by the browser in the first place. That is why the RadSplitBar never receives the mouseup event and thus you cannot release it over the applet.
The plugin browser architecture works in the following manner:
- A rectangular portion of the page is "given" to the plugin to display a document.
- All events are managed by the plugin and no event communication or propagation occurs from the plugin area to the browser.
The RadSplitter control supports a property LiveResize, and if you set it to true and test it, you will see that when moving the mouse slowly, everything seems to work. But a fast move over the applet would cause the events to get 'lost'.
Greetings,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
chris
Top achievements
Rank 1
Rank 1
answered on 17 Jun 2009, 10:45 PM
I'm seeing similar behavior when the splitBar is used between two panes containing iframes. Is that expected? What about if the panes contained ActiveX controls like stellant / oracle's document viewer?
It's also interesting that it seems to be just the presence of the iframes. That is, even if I do the drag operation over parts of the panes that don't include the iframes I still see the splitBar missing the mouseUp events.
Thanks,
Chris
It's also interesting that it seems to be just the presence of the iframes. That is, even if I do the drag operation over parts of the panes that don't include the iframes I still see the splitBar missing the mouseUp events.
Thanks,
Chris
0
Hi Chris,
There is a problem with catching mouse events when using IFRAMEs also but they are also due to the way the things work. The IFRAME is actually another, separate document and it has it owns events - this being said, you come to a point that once you have gone into the IFRAME, the events belong to the other document and if you release the splitbar, the main document does not know about this event but only the document loaded in the IFRAME "understands" that the mouse button was released.
Dealing with IFRAMEs,PDF documents, Java Applets and their events is pretty complex in such scenarios and we have introduced different workaround where this is possible - e.g the RadWindow which also contains an IFRAME hides the IFRAME while it is being moved or resized in order to prevent this IFRAME to catch the mouse events and to associate them with the main page. For the RadSplitter control, everything which we can suggest in order to improve the behavior in such scenarios is the following:
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
There is a problem with catching mouse events when using IFRAMEs also but they are also due to the way the things work. The IFRAME is actually another, separate document and it has it owns events - this being said, you come to a point that once you have gone into the IFRAME, the events belong to the other document and if you release the splitbar, the main document does not know about this event but only the document loaded in the IFRAME "understands" that the mouse button was released.
Dealing with IFRAMEs,PDF documents, Java Applets and their events is pretty complex in such scenarios and we have introduced different workaround where this is possible - e.g the RadWindow which also contains an IFRAME hides the IFRAME while it is being moved or resized in order to prevent this IFRAME to catch the mouse events and to associate them with the main page. For the RadSplitter control, everything which we can suggest in order to improve the behavior in such scenarios is the following:
- Set LiveResize="true" as already suggested.
- Set debug="false" in the Web.config
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.