i am using asp.net with c# web app in vs 2008
problem 1:
i do not know why Telerik RadControls- RadFormDecorator Moves some controls (such as Buttons or chech boxes) and changes their positioning up or down in my form after viewing in browser...
i put those controls in a cell of a table ... but not help
i had this problem about radajaxmanager and by setting UpdatePanelsRenderMode property to inline problem solved - but here there is no property like that...
what is going on here?
problem2:
i decorated my buttons and chechboxes with radformdecorator (telerik radcontrols) control...
when i click on a checkbox to set it to true or false so my webpage positioning goes to up (like when postback occurs , but this is not postback)
how can i prevent this problem ?
thanks for attention
This happens in some scenarios because of the way RadFormDecorator styles checkboxes - real checkboxes are hidden outside of the viewport. When the decorated checkbox is clicked however, browsers try to focus the real checkbox, hence the "jumping". To avoid that, you should set position:relative to the parent container.
Related
I have a problem: I am using devexpress wizard control and want to toggle visibility of wizardpage on the basis of a checkbox input.
Problem:
If suppose checkbox A is checked then wizard page X must be visible while going to and fro in wizard control else page should not be visible.
What I have tried:
tried to toggle visibility in SelectedPageChanging event - didn't get success
tried to add or remove page from parent control - didn't get success
Please help me out in this..
You could:
handle the SelectedPageChanging event.
Check the Page property of the event arguments is the page right before the page to show/hide.
If true, set the Cancel property to true.
Set the SelectedPage to your desired page, depending on your checkbox A's state.
You could also optionally theck the Direction property to see whether the user is navigating forward or backward.
General hint:
When dealing with DevExpress questions/issues, the DevExpress Support Center always was the most useful location to ask my questions or browse for solutions.
Even Stack Overflow cannot compete with there speed and depths of anwsers (IMHO).
So if my answer (or the other answers) do not satisfy your need, I would recommend that you go to the Support Center and ask there for advise.
I got this from devexpress below is the link for the same
How to prevent a specific page from being activated
I am working on .net 4.0 application. I am trying to load a bunch of custom controls that has a "gridview" control along with several text boxes and dropdowns. As the viewstate is really slowing down the system in order to improve the performance I Disabled the ViewStateMode of the parent control (i.e User control) and Enabled the ViewStateMode for dropdowns. But the problem I have is the dropdowns inside the gridview and panel thrw an error even though their ViewStateMode is Enabled. If I Enable the ViewStateMode of gridView or Panel it works fine but that's increasing the size of Viewstate.
Can somebody please make me understand why it is happening and what is the solution for this?
Thanks
BB
If you are getting tons of viewstate.Then I would suggest you two ways that worked for me too
Compress Viewstate - http://www.codeproject.com/KB/viewstate/ViewStateCompression.aspx, http://www.hanselman.com/blog/ZippingCompressingViewStateInASPNET.aspx
Trace the layout of the rendering area in html, using div , ul, li wahtever. Now instead of placing grids and other server controls, get the datasource(datatable or dataset), itereate through the items and make the html in the codebehind and write the final html tag on page using a literal. using html controls you can get rid of the view state issues. Also on that html tag you can apply jquery to make it better too.
I have a custom control that has an update panel in it. Within the update panel, there are no custom controls, but there are custom controls outside the update panel. All controls have an ID set as do the parents of the controls. Inside the update panel is a repeater that has controls that should trigger an async postback. The update panel has an update mode of conditional and children as triggers is off. The update panel renders standalone divs, not table cells. EnablePartialRendering is on on the script manager.
Each repeater item has numerous textboxes, but two of them have autopostback turned on. Inside the repeater ItemDataBound event, I register the control with the script manager's RegisterAsyncPostBackControl.
If I edit either textbox, it does a callback correctly. But after the first one is edited, if you edit the other one, it does a full postback. It doesn't matter which one is done first. But after it's done its postback, if you edit either of the textboxes, it does callbacks correctly.
I've tried several things like changing the UpdateMode and ChildrenAsTriggers properties to various combinations. Nothing seems to work.
Any suggestions?
A lot of things can cause this, compare UpdatePanel causes full page postback with LinkButton in ListView in UpdatePanel causes full postback.
You'll need to provide more information, e.g. .NET Framework version, IIS version etc. exact ASP.NET markup etc
But since you asked for "Any suggestions?" try looking through these questions
I've come across the strangest bug pertaining to DataGridViews in Windows Forms.
I have a TabControl, that is supposed to contain a docked DataGridView in each tab page. I thought it would be convenient that the grid is focused upon changing the tab page, so that the user could simply hover the mouse over the grid and start scrolling when he changes the page. So, I just put a grids[tabs.SelectedIndex].Focus() in the event handler for changing the tab page.
However, something really strange happened. In my test application, I have three tab pages. If I try scrolling the grid right after starting the application, it doesn't work; I have to click in the grid first. I was expecting this. However, if I change the tab page, I can't scroll in any of the other grids until I click, except for the first one!
So, if I switch pages to the second page, then back to the first, I can automatically scroll that grid without clicking, but if I then switch to the third, I have to click for the grid to focus.
I had a look at the CanFocus properties of the grids, and it seems that only the first grid has it set to True. They are all created programmatically, and all in the same way. I don't see why they would be different.
Any ideas?
Inactive tab pages have their Visible property set to false. The documentation for CanFocus says:
In order for a control to receive
input focus, the control must have a
handle assigned to it, and the Visible
and Enabled properties must both be
set to true for both the control and
all its parent controls
Well, I solved it. Stupid programming error on my part, I had grids[tabs.TabIndex].Focus() instead of grids[tabs.SelectedIndex].Focus().
Oh well.
I have 2 identical AutoCompleteExtender's - one is in the Insert mode of my DetailsView, which is the default mode, and one is in the Edit mode. There is also another DetailsView, which only shows when a Checkbox is ticked (and the page posts back), which also hides the previous one.
When the mode is Insert, there are no issues at all, even when ticking the checkbox to hide the DetailsView with the AutoCompleteExtender in and show the other one (which has no AJAX controls btw). But when the mode changes to Edit, and the user ticks the checkbox to change to the other details view (with no ajax), I get this error:
Extender control 'autoNom' is not a
registered extender control. Extender
controls must be registered using
RegisterExtenderControl() before
calling RegisterScriptDescriptors().
Parameter name: extenderControl
Any ideas guys?
Thanks
The problem is not with the other DetailsView. Try deleting the extender for the edit mode and and configure it again. Because it looks like there is something with the Ajax config in the edit more. Make sure about the namings.