iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Hi,
I have sent an email and mark it as important item for your request. I will keep follow up your issue to our developer daily.
Regards,Handy
Hello Sayuri,
It works fine when I add the column. Besides, the sample does not show ColumnSet sample.
Hello Raja,
I haven't received any news about this.Btw, I have told you that we cannot promise to make this fix since you were using the old products which has discontinued. Even though there are changes in framework level, I am not sure if our developer agreed to change or modify the code. The framework code level should change due to the growth of latest control. That means it could not be reverted back or changes easily based on old product.If the changes are major or took much effort, we would consider to drop it.That's why there is no guarantee for the old products.
Hello,
As I said before, it is not a bug. It is a different behaviour rendering in HTML and XHTML. You would need to adjust the style.Here, I show you the prove about white space below WebGrid control.I made 3 divs in simple sample (default.aspx) to show you that I can replicate the same problem without WebGrid.If you put <p> in the bottom <div>, you will able to see the white space. If you open in HTML doctype, it works well. That's because HTML and XHTML has some differnces behaviour in rendering its element and style.Or, try to remove <p> in BrokenPage.aspx. You will see that the white area at the bottom grid would be dissapeared.To remove the white space, simply set padding and margin to 0 in your <p>.
However, about the resize issue when resize the page, it might be an issue.When you resize the page, WebGrid should automatically resize based on the screen.However, sometimes, the resize got stuck by time out and not functioning properly.In this case, we would like to call wgDoResize(true,true) with timeout in window::onresize.WebGrid would resize when called this code.Based on your scenario, I am able to resize WebGrid when resize the screen. But I found one issue. The height is not resized. I would need more time to discuss this issue to our developer teams.
After further investigation, unfortunately, this is not a bug from ours.
The problem are located in diferences rendering behviour between HTML and XHTML.
Therefore, you need also to customize the style when inside XHTML page.
e.g
I modified your sample and customized the style. Now, it looks similiar to HTML page.
I also send you the comparation between HTML and XHTML with WebGrid stand alone in the page.
You can see that with style customization, it works fine. Please see the attachment.
Regards,
Handy
Hi Eric,
There is no much detail information about PreRender event. I will try to ask our developer regarding this information. For information, you can see our WebGrid server side sequence life cycle in our documentation (Features and Concepts>>Events>>Event sequence of server side event).
Hello Pendry,
You can see those files in our WebGrid sample>>App_Code>>dsNorthwind_extended.cs.The sample that used that method is ClassicPagingUsingCustomDataRetrieval.aspx.
Let's me explain the behaviour and logic in this code snippet.
1. Here is the first load.
At first, startRowIndex would start from 0 and maximumRows would start from 25.In this case, startRowIndex and maximumRows are handled automatically by WebGrid.In this sample, the paging size is left as default, which is 25. That's why maximumRows is 25.startRowIndex starts from 0, means that WebGrid is still in page 1.You can see the query details in the image.
2. Here is what hapenned if we navigate into the second page.
When you navigate into the second page (or maybe others page), startRowIndex would start from 25.As I said before, WebGrid handled this automatically. The number page increased into 2 which would show the next startRowIndex based on your paging size.
3. If you do sorting during this scenario, you can also see that it will load based on your sortExpression which is also handled by WebGrid automatically.
For your information, all those paging are using ISDataSource.If you don't want to use ISDataSource at all, you can your own query at InitializeDataSource event.E.g in our WebGrid Tutorial>>V 3.5>>CustomVirtualLoad.aspx.It is using VirtualLoad as its paging mode.
Here is the reason why it is not said as bug.
When postback, it’s too early because the columns are then overridden with the setting which is sent from the client-side. That’s why Column D is gone.
To address this issue, there is others workaround.
Private Sub InitializeColumns() Const cDataWidth As Integer = 80 AddHiddenGridColumn(grdUpper, "Upper_Id", "Upper_Id") AddHiddenGridColumn(grdUpper, "Upper_Parent_Id", "Upper_Parent_Id") AddGridColumn(grdUpper, "Description", "Description", "Description", cWidthUpperDescription) AddGridColumn(grdUpper, "A", "A", "A", Nothing, Sorting.Yes, Nothing, cColorLeft, HorizontalAlign.Left, cDataWidth) AddGridColumn(grdUpper, "B", "B", "B", Nothing, Sorting.Yes, Nothing, cColorLeft, HorizontalAlign.Left, cDataWidth) AddGridColumn(grdUpper, "C", "C", "C", Nothing, Sorting.Yes, Nothing, cColorLeft, HorizontalAlign.Left, cDataWidth) AddGridColumn(grdUpper, "D", "D", "D", Nothing, Sorting.Yes, Nothing, cColorLeft, HorizontalAlign.Left, cDataWidth) grdUpper.RootTable.DataKeyField = "Upper_Id" grdUpper.RootTable.SelfReferencingSettings.ChildDataMember = "Upper_Parent_Id" grdUpper.RootTable.SelfReferencingSettings.Enabled = True grdUpper.RootTable.SelfReferencingSettings.ParentDataMember = "Upper_Id" grdUpper.RootTable.SelfReferencingSettings.ExpandColumnMember = "Description" grdUpper.RootTable.SelfReferencingSettings.LoadOnDemand = False grdUpper.RootTable.SelfReferencingSettings.ApplyChildSorting = True End Sub Protected Sub grdUpper_Init(ByVal sender As Object, ByVal e As System.EventArgs) Handles grdUpper.Init If (Not IsPostBack) Then InitializeColumns() End If End Sub Protected Sub grdUpper_Load(sender As Object, e As System.EventArgs) Handles grdUpper.Load If IsPostBack Then grdUpper.RootTable.Columns.Clear() InitializeColumns() End If End Sub
Of course there has been some progresses in this issue. Our developer teams has been fixed some issue about this auto height. But it has not fully worked as expected yet. Please give us a little time and we will deliver it for you when it's fixed completely.
I have forwarded your feedback to our developer. I will update to you when there is a progress regarding this issue or not.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname