User Profile & Activity

James Member
Page
of 14
Yep, the previous WebUI registers the border-box model automatically, that's why the jQuery tab looks fine. I'm not sure, but it may be possible that you mixed up the styles previously during testing. 

If you would like to render all elements using the border-box model similar to the what the previous WebUI did, simply add the following styles.

<style type="text/css">
    html * { box-sizing: border-box; }
</style>


You'll then notice all UI elements (including the jQuery tab) to render properly now.

Hope this helps,
James.

Ah I see, ok. It seems your jQuery tab is styled according to the 'border box' model which is also used in non XHTML doctype mode.

When pre 2009 Intersoft controls (including WebGrid 6) is added to the page, the control appears to insert the css style which automatically re-style all elements' boxing to use 'border box'. This is why your jQuery tab looks good in such case.

The 2009 controls seems to be enhanced so that it won't affect other page elements other than Intersoft controls itself. I personally think that this new implementation is much better since the border box model will be applied only on WebGrid's elements without affecting the other UI elements in the page (such as AJAX extender controls, jQuery controls, etc). 

For your case, an easy solution is by simply removing the xhtml doctype definition from your page, and your jQuery tab should render properly since it was styled based on HTML style model. For a more solid solution, re-style your jQuery tabs to use XHTML box model. Alternatively, you can also add your own style to force the entire page to render HTML style model (this would be similar to the approach used in pre 2009 Intersoft controls).

Hope this helps,
James.

hi Xedem,

It seems you missed to include the styles.css. Although without the styles, I still can see the alignment issue. However, the alignment issue doesn't seem to be caused by the Grid.

I tried to remove the Grid completely from the page, and the alignment issue is still there. Am I missing something?

Posted: October 16, 2009 1:45 AM

John, do you have UAC turned off already? Also, you can try to launch the application as admin (right click on the program then click Run as Administrator).

I'm using Windows 7 x64 as well, and can run Update Manager just fine.

Posted: October 15, 2009 12:48 PM

To have better control on the desktop's background image, you can try to set the BackgroundImage property of the FrameStyle. Then, set the desired css styles in the provided CustomRules property to customize the position and repeat behavior of the background image.

Let me know if that works for you.

Posted: October 15, 2009 8:23 AM

Staffan, you may want to clear IE temporary cache if you have just updated to latest WebGrid assemblies or script resources.

If you continue to get the error, please post a simple sample that replicates the issue.

Hi Xedem, do you mind to post a simple sample along with jQuery required dependencies? Thanks!

Staffan, one more thing worth to try. 

It seems somehow the exporting process disregards the properties set at column and table level. So you can shoot directly at the group column level. For instance,

grid.RootTable.GroupedColumns[0].GroupRowValueFormatString = "[value]";

Let me know if that does the trick.

Anyhow, if that works, I'll still assume this issue is a bug since the exporting should have take account the other two level of properties (column and table). 

Posted: October 15, 2009 12:29 AM

Vincenzo,

I think that error could happen if you installed the whole product to your deployment server using the setup.

The correct way for deployment is by simply including the required assemblies to your project's bin folder, and set the RuntimeLicenseKey of the product through Deployment Manager (or set it manually in web.config). Check out this article for more information.

Posted: October 15, 2009 12:22 AM

Holger,

In addition to Yudi's suggestion above, you may also want to double check your references and make sure they are updated properly. In this case, ensure that the WebInput assembly in your project's bin folder is already using the latest version (Build 215).

All times are GMT -5. The time now is 10:50 PM.
Previous Next