Services
Support
Store
©2015 Intersoft Solutions. All rights reserved.

User Profile & Activity

Jimmy Petrus Administrator
Page
of 18
Window Desktop Problem
Posted: February 16, 2011 11:37 PM

Hello,

The .Show() and ActivateWindow are not necessary when you already set the properties.

You can try to set only the following:

axWindow.IsClientVisible = true;
axWindow.IsActive = true;

Hope this helps,
Jimmy

Opening a view from another DLL as modal
Posted: February 16, 2011 12:12 PM

Hi Sebastien,

Although your workaround may work in the current state, you lose the benefits of having independent type that created based on the application package. For instance, the GetCallingAssembly may return an unexpected assembly when your application grows more complex.

Hth,
Jimmy

UxNavigationBar Child
Posted: February 11, 2011 1:28 AM

Hi Andre,

You can use the FindName or FindNameDeep method on the UXNavigationBar to find a specific name of the button inside the AdditionalCommandTemplate.

However, this should be a rare case in Silverlight since UI elements should be "discoupled" in most chances. A number of UI scenarios can now be elegantly achieved through commanding and MVVM. Example, if a button should be disabled in a certain case, you use a Command in the button and write the CanExecute logic for the button.

Hope this helps,
Jimmy

Opening a view from another DLL as modal
Posted: February 11, 2011 1:22 AM

Hi Sebastien,

I supposed that you have created the ApplicationPackage for the Silverlight project you wish to load on demand.

In this case, make sure the EntryPointAssembly or the MainAssembly attribute in the SAFMetaData.xml that resides in your "external" Silverlight project has been properly set.

The type that you passed to the CreateInstance should be the FQDN of the class type (i.e., SilverlightApp1.Class1), and this class should be found in the assembly you specified in either the EntryPointAssembly/MainAssembly described above.

For more information about ApplicationPackage, please refer to ClientUI Application Framework Overview.

Hope this helps,
Jimmy

Communication
Posted: February 11, 2011 1:11 AM

Hi Mark,

Although the above approach may work, it's not a recommended design pattern because you're tightly coupled to a specific UI.

The best way to handle the communication is through the ViewModel. You can have the GlassLabel bound to a property in the ViewModel, let's say "{Binding Title}".

Later, in your child page (loaded inside the UXFrame), you can access the ViewModel through the DataContext and change the Title as necessary in the ViewModel.

For example, setting viewModel.Title = "New Title" in the ViewModel would automatically update the View elements bound to it.

Hope this helps,
Jimmy

Grid to Detail to Grid
Posted: February 9, 2011 10:25 AM

Hi Mark,

First of all, do you really need your users to press the "back" button to navigate back to the master view? Your answer will lead to different paths.

There are a number of ways to do this, you can use either the window or hidden panel approach, and "still" enable users to use "back" button to go back. This is done through "child" navigation where you actually has a UXFrame inside your page. You can place the frame inside a window, hidden panel, a content transition, or any content controls.

In fact, our ClientUI live example uses the similar technique to display the selected sample in the window (while still preserving the navigation functionality).

Hope this helps,
Jimmy

navigationbutton -> load xap-File
Posted: February 9, 2011 4:48 AM

Hi Andrzej,

Thank you for your post.

Could you please open a new thread for your recent question? This allows us to track solutions per opened threads.

Thanks,
Jimmy

Wpf Deployment
Posted: February 2, 2011 10:50 PM

Hi Andre,

The default template for WPF is missing the [assembly: Guid( ... )] attribute in the AssemblyInfo.cs, which is required by the ClientUI runtime licensing. We added this attribute by default in both our SL & WPF templates to ensure the licensing to work properly.

You can simply add that attribute (ensure you put in a unique GUID) to your existing application, recompile and re-run the runtime licensing.

Also, it's recommended that you fill-in the basic properties in the AssemblyInfo.cs to ensure the identity of the application.

Hope this helps,
Jimmy

UXMaskedInput
Posted: February 1, 2011 11:43 PM

Ross, thanks for the update.

We've tested the UXMaskedInput in a number of scenarios, including applying it in the Contacts application that use DevForce as data store. All worked fine so far.

It will be great if you can help to provide a small working example that replicates the issue.
Wpf Deployment
Posted: February 1, 2011 11:31 PM

Hello Andre,

Yes, you can select a WPF executable file by choosing it from the file type dropdown in the Select File dialog box.

See the illustration below.

Also, do you create the WPF application from Intersoft's WPF templates?

Hope this helps,
Jimmy

All times are GMT -5. The time now is 12:22 PM.
Previous Next