Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

Very buggy. I would recommend NOT using it. It only worked for me as expected on one page I tried it on.

 

There is also a lot of stuff in a lot of forums saying the same thing I am saying here. Which is sad, because it would be so awesome if it worked.

Posted
Very buggy. I would recommend NOT using it. It only worked for me as expected on one page I tried it on.

 

There is also a lot of stuff in a lot of forums saying the same thing I am saying here. Which is sad, because it would be so awesome if it worked.

 

What's so buggy about it? I've turned it for today to see if I can see any difference in my asp.net project, and a couple pages don't flicker much, but I haven't seen any bugs yet...

  • Moderators
Posted

I don't find it buggy at all, it's primarily for the page to go back to the same area of the page on postback as it was before the postback.

 

So if you have a grid 20 inches down and you click to go into edit mode you will see the grid on postback. It works just fine.

Visit...Bassic Software
Posted

Most of my pages have controls that are made visible on demand or datagrids that need viewstate enabled, etc. As long as the page has only standard controls do the most basic tasks, I have not had any troubles with it. It is when I have controls that are made visible at runtime or datagrids whose properties are altered at runtime that the smartnavigation causes errors. If you just have textboxes, lables, etc. then it is nice.

 

On pages where I have manipulated the controls either the page postbacks without them being visible anymore or the page freezes (this was the most common). In some cases the information in the controls that had been made visible was set back to blank rather than maintaining state through postbacks.

 

If I want a page to show up in a specific place I use a class I created to set focus where I could like it to be after postback. The code for the class is:

 

Public Class SetFocus

 

Public Sub SetFocus(ByVal controlToFocus As Control, ByVal callingPage As Page)

Dim scriptFunction As String

Dim scriptClientId As String

 

scriptClientId = controlToFocus.ClientID

 

scriptFunction = "<script language='javascript'>"

scriptFunction += "document.getElementById('" & scriptClientId & "').focus();"

scriptFunction += "</script>"

 

callingPage.RegisterStartupScript("focus", scriptFunction.ToString())

End Sub

 

End Class

 

 

I hope that clarifies things a bit more. I would add links here to other examples of bugs in smartnavigation that people have encountered but didn't keep them after I stopped using the feature altogether.

 

Eva

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...