User Profile & Activity

Bernard Xiang Member
Page
of 52

Hi,

Could you try to clean install our product and please also ensure if your assembly in your project's bin folder is the latest one? This might solve your problem regarding the reference to 2012 product. You could also find the WebCombo Hotfix in this thread:

http://intersoftpt.com/Community/WebCombo/webcombo-and-firefox/

You could apply those hotfix in your program files and in your project to fix the WebCombo Rendering in Firefox.

However, I could replicate your issue above. If possible, could you lead me with steps to replicate this issue in my local end? Please also ensure if you're using the right doctype which is HTML5 doctype and the right rendering mode in our control. It will prevent the error in your page. Hope this helps.

Regards,
Bernard

Hi Oliver,

I will follow up our developer team to deliver this hotfix at the end of December. I will also let you know if this hotfix has already available. Sorry for this inconvenience. Hope this helps.

Regards,
Bernard

Hi Oliver,

This issue is still on our queue. I will ask our developer team and move this issue as critical issue. I will let you know if I heard any news regarding this work item from our developer team. Hope this helps.

Regards,
Bernard

Posted: December 11, 2013 10:59 PM

Hi Frank,

I think it would be better if you uninstall the WebScheduler 3 first then you can install the newest WebScheduler 4 in your development environment. With this method, you won't get any wrong references to WebScheduler 3 instead of WebScheduler 4 in your project. But you can install both of them in your development PC. You can get our trial by visit our website at: http://www.intersoftpt.com/RequestTrial or by you can contact our sales to get special offer or interesting price at martin@intersoftpt.com. Hope this helps.

Regards,
Bernard

Posted: December 11, 2013 10:47 PM

Hi Roi,

Yes, I think it should have done automatically just by using ShowDialog(). But I think there is some API that our user inherit from our WebDesktop that cause us to search a different level object for rendering different size on WebDialogBox. However, I will add you suggestion to our developer team so they can consider this scenario in the future. For your information, you can see all of our client side API reference on our Documentation in Client Side Reference section. Hope this helps.

Regards,
Bernard

Posted: December 10, 2013 9:27 PM

Hi Roi,

I can replicate your issue here. However this problem appear because it has create the object at client side when showing for the first time. You could change the size value by changing its Window after it has the Window value. Here's the code:

function WebButton1_OnClientClick(controlId, parameter) {
    var WebDialogBox1 = ISGetObject("WebDialogBox1");
    if (WebDialogBox1.Window == null) {
        WebDialogBox1.Height = "200px";
        WebDialogBox1.Width = "400px";
    }
    else {
        WebDialogBox1.Window.ResizeTo("400px", "200px");
    }
    WebDialogBox1.ShowDialog();
    return true;
}

When initialize the Window attribute will be null so the height and width will refer to WebDialogBox' Height and Width and it will refer to window object when it has been initialized. Hope this helps.

Regards,
Bernard

Posted: December 10, 2013 9:13 PM

Hi Roi,

I think you could validate the session when flypostback in Page_Load event.

protected void Page_Load(object sender, EventArgs e)
{
	if (IsPostBack)
	{
		//you can validate the page session in here and call the response from here
		WebButton1.ClientAction.InvokeScript("Redirect()");
		WebButton2.ClientAction.InvokeScript("Redirect()");
		WebButton3.ClientAction.InvokeScript("Redirect()");
		WebButton4.ClientAction.InvokeScript("Redirect()");
	}
}

Page_Load event will be called during postback in postback cycle. It will be better if you put the validation in there. However, when doing flyposyback the page need to get the responses from Server side. With the method above, the javascript will be called right after the response has been by the page. Hope this helps.

You can download the file from my SkyDrive here: https://skydrive.live.com/redir?resid=F226E4DAA368F2A6!317&authkey=!AFYTwg_yj77uUYk&ithint=file%2c.zip

Regards,
Bernard

Posted: December 8, 2013 9:48 PM

Hi Roi,

I think there are no other way than redirect the page using InvokeScript method that you mentioned before. Perhaps, you doesn't need to check it in all OnFlyPostback event of our control that you used in your page because you could add this validation on Page_Load event. Everytime our control do Flypostback, it needs to return the parameter to its page. So it will be better if you redirect the page in client side because it won't bother the FlyPostback mechanism to return the parameter.

I also attach my sample here. Hope this helps.

Regards,
Bernard

Posted: December 5, 2013 11:51 PM

Hi Roi,

Sorry for my misunderstanding. I think the response.redirect only can be used when you are in fullpostback mode. However, you could achieve this scenario in client side. In OnClientClick you could request the session in server side and save it to a hidden field in your page. Then using window.location attribute, you could redirect when the session is over. To get this session in server side your could use our WebFlyPostBackManager or you could do Ajax request to server. Hope this helps.

Regards,
Bernard

Posted: December 3, 2013 9:07 PM

Hi Roi,

I think you could do this scenario with session timeout. However, you should check this session on Page_Load event because it will call Page_Load event even when the page do FlyPostback. You can check if the session still available and redirect it to login page when the session is over. Also, you could do flypostback method from client side to request the session in server side. You can also redirect the page in client side. Hope this helps.

Regards,
Bernard

All times are GMT -5. The time now is 3:47 AM.
Previous Next