Search

You searched for the word(s): userid:807355

Matching Posts

  • Re: Instructions for using the TreeView adapter

    Hi Russ What´s the point of creating alternative event handlers? Why not just use the existing ones? Shouldn't one of the goals of a control adaptor be to not alter either the base control's functional behaviour or it's API? That way it makes it easier to plug the adaptor in to existing projects that use the control without having to rework them.
  • Re: When MenuItem.NavigateUrl is not set the MenuItemClick event isn't fired!

    As you say, the Menu control is supposed to post back when the NavigateUrl property is not set (see http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.menuitem.navigateurl.aspx ). However, when it is bound to the SitemapDataSource, the Selectable property of an item with no NavigateUrl is set to false, and no postback javascript is generated. This is not to do with the adaptor. If you do a simple test with the normal "unadapted" control, it does exactly the same. But, if
  • Re: StaticDisplayLevels and MaximumDynamicDisplayLevels

    Nice work turkoid, I was needing this too, and your post saved me a lot of time.
  • Re: Stored Procedures w/multiple resultsets in DataSet Designer??

    Hi Eddie, It´s a long time since you asked the question, but I had the same problem and think I have found the answer. I thought I´d document it here in case anyone else needs it. Basically, the TableAdapter functionality of the Dataset Designer (in VS 2008 at least) is limited to only support a single table, as you suggested. The underlying reason is that the TableAdapter calls the overload on the DataAdapter.Fill method that accepts a DataTable, not a DataSet (see http://blogs.msdn.com/vsdata/archive
    Posted to Visual Studio 2005 (Forum) by dotcomsoftware on 11/11/2008
  • Re: Stylesheet Question

    [quote user="dotcomsoftware"]When I remove the link to the basic styles in the source code project, I don't notice any difference in appearance or behaviour... have I missed or misunderstood something?[/quote] OK, I see it now, you're using embedded stylesheets, so the link from the page to the .css is not necessary. I suggest removing those explicit links in the pages and highlighting somewhere that you are using embedded css definitions so as to avoid confusion.
  • Re: Thoughts on version 2 of these adapters

    [quote user="dotcomsoftware"]The same goes for other properties such as StaticDisplayLevels. [/quote] By the way, the reason I mentioned this property is so that the menu can be used with the SiteMapDataSource. Sitemaps only allow one root element, conventionally the site home page. Displaying just a single menu item for the home page is usually not enough; normally you want to display the second tier of links as well. To achieve this with the Menu control, you set the StaticDisplayLevels
  • Stylesheet Question

    A question about the stylesheets. There appear to be two sets: one that provides default functionality, the other providing "theme-related" styling. Am I right in thinking that the intended implementation is that pages using (say) the adapted Menu control should link to the former styles as well as the "theme" styles? When I remove the link to the basic styles in the source code project, I don't notice any difference in appearance or behaviour... have I missed or misunderstood
  • Missing .vsi file?

    Anyone know where the .vsi file has gone for this project? All the links seem to point to an MSDN library page at present, with no sign of the file itself.
  • Re: Thoughts on version 2 of these adapters

    This is a great initiative, a much needed project. Can't see why Microsoft don't just bite the bullet and generate css friendly code though. I agree that the adapters shouldn't issue hard-coded class names on the elements that they generate. But rather than use the configuration file, why not use the original control classes? An adapted control is supposed to use the same semantics as the original control. For example the Menu control has numerous properties to allow you to specify class
  • Re: Help: Master page middle column got deformed by a GridView in the content area

    Set the GridView width to 100%. It should limit it's size to the width of the container (ie. your middle column). Better still, set the CssClass properties to a CSS classname that defines the widths instead of using control property settings.
Page 1 of 3 (24 items) 1 2 3 Next >