>>But I found solution to my problem (from a message on Stackoverflow). What I needed to do is following: Enable all button at design time. Then disable those that need to be disabled in jQuery (in script). This way the post back (or no post back) that I set up at design time work.
>
>Glad you got it working - but it occurs to me that if neither button should ever initiate a postback then it would be better to use a simple HTML input control rather that asp:Button in the markup so that the problem doesn't arise. i.e:
<input type="button" id="button1" value="One" />
Very good point. I kind of forgot that you can use plain HTML input instead of aps:button. The only thing I am thinking right now is in this case I have 4 buttons (centered on the page). And 3 of them don't need to post back but one does. I want to be sure that they all have the same "look and feel.". Will having one as asp:button and others as html buttons affect it?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
