Ulrich_Laegeler at arburg.com wrote:
> 
> i pop up once more this old issue.
> 
> I have a normal text value-editor() for a xs:string attribute.
> 
> If i press the right mouse button with the inside this editor
> the mouse event is not passed thru to the document view.
> As a result my binding for the mouse button 3 is not executed.
> 
> It doesn't make any difference if the text value-editor is activated
> or not.
> 
> I think this event should be passed thru so that my binding is executed,
> or am i wrong.
> 

I've already answered your question about this. There is no bug we can
fix here. It simply cannot work with a value-editor() or any other
built-in ``form control'' generated by the CSS.

XXE bindings work only in the document view. value-editor() creates an
``alien island'' within the document view where XXE bindings no longer
apply.


> Best regards, Uli
> 
> 
> 
> 
> Von:  Hussein Shafie <hussein at xmlmind.com>
> An:   Ulrich_Laegeler at arburg.com
> Kopie:        "xmleditor-support at xmlmind.com" <xmleditor-support at 
> xmlmind.com>
> Datum:        15.12.2009 12:49
> Betreff:      Re: [XXE] value-editor control
> 
> 
> 
> Ulrich_Laegeler at arburg.com wrote:
>> the value-editor control
> 
> There is no value-editor control per se.
> 
> ---
> foo {
>     content: value-editor();
> }
> ---
> means: create whatever form control (text field, combobox, list, etc)
> that can be used to edit the content of the element which is the subject
> of the CSS rule. Of course, value-editor() needs a schema to do its job.
> 
> See
> http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/value-editor.html
> 
> 
> 
>> grabs the mouse button 3
>> with which i want to popup a context menu.
>> Is it possible to pass thru this mouse event to the application?
> 
> I'm not sure to understand.
> 
> [A] Do you want to create your own context menu, which would be specific
>  to the embedded form control?
> 
> [B] OR do you want a right-click on a embedded form control to display
> XXE's edit menu?
> 
> --> [A] is possible by specifying:
> 
> foo {
>     content: component("your AWT/Swing Component factory here");
> }
> 
> How to do this is easy and fully documented:
> 
> * See
> http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/component.html
> 
> * See
> http://www.xmlmind.com/xmleditor/_distrib/doc/api/com/xmlmind/xmledit/styledview/ComponentFactory.html
> 
> 
> * See http://www.xmlmind.com/xmleditor/_distrib/doc/dev/styleext.html
> 
> 
> 
> --> [B] is *probably* possible by specifying:
> 
> foo {
>     content: gadget("your Gadget factory here");
> }
> 
> See http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/gadget.html
> 
> Unfortunately, how to develop Gadgets is not documented (and will
> probably never be). Moreover in the case of embedded form controls, the
> Gadgets created by the factory should use a special technique[*] which
> makes all this even more difficult.
> 
> 
> 
> ---
> [*] In fact, the Gadget displays an image (i.e. screen capture) of the
> form control and not the actual form control. The actual form control is
> temporarily created when the Gadget gets the keyboard focus (Tab to or
> click on the Gadget). The actual form control is destroyed and replaced
> by its image when the Gadget looses the keyboard focus.
> 
> This allows a styled document view to efficiently embed thousands of
> form controls.
> 


Reply via email to