User Profile & Activity

Michael Walgram Member
Page
of 2
Posted: May 4, 2013 7:21 AM

Hy Yuri,

thx for your replay ... that do it!

Again big thx!

cheers mike

Posted: April 16, 2013 2:44 AM

Hy Yudi!


do you found some workaround for the CallOut pointer problem?


Thx Mike

Posted: April 6, 2013 10:01 AM

Hy Yudi!


I have found a solution based on your sample project and the example of the CallOut TargetElement (see parent thread) 

Once again thank you for the example.


I do it with a Intersoft.CallOut and animate the pointer. That feels great on the UI. :)


One last question:

The animated pointer of the CallOut control doesn't fit exactly with the selected Item.

When the selected item of the tree isn't expand, the pointer is fitting to the item (see picture_4). 

But when a tree item is expand, the pointer goes - i think - to the middle of the hight of the expanded tree item. (see picture_5)


Is there a possibility that the pointer remains at the position of the selected tree item, even if it is expanded?


Cheers

Mike

Posted: April 6, 2013 5:19 AM

Hy Yudi!

Thx for the sample project.


You use a Intersoft:CallOut in the sample. I want to use a Intersoft:UXCallOut instead of Intersoft:CallOut because the user experience is better and the PointerPosition follow the TreeItem I have selected.


Is that also possible? I fail because the UXCallOut only works with MouseOver effect. But not when I select a new TreeItem.


Currently I use this xaml code to show a UXCallOut with MouseOver effect. I would like to change this behavior so that the contents of the UXCallOut only changes when I select another TreeItem.

<Local:HierarchyTemplateSelector x:Key="ItemTemplateSelector">
    <Local:HierarchyTemplateSelector.AnlagenbaumItemTemplate>
        <Local:HierarchicalDataTemplate ItemsSource="{Binding Kinder}">
            <Intersoft:UXCallOut HorizontalAlignment="Center" VerticalAlignment="Center" 
			 IsOpen="False" MouseClickAction="None"
			 MouseEnterAction="ShowPopup" MouseLeaveAction="HidePopup" 
			 DisableOverlay="True" PreferredPosition="Right">
                <Intersoft:UXCallOut.CallOutEffect>
                    <DropShadowEffect BlurRadius="9" ShadowDepth="12"/>
                </Intersoft:UXCallOut.CallOutEffect>
                <Intersoft:UXCallOut.Header>
                    <StackPanel Orientation="Horizontal">
                        <Image Source="{Binding BildPfad}" Style="{StaticResource ImageStyle}" />
                        <TextBlock Text="{Binding Name}" Style="{StaticResource TextBlockNormalStyle}" />
                    </StackPanel>
                </Intersoft:UXCallOut.Header>
                <Grid Height="Auto" Width="Auto">
                    <Local:AggregatWechselnForm/>
                </Grid>
            </Intersoft:UXCallOut>
        </Local:HierarchicalDataTemplate>
    </Local:HierarchyTemplateSelector.AnlagenbaumItemTemplate>
</Local:HierarchyTemplateSelector>

 

I tried to change the UXCallOut MouseClickAction property to "Show Popup", but this value did not produce the desired behavior.

I also would like to set a fixed position for the UXCallOut, so that only changes the pointer position.

As in this example here: http://live.clientui.com/#/Controls/CallOut/TargetElement


Cheers

Mike

Posted: February 14, 2013 9:55 AM

Thx for the reply and the information.


I have fixed it with my ViewModel!


Cheers mike

Posted: September 13, 2012 9:03 AM
Exactly!

It is also possible that the corresponding window is already open!
Posted: September 10, 2012 9:17 AM
Has anyone an idea
Posted: September 6, 2012 4:32 AM
Hi Yudi!

An other question to this topic!
Is there a possibility for windowCommanding that the addressed window will not be activated.

I use this part of code to send my data to an other window.

var wo = new WindowOptions(){
    Uri = new Uri(String.Format("/{0};{1}", targetAssemblyName, targetWindowName), UriKind.Relative),
    ForceSingleInstance = true,
    WindowName = targetUXWindowName.ToString(),
    ReactivateExistingInstance = true,
    StartupParameters = parameter
};
Intersoft.Client.Framework.WindowCommands.LaunchApplication.Execute(wo, desktop);


cheers mike!


Posted: September 5, 2012 3:17 AM
thx yudi!

that helps me!
Posted: July 6, 2012 2:55 AM

Hy Yudi,

 

thx for the replay.

This post helps me to solve my problem!

 

cheers mike

All times are GMT -5. The time now is 1:59 AM.
Previous Next