Map a functional UI to the side of a 3d object

I'd like to see something along the lines of a ui. One form worth of
user input on the side of a cube, another form of input on another side
of the cube.

Previous this wasnt possible, only able to SIMULATE by transforming and
painting (but apparently the controls themselves were no longer functional?)

I was just curious if this remains to be true.

Thanks in advance.

For WPF V1 the answer is "nothing has changed"...but....

WPF V2 should have a fix for this.

Third party control vendors may have offerings of a fix post V1 and pre V2.

You can do a 2d to 3D to 2d transitions...which can be tricky, but it can
work. I've done this numerous times for WPF demos - like the latest
healthcare app. The tricky part is dynamic resizing which third party vendors
will need to investigate for a more robust solution using this technique.


"Weston Weems" wrote:

> I'd like to see something along the lines of a ui. One form worth of
> user input on the side of a cube, another form of input on another side
> of the cube.
>
> Previous this wasnt possible, only able to SIMULATE by transforming and
> painting (but apparently the controls themselves were no longer functional?)
>
> I was just curious if this remains to be true.
>
> Thanks in advance.
>

You still have to simulate mouse events. Maybe this post will help you
:

http://www.codeproject.com/useritems...nteraction.asp

The trick is to map the visuals in int ui each on their own model to
make the manual hittesting simpler.


TheRHogue wrote:
> For WPF V1 the answer is "nothing has changed"...but....
>
> WPF V2 should have a fix for this.
>
> Third party control vendors may have offerings of a fix post V1 and pre V2.
>
> You can do a 2d to 3D to 2d transitions...which can be tricky, but it can
> work. I've done this numerous times for WPF demos - like the latest
> healthcare app. The tricky part is dynamic resizing which third party vendors
> will need to investigate for a more robust solution using this technique.
>
>
> "Weston Weems" wrote:
>
> > I'd like to see something along the lines of a ui. One form worth of
> > user input on the side of a cube, another form of input on another side
> > of the cube.
> >
> > Previous this wasnt possible, only able to SIMULATE by transforming and
> > painting (but apparently the controls themselves were no longer functional?)
> >
> > I was just curious if this remains to be true.
> >
> > Thanks in advance.
> >

I was told that it is possible in wpf to retrieve the texture-UV-Coordinates
of where an object was hit. I haven't managed to implement a working sample
that does this, though. In case this is possible, the rest is not so hard
anymore. Does anyone have a working sample that does that ?

<sbarlea@gmail.com> schrieb im Newsbeitrag
news:1156747609.703032.240090@m79g2000cwm.googlegroups.com...
> You still have to simulate mouse events. Maybe this post will help you
> :
>
> http://www.codeproject.com/useritems...nteraction.asp
>
> The trick is to map the visuals in int ui each on their own model to
> make the manual hittesting simpler.
>
>
> TheRHogue wrote:
>> For WPF V1 the answer is "nothing has changed"...but....
>>
>> WPF V2 should have a fix for this.
>>
>> Third party control vendors may have offerings of a fix post V1 and pre
>> V2.
>>
>> You can do a 2d to 3D to 2d transitions...which can be tricky, but it can
>> work. I've done this numerous times for WPF demos - like the latest
>> healthcare app. The tricky part is dynamic resizing which third party
>> vendors
>> will need to investigate for a more robust solution using this technique.
>>
>>
>> "Weston Weems" wrote:
>>
>> > I'd like to see something along the lines of a ui. One form worth of
>> > user input on the side of a cube, another form of input on another side
>> > of the cube.
>> >
>> > Previous this wasnt possible, only able to SIMULATE by transforming and
>> > painting (but apparently the controls themselves were no longer
>> > functional?)
>> >
>> > I was just curious if this remains to be true.
>> >
>> > Thanks in advance.
>> >
>

funny, to me it seems to be the other way round
mapping 3d to 2d is not soo difficult (turn mouseposition
into ray and calculate intersection with plane).
but how would you translate the found coordinate into a
click event?

cheers
Florian


bonk wrote:
> I was told that it is possible in wpf to retrieve the texture-UV-Coordinates
> of where an object was hit. I haven't managed to implement a working sample
> that does this, though. In case this is possible, the rest is not so hard
> anymore. Does anyone have a working sample that does that ?

I realize that there's quite a few different scenarios.
mapping a functional ui onto a side of a 3d cube, IMHO involves the
following steps:
1. create a normal (2D) UI (e.g. a Panel with buttons) and hide it
somewhere.
2. setup your 3d scene and map a visual brush onto the cube, which
you bind to the hidden ui
3. translate mouseclicks to relative 2d coordinates on the side of
the cube (construct a ray using an inverse matrix and intersect the
ray with the functional side of the cube).
4. artifically raise a mouseclick event on the hidden ui...

except for the last step, it all seems doable to me.
I've wrapped my head around this for quite a while, but possible
solutions all look pretty difficult. e.g. using UIAutomation or
create a custom subclass of InputDevice.

Florian
--
kruesch.de
Florian Krüsch | MCAD
info@kruesch.de

Or try

RoutedEventArgs fakeArgs = CreateFakeInputEventArgs(originalEventArgs,
fake2DX, fake2DY);
hiddenElement.RaiseEvent(fakeArgs);

CreateFakeInputEventArgs(...) would create an appropriate
(MouseButtonEventArgs or KeyEventArgs) by cloning and modifying the
apropriate properties on originalEventArgs

-- Ifeanyi Echeruo [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Florian Kruesch" <nospam@kruesch.de> wrote in message
news:OHMx1L1yGHA.3440@TK2MSFTNGP06.phx.gbl...
>I realize that there's quite a few different scenarios.
> mapping a functional ui onto a side of a 3d cube, IMHO involves the
> following steps:
> 1. create a normal (2D) UI (e.g. a Panel with buttons) and hide it
> somewhere.
> 2. setup your 3d scene and map a visual brush onto the cube, which
> you bind to the hidden ui
> 3. translate mouseclicks to relative 2d coordinates on the side of
> the cube (construct a ray using an inverse matrix and intersect the
> ray with the functional side of the cube).
> 4. artifically raise a mouseclick event on the hidden ui...
>
> except for the last step, it all seems doable to me.
> I've wrapped my head around this for quite a while, but possible
> solutions all look pretty difficult. e.g. using UIAutomation or
> create a custom subclass of InputDevice.
>
> Florian
> --
> kruesch.de
> Florian Krüsch | MCAD
> info@kruesch.de

Ifeanyi - exactly that's what I was going to do, but everything position
related is bound to a MouseDevice, which is a sealed class and cannot
be overridden.

Florian


Ifeanyi Echeruo [MSFT] wrote:
> Or try
>
> RoutedEventArgs fakeArgs = CreateFakeInputEventArgs(originalEventArgs,
> fake2DX, fake2DY);
> hiddenElement.RaiseEvent(fakeArgs);
>
> CreateFakeInputEventArgs(...) would create an appropriate
> (MouseButtonEventArgs or KeyEventArgs) by cloning and modifying the
> apropriate properties on originalEventArgs

Yup, you're right. I was channeling the winforms mouse eventing model, where
the x and y of the mouse are captured in the event args.

-- Ifeanyi Echeruo [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Florian Kruesch" <nospam@kruesch.de> wrote in message
news:%23WMolW6yGHA.1288@TK2MSFTNGP03.phx.gbl...
> Ifeanyi - exactly that's what I was going to do, but everything position
> related is bound to a MouseDevice, which is a sealed class and cannot
> be overridden.
>
> Florian
>
>
> Ifeanyi Echeruo [MSFT] wrote:
>> Or try
>>
>> RoutedEventArgs fakeArgs = CreateFakeInputEventArgs(originalEventArgs,
>> fake2DX, fake2DY);
>> hiddenElement.RaiseEvent(fakeArgs);
>>
>> CreateFakeInputEventArgs(...) would create an appropriate
>> (MouseButtonEventArgs or KeyEventArgs) by cloning and modifying the
>> apropriate properties on originalEventArgs

v2? Is this for .NET v4?

Jon