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

User Profile & Activity

Harry Fairhead Member
ProgressBar Postback mode
Posted: January 6, 2011 6:00 AM

Well yes it helps and thanks for that  but....

This is exactly the sort of kunge I want to avoid by using a library like Intersofts.
I want uniformity and I a can't see any reason why ALL of Intersoft's controls shouldn't support PostBackMode  - a point the documenation and advertising makes as a plus point - and to this question or issue you have remained completely silent.

So once again thanks for your efforts but it doesn't really address the logical inconsistency in the framework.

ProgressBar Postback mode
Posted: January 5, 2011 5:52 AM

Yes indeed I understand how FlyPostBack works and I can see that yes I can do these small changes but I want a FullPostBack to occur when the ProgressBar reaches 100%.

It is more logical (as the documenation suggests) for ALL Intersoft's ASP .NET components to support both full and fly PostBack - it is a great shame that this is not the case as  it would be a compelling reason to use them.

 

ProgressBar Postback mode
Posted: January 4, 2011 4:55 AM

"But you are still able to run WebProgressBar in FullPostback mode by using the Server-side event provided in its properties."

How exactly - I'm using the server side events and the only option is for FlyPostBack?

ProgressBar Postback mode
Posted: January 4, 2011 2:10 AM

can the documentation be updated to reflect this - wastes a lot of time trying to find facilities which actually dont exist.

Also why "naturally" I want a full postback on the finished event?

It would be more logical - again as the documentation suggests - to support both bostback modes on all components

Commanding in WPF
Posted: January 3, 2011 1:22 PM

Any progress on the update?

Navigation in WPF
Posted: January 3, 2011 1:20 PM

Any progress?

 

Navigation in WPF
Posted: December 9, 2010 12:54 PM

The code is essentially that given in the documenation.

        <StackPanel Grid.Column="1">
            <Intersoft:UXHyperlinkButton Content="Home" NavigateUri="/page" />  
           
        </StackPanel>
and
     <Intersoft:UXFrame etc>
            <Intersoft:UXFrame.UriMapper>
                <Intersoft:UriMapper>
                    <Intersoft:UriMapping Uri="/page" MappedUri="/View/UXPage1.xaml"/>
 
                </Intersoft:UriMapper>
 
            </Intersoft:UXFrame.UriMapper>
        </Intersoft:UXFrame>
 

and there is a UXPage1.xaml in the View Directory - the code works in Silverlight and WPF browser but in WPF it gives

 

System.NullReferenceException was unhandled
  Message=Object reference not set to an instance of an object.
  Source=Intersoft.Client.UI.Navigation
 

Commanding in WPF
Posted: December 9, 2010 11:59 AM

Ok, thanks and I follow the answer perfectly.

I will look out for the update and redownload the trial - I assume that this doesn't trigger any problems with the licence (time remaining etc.)

 

Commanding in WPF
Posted: December 9, 2010 8:20 AM

So again to be clear - I can't make the WPF routed command version work until I download a new build of the ClientUI framework?

Also how do I find out about the update i.e what do I do with  "feedback reference #868".

Also I'm evaluating the software using the trial version - will the update work with this?

Navigation in WPF
Posted: December 9, 2010 7:39 AM

So to be 100% clear - the navigation should work in a standard (not browser) WPF application as it does in a Silverlight app?

 

And I am using UXPage and UXFrame as per the Silverlight and WPF browser app which both work - but the WPF desktop app doesn't work.

 

All times are GMT -5. The time now is 8:05 AM.
Previous Next