| Author |
Message |
|
|
|
Today, the new ECruiser Suite beta v 1.1.4 will be up on the site. It will include also the fix for your problem.
|
 |
|
|
|
Currently, the tree doesn't support this behavior. We will consider this for future.
|
 |
|
|
|
This fix will be available next week, when we'll have a maintenance release. Thank you for your interest in our components.
|
 |
|
|
|
In this case, it is recommended that you use immediate="true" at menucell's level. In this way, you control page flow through navigation rules while bypassing validation.
|
 |
|
|
|
We will have a maintenance release until next week, so you could use this fix in your presentation.
|
 |
|
|
This issue will be fixed in our next maintenance release.
Thanks for your interest in our components.
|
 |
|
|
|
This seems to be a bug in our code. We will fix it , and we will send you a patch soon.
|
 |
|
|
mattwestbright wrote:
Hi
Does Ecruiser Suite v1.1.3 beta work OK with Microsoft Internet Explorer version 5.5 ? or do you specify a higher version as a minimum ?
We are seeing some javascript errors in IE 5.5 at work (to do with "this.domName.nodeName" from memory; I'm at home now). I've no idea what file it's in, just I'm fairly sure its not in our own code. We don't see the errors in Firefox. Unfortunately the client will not be upgrading IE any time soon.
Thanks
Matt West.
The ECruiser Suite v1.1.3 was tested with IE 6.0 and 7.0, and not with IE 5.5. You can find informations about supported browsers and servers at http://www.simplica.com/learn.htm ECrusier Getting Started Guide.
|
 |
|
|
Hello,
You can find our release notes at /ecruiser-suite-v1.1.3-beta.zip/ecruiser-suite-v1.1.3-beta/doc/release_notes.html
Regarding readme.txt file, we assume that mistake, but you have to know that the specifications are right for all ECruiser versions.
Thank you for your interest in our components!
|
 |
|
|
|
We couldn't reproduce this problem. Please, send us the .jsp and .css or a simple application that demonstrates this issue on support@simplica.com. In this way, we can help you easier.
|
 |
|
|
This is a label issue, not a content one. We assume this mistake, and we will take care of that in our next releases.
Thank you for your feedback!
|
 |
|
|
liji wrote:
Thanks adina. I purchased the datatable on 10-18-2006, does it qualify for an upgrade or do I have to purchase the upgrade?
Your license key allows you to use only dataTable and it's subclasses (selectTable and gridTable).
If you want to use all of our components, then you should purchase a license for the Suite.
Please, send an email to sales@simplica.com with your DataTable order number and contact details, to learn about upgrading to the Suite.
|
 |
|
|
The percentage width is now implemented in our code, which will be released in about one week.
Thank you for your interest in our components.
|
 |
|
|
Your problem seems to be a particular one. It might be caused by following situations:
[list] Somewhere in the project is a different version of the commons-
logging files and this mis-match is causing the problem;
[/list]
[list] Somewhere else in the project is the same version, but they are being
loaded by different class loaders and this makes the Log class look like a
different class to SimpleLog.
[/list]
The commons-logging files are used in our source code, so they must be in there in a way or another.
|
 |
|
|
Hello!
With the current version of dataTable, the solution is to add a custom TR and hide the top row.
The .jsp page look like this:
In a future release, we plan to provide a easier way to do this directly within the column definition.
Adina Mihai - Simplica Support Team
|
 |
|
|