StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3591963
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2010-08-28T18:36:56.293
FavoriteCount
0
LastActivityDate
2010-08-30T13:42:43.037
LastEditDate
2010-08-30T13:42:43.037
LastEditorUserId
214997
OwnerUserId
214997
ParentId
3591855
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You may not necessarily need to use postbacks, but if you want to, you need to use something called <code>delegates</code>. check it out over here: <a href="http://www.akadia.com/services/dotnet_delegates_and_events.html" rel="nofollow noreferrer">link</a> Even if you don't use them, they are useful, and will allow you to add "custom" events to your user control. <hr> Edit: Here is some code you can use: First you define your delegate type. Think of a delegate like a function pointer. You will definte this in your code-behind: <pre><code>public delegate void OnChangeDelegate(object sender, EventArgs e); </code></pre> Then you will define the actual event to be of type <code>OnChangeDelegate</code> type. <pre><code>public event OnChangeDelegate Change; </code></pre> Then you create a method (or two) which "fires" your event: (this is in your ascx.cs file) <pre><code>public void ItemChange(object sender, EventArgs e) { if (sender != null && sender is LinkButton) { string idx = ((LinkButton)sender).CommandArgument; FireMyChangeEvent(sender, idx); } </code></pre> Also <pre><code>private void FireMyChangeEvent(object sender, string index) { if (MyItemChange != null) { EventArgs e = new EventArgs(); Change(sender, new ItemSelectorEventArgs(index)); } } </code></pre> So anywhere in your codebehind, you can pass a handle to the control and some extra stuff in the EventArgs object. Now the tricky part is getting your <code><li></code> s to cause a postback. Traditionally, you would use a <code><select></code> and <code><option></code>s because of the native <code>onclick</code> event, but since you are rendering a <code><ul></code> and <code><li></code>s You might want to wrap them with an <code><asp:LinkButton runat="server"></code> so you get an event firing, instead of the <code><a href="#"></code>, so you can say <code>OnClick</code> for that LinkButton, and in that event, you can just call your <code>ItemChange</code> method to fire your control's event, and pass the id of the item which you can send in the EventArgs of your event. I would definitely recommend reading the link I sent you, and remember that unless a control has <code>runat="server"</code> your server will not have any handle on it. **Update*: Here is some more code. MY ASPX Code Note here that <code>WebUserControl1</code> is my user control and <code>MyClick</code> is the method defined in ASPX.cs code. <pre><code><ul> <uc1:WebUserControl1 ID="WebUserControl11" runat="server" OnChange="MyClick"/> </ul> </code></pre> My ASCX Code Note here that the CommandArgument is used to specify which item is clicked. Also, you can use this for a database id or some such value, I just use a simple integer ordinal. <pre><code><li><asp:LinkButton ID="lb1" runat="server" OnClick="ItemChange" CommandArgument="1">item1</asp:LinkButton></li> <li><asp:LinkButton ID="lb2" runat="server" OnClick="ItemChange" CommandArgument="2">item2</asp:LinkButton></li> <li><asp:LinkButton ID="lb3" runat="server" OnClick="ItemChange" CommandArgument="3">item3</asp:LinkButton></li> </code></pre> In APX.CS Code Note here that <code>lblResult</code> is a simple <pre><code><asp:Label ID="lblResult" runat="server" /> </code></pre> I used this just for display purposes <pre><code>protected void MyClick(object sender, EventArgs e) { int myitem = ((WebUserControl1.ItemSelectorEventArgs)e).ItemSelected; lblResult.Text = "You clicked Item " + myitem.ToString() + "!"; } </code></pre> Lastly This is the Custom Event Args class I created in my <code>ascx.cs</code> code: <pre><code>public class ItemSelectorEventArgs : EventArgs { public int ItemSelected { get; set; } public ItemSelectorEventArgs(string indexSelected) { int tryGetANumber; if (int.TryParse(indexSelected, out tryGetANumber)) { this.ItemSelected = tryGetANumber; } else { this.ItemSelected = -1; } } } </code></pre> Remember You are trapping the events of the HTML Controls inside your user control, gathering some info from them, and firing a custom event on your user control.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdding click events to user control
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USfunkymushroom
UserOwnerUserId
1. USfunkymushroom
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.