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
AFAIK, it can't be implemented, because "Popup" is never introduced by W3C, and hence standard browsers like FF, Safari, Chrome - won't support it. The "Popup" was a proprietary implementation by Microsoft alone since IE 4.
I also suggest you to use "Normal" window type whenever possible, even for IE for consistent display result across all browsers.
Hope this helps.
Xedeem, only Internet Explorer browser supports "Popup" object that can be displayed out-of-browser. When used in other browsers such as Firefox, Safari, and others, WebCombo will fallback to normal window type automatically.
Michael,
Please note that only framework assemblies should be put in GAC, so product assemblies such as ISNet.WebUI.WebGrid.dll and all *.Resources.dll shouldn't be in GAC.
If you have SmartWebResources registered properly, the JS files should be loaded without issues. Since you mentioned that "IS" is undefined, most chance is the JS files failed to be get loaded.
Could you inspect further by using HttpWatch and see the response of the ISRes.axd request?
You can use row object model to perform the selection. It's much easier, and more elegant.
Example:
var grid = ISGetObject("WebGrid1"); grid.RootTable.GetRow(0).Select();
Hope this helps,
James.
Memo, okay, it seems I used a wrong sample to test your scenario. It's true that multiple whitespaces are removed automatically by HTML (browser) and rendered as a single whitespace.
However, you can request this feature to Intersoft by submitting this request to their product feedback in Developer Network.
AFAIK, all ISNet assemblies should remain in GAC for designer, editor, wizard and other use in Visual Studio designer. Re-adding the dlls to your project should resolve the problem.
The references refreshing is required because new installation updates only the assemblies in the program files which would be automatically consumed for new projects. However, the new installation won't affect your existing projects, so you still have to refresh your project references manually after fresh installation.
Another note is, if you have proper references with auto refresh file, you can easily update the references by right click on it, and then choose Update References, or you can do "Rebuild Solution". However, note that this will work only if your references are properly pointed to the original files path (not pointing to bin or other places).
Yaniv, I'm glad your issue is resolved. Would you mind to share your steps to resolve? That'll be helpful for others who also running on the same issue.
Thanks,James.
Memo, what Grid version do you use?
Please make sure that the Framework assemblies have been updated properly in your project. If you're using SmartWebResources, make sure all *.Resources.dll are updated. The resources assemblies should match the component assembly version.
Michael, yes, definitely. Otherwise, your keys would be locked up and unavailable to use in the next installation.
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