User Profile & Activity

Handy Surya Support
Page
of 223
Posted: March 25, 2011 5:29 AM

Hello Raja,

Yes, Our developer would like to see the possiblies first to decide. For your information, maybe some of the code could not be changed due to our mechanism in our latest product. But we will try our best.

By the way, do you mind to use build 703 in order to run the project temporary?

Regards,
Handy

Posted: March 24, 2011 8:57 PM

Hello Eric,

I don't say it is normal or not. But it might happen since you used Page_Load for your DataBinding. Using InitializeDataSouce event is the correct and the best way for the databinding. 
I suggest you to read "Event sequence of server side events" in our documentation to understand our WebGrid behaviour. 

Regards,
HAndy

Posted: March 24, 2011 2:22 PM

Hello Eric,

It's true that by design, All binding should be handled in InitializeDataSource event. You can also bind at Page_Load. But sometimes, it can return unexpected result such as no data return in "some condition and scenario", "get some random unhandled error", or even incorrect random data load.

Regards,
Handy 

Posted: March 24, 2011 7:33 AM

Hello,

As far we checked your code, it seems you did not bind WebGrid in proper event. Sometimes, this can return unexpected result. Please use your binding code in InitializeDataSource event instead of PageLoad.

Regards,
Handy

Posted: March 24, 2011 5:43 AM

Ok, Thank you for your understanding. We will investigate this issue. 
For now, you can read our online documentation from
http://intersoftpt.com/Support/ClientUI/Documentation/

Or, offline documentation from
http://intersoftpt.com/Support/ClientUI/ClientUI.chm

Regards,
Handy

Posted: March 22, 2011 10:27 PM

Hi Raja,

In your project, it used CommonLibrary for scripts and images. However, we don't have a property to turn off the script, except for WebResources.
Also, I think it is not possible because all Intersoft control needs its Framework in order to run. 
Currently, even though our developer can fix this in Framework level, it cannot be done quickly (asap) due to the tight scheduler of release. I suggest you to use build .703 which works fine before.
If you don't have any backup of build .703, I can send it to you.

Regards,
Handy

Posted: March 22, 2011 9:45 PM

Hello,

We are planning to release at the end of month. FYI, I attached a nightly build (disclaimer:on). This hotfix has not been fully tested (not official). We are glad to receive any feedback regarding this hotfix. Hope this helps you to continue your development process.

Regards,
Handy 

Posted: March 22, 2011 6:48 AM

Hello Michael,

I just want to confirm if attached screenshot is the error you faced or not. If not, please send me your error screenshot.

Regards,
Handy

Posted: March 21, 2011 11:24 PM

Hello Raja,

My point is:

It might be not possible to fix in Framework level since maybe the code is needed for our latest enhancement or fixes.
In this state, this means the old product does not support the latest Framework anymore.
We also would not do some fixes in old product since it has discontinued.
I can try to discuss with our developer teams to ask if the framework still can be enhanced or not. But I could not promise anything.

The best approach or solution is try to downgrade your current Framework into the older Framework which works well previously.

Regards,
Handy

 

Posted: March 20, 2011 10:45 PM

Hello Raja,

Yes, we do understand about the issue. It seems some changes or enhancements in our framework maybe cause this issue.
However, we need to see the posibility if it can be changed or not  because some changes or enhancements are very important to us.

As you mentioned in your first post, you have WebGrid 6, WebCombo 4 and WebInput 3.
Currently, WebGrid 6 and WebInput 3 are the old product. We have discontinued support/hotfixes for this product.
Just for your information, while WebUIFramework keeps growing and changing due to development, soon or later all the old products would become obsolete. In other words, the old product would not compatible with our latest framework soon or later. That's why we suggest you to upgrade into our latest version.

If your work are very important for now, we can help you by sending the previous version of Framework which compatible or works fine with your current product.

Regards,
Handy

All times are GMT -5. The time now is 7:23 AM.
Previous Next