Hello,
New design of My CLient.net home page is nice and we can see top 5 of forum posts, blogs, My support tickets & .... but i think it's very good to add show more... to buttom of these top 5 lists.
Excuse me english isn't my native language.
Best regards
Mostafa Anoosheh
I have a RadWindowManager which consists of 8 RadWindows It is working fine in page load, i have an image button in the same page to download a .pdf file, I can download the .pdf file or cancel it based on the user's wish.
Once i save the .pdf file or cancel the download and again if I try to open the radWindow, it is not getting opened.
If i click that image button and then open the radwindow,it is not working.
Maybe this is a bit off-topic, but thats why we have this 'Miscellaneous' forum, right?
I've a question about when and how to save data before the Postback occurs...
I've a page called Default.aspx. On this page I use a Tabcontrol with a Multipage control. When the Default.aspx page loads, the Tabs and PageViews are dynamically created based on data inside a table.
Also, the active PageView loads a UserControl (Question.ascx) that filters data based on the selected tab.
I want to save the data inside the Question.ascx when a user clicks another tab, because the content of a PageView is gone on each postback, I MUST save the entered data before this Postback occurs... What event on either the Usercontrol or the Page must I use to save the data before the postback?
If I click on a tab, the postback allready has occurred.
I'm the kinda guy who, given enough time, would build his own car. So, I ask, Why tools? Why not build it all from scratch? Like when all we had was CGI-Perl. Or like ASP 3.0.
Maybe it is a control issue. Knowing exactly what is happening under the hood gives me warm fuzzies.
But, I'd like to hear from other developers who have found a justification for tools. How you have integrated them into your own coding. I don't think I'll ever adopt an all tool approach. I require too much customization.
Don't get me wrong, I'm not anti-tool. I can see an advantage to dragging and dropping. I just remember the junk that hit the streets when MS Visual Basic 3.0 hit the ground.
I just have a question: what is the secret of such a good support system? Is it the the ticket-system? Then you should sell it as a product :) Is it the people who work for the company? Then they have a big heart for Telerik...
I was just wondering why some software companies (or others) are just so un-friendly and let you wait such long times...
Well, just letting you know that you are a fine - full of support - company.
Any others who have good tips for setting up a good support service?