Yep, this is one of those nasty, known issues with vendoring right now. 
this exact issue was first raised on this list here: 
https://groups.google.com/d/msg/golang-nuts/AnMr9NL6dtc/UnyUUKcMCAAJ. 

We've got a crew coming together soon to address this issue, among many 
others: 
https://docs.google.com/document/d/18tNd8r5DV0yluCR7tPvkMTsWD_lYcRO7NhpNSDymRr8/edit#

On Thursday, August 18, 2016 at 8:19:26 PM UTC-4, howar...@gmail.com wrote:
>
> My poor brain is melting. I was just worried about vendoring shiny and the 
> effect of that on producing something to be easily embedded in other 
> people's programs... while writing a (successful, mind!) wrapper of 
> sigint.ca/graphics/editor that makes it fit the Widget node.LeafEmbed 
> model of shiny... 
>
> And when I tried to pass in mouse events as well as the keyboard events I 
> was already passing, I got this error:
> ./textedit.go:65: cannot use e (type "golang.org/x/mobile/event/mouse".Event) 
> as type "sigint.ca/graphics/vendor/golang.org/x/mobile/event/mouse".Event 
> in argument to t.editor.SendMouseEvent
>
> Sooo.... the library I am adding to extend the missing functionality in 
> shiny, already vendors shiny and mobile. o_O
> Though, only mobile/event/mouse/mouse.go, which based on its alterations, 
> I assume fits with modifications to their vendored shiny, as otherwise I 
> can't see how it could be filled out. But which means that when embedding 
> in un-vendored shiny, you can't send them any mouse events... as far as I 
> can see, you can't even manually repackage events in the format they want, 
> because you can't import the vendored package from another package.
>
> I also can't just vendor sigint.ca and add a WrapMouseEvent(e 
> unvendoredevent) type call, since the new 1.7 vendoring stuff does 
> automatic rewriting, so I can't get at *both* the vendored *and* the 
> unvendored on either side. I could possibly pass it through as an 
> interface{} and unpack it with reflection (bleh!), or create yet a third 
> mouse.Event that is actually on a different path, so is accessible to both, 
> and convert it twice (ick, but less so). Not really sure where to go with 
> this, but I guess mouse interaction is not critical to my primary intended 
> use... so back to what I was trying to accomplish.
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to