Showing posts with label upgrading. Show all posts
Showing posts with label upgrading. Show all posts

Wednesday, March 28, 2012

Programatically Expand CollapsiblePanel (With Lastest ToolKit)

The issue I am experiencing is due to upgrading to the latest ToolKit. I previously was able to use this code on a postback to expand a collapsible panel.

Previous Code:
Dim clp2 As CollapsiblePanelProperties = CollapsiblePanelExtender2.GetTargetProperties(Panel2)
clp2.ClientState =True
clp2.Collapsed =False

However I do understand that with the upgrade the Properties sections under each of the ToolKit controls is no longer valid. I personally liked the ability to place multiple <atlasToolKit:Properties> tags underneath ONE <atlasToolKit:CollapsiblePanel> tag. Why did you remove that?? It was easy to migrate but a hassle in regards to having to set up a new tag for each time. Anyhow... off of the soapbox.

Current Code:
Dim clp2As CollapsiblePanelExtender = CollapsiblePanelExtender2
clp2.ClientState =True
clp2.Collapsed =False

This fails to expand the Panel on a postback. Any help or solutions?

JoeWeb

I believe the ClientState value needs to be lower cased and quoted as per this post:http://forums.asp.net/thread/1325048.aspx.


Yeah after playing around with it for a little bit... I actually discovered that the following code fixed it.

Dim clp2As CollapsiblePanelExtender = CollapsiblePanelExtender2
clp2.ClientState =False
clp2.Collapsed =False

All that is different is that I set both to false.

Anyhow I figured it out about a week ago sorry I didn't post an update. Thanks!

JoeWeb

Wednesday, March 21, 2012

Question about the slider extender control and "hiding" the textbox it extends

Copied and pasted from the interactive sample pages, under slider tips:

TextBox visibility. The asp:TextBox that the Slider is upgrading will be visible during the page loading, so it is usable if JavaScript is not enabled on the browser. Depending on your requirements, you can prevent the asp:TextBox from being visible by setting its display mode to "none".

However, there is no display mode or displaymode property for the textbox control, nor for the slider extender. How then can I prevent the textbox from being visible while the page is loading?

Another question: is there a way to set the slider to enabled = "false" where it would show the value (e.g. the slider being at the middle of the rail for a value of 50%) without it being movable? I tried setting the textbox to enabled = false. The slider looks somewhat grayed out, but you can still click on the slider and move it. Thanks a lot.

Hi,

1) display is a CSS attribute. you should set display:none on the extended TextBox.

2) At the moment the slider can't be disabled, but this is a good suggestion.

Thanks.


Ah thanks. Forgot about the css attribute for that.

As for the slider not being enabled or disabled, I guess I'll just make it invisible for now.

Question to the Ajax/ MS Team - UpdatePanels

There have been several posts that remained unresolved about why they were always getting FULL PostBacks after upgrading from RC versions to the Release Version. After reading the posts and doing a little testing - I discovered that merely dragging and dropping an UpdatePanel on a page - it defaults with UpdateMode = "Always".

That kinda does not make sense as the default should be towards the benefit of using Ajax - or in other words should always default to "Conditional" and I do believe that is a change between the RC and Release version.

The same goes for PageMethods - It should default to already enabled - like it did in the previous versions or at least on the docuementation site a left hand menu selection specifically for PageMethods - should annotate when clicked - PageMethods not enabled by default...

Alot of times as programmers while we may use the Designer mode - most of the times as we are building references do not popup to display all the defaults especially if there is an error on the page such as a missing /div tag etc...

But the main point it - strikes me odd from a usability standpoint why UpdateMode is defaulted to "Always"... I use VS Team Studio if that helps (and it has always had it quirks in the Ajax development scenarios...

None the less there mere fact it is defaulted to Always should be emphasized on the Docs site considering now everyone assumes that is the goto reference since it is no longer beta...

Hi,

the "Always" mode is not related with performing a full postback rather than a partial one. If an UpdatePanel has UpdateMode="Always", it will refresh its content even if the partial postback was triggered by a control that's not contained in the UpdatePanel, nor it's a trigger for that UpdatePanel.

If UpdateMode="Conditional", the UpdatePanel will refresh its content only if one of *its* children controls (if ChildrenAsTriggers="true") or triggers start the partial postback.


I believe that UpdateMode = "Always" has been the default since the Beta 1 release, and I don't think there was a default before that with the CTPs. I remember having to put it for every UpdatePanel. A large number of the posts I have come across about full postbacks have been from people who have not used the previous releases or are having validator issues. I have seen a few posts where people thought ajax worked differently, for example mistaking full postbacks with going to a whole new page. There are a lot of people that seem to have validator issues because they just are reading the conversion guide, not the blogs or other information about the validator change in the RTM, so they don't know they have a problem with validators.

Question: Is Upgrading Atlas Versions Easy?

Hi there,

I'm just wondering how difficult it will be to upgrade an app using the October release to the January release of Atlas. Are there any issues I should be looking at? Has anyone else tried it?I've never done it, but I have upgraded one of Nikhil Kothari's samples from the PDC2005: thePhotoBrowser to the December release and there were several API changes. These files are dated in September 2005, so I'm assuming they're using an earlier release than the October release. I believe upgrading from the December to the January release should be a smoother process.