If they are choosing their own UI, I am assuming they will want to retain
these settings beyond this session?
In that case you would store in either a data store (xml file on server, db
on server) or client cookie
While they are choosing, you can store the interim decision points
(rows/cols counts) in a session variable and call from a postback, so on
each page load it will
1) check if there is stored data setting the UI, and if none, then
2) check if there are session variables indicating they are mid-process in
choosing their ui layout , and if none, then,
3) display the starting point for laying out their ui (two textboxes).
It sounds like you are using events to create the table based on the
textboxes and/or the button on click, but are not retaining the information
between postbacks.
Hope this helps. If you need some code examples, post relevant code
snippets to your question - makes it easier to make the answer more
relevant. :)
"Sachi" <Sa***@discussi ons.microsoft.c om> wrote in message
news:79******** *************** ***********@mic rosoft.com...
Hi,
I am looking for a optimized design for my problem.
Purpose : Need to give a UI where user can select the layout they want.
Initially we also need to give them one possible way to define rows and
col. So I am providing two textbox to get this. After based on row and col
i
am generating a table. In which each TD will be showing dropdown to select
which usercontrol to be load in different TD, which need to be stored in
database.
Now I am able to build dynamically a table with dropdown in each TD. But
now comes the issue of persistance. Once user selects usercontrols from
different dropdown , will click the button SAVE. By then all the contents
goes off. I tried various persistance methods. But no success soo far.
Finally looking forward for some experts view. Well, there is a better
solution for this please let me know.
Thanks in advance,
Sachi
