Hello Dave, It's possible the code isn't being called. A simple (very temporary) way to check that would be to put an alert('here'); into the beginning of the getLocation function and see if it displays when the page loads. If it's not being called then we'll need to find the suitable location for i...

Hello Dave, Here's a workaround that will hopefully resolve the issue. It has been tested on table located Charts but not within a WebUserControl/Webpart (we'll get to that check but it requires more setup time). We'll internalise this code in the next maintenance release if all tests checkout. The ...

Hello Dave, This may be related to the x,y location as you've pointed out. I haven't checked it in a Sharepoint page yet but I suspect the cause is similar to a problem we're looking at for a Chart located in a table. Default behaviour on a WebForm is via absolute positioning of objects, that return...

Hello, We're still not able to reproduce the problem on the english windows test machines here. For tests we have thoroughly cleaned-off installed teechart versions as you have described and closed the v6 test page before running the v7 page. Are you checking that the registry settings for TeeChart ...

Hello, We haven't yet been able to reproduce the DAX error following the steps described and the test pages linked in your post. Tests run on - IE v6.0.2800.1106 on Win2000 (English lang) - IE v6.0.3790.1830 on Win2300 (English lang) Please could you confirm browser operating system versions and let...

Hello Fred, I'm not immediately sure what the problem might be. TeeChart isn't a Windowless Control so I wouldn't have expected the error message. Do you get a similar error message if you open (and close) one of the TeeChart example projects for .NET ? What kind of project should we build here to t...

Hello Gabor,

Thanks for the problem report. The problem is caused by Javascript generated by TeeChart for the page and not compatible with Firefox requirements. We'll correct it and publish the fixed version very shortly.

Regards,
Marc Meumann

Hello Mateo, Here's an example of useage. It's not very intuitive so we'll make sure to add this or a similar example to the documentation. private void button2_Click(object sender, System.EventArgs e) { Steema.TeeChart.Editor editor = new Steema.TeeChart.Editor(tChart1); editor.HelpFileName="myHelp...

Hello Matteo,

Yes, thanks for pointing that out, it's incorrect. We'll correct the documentation for the next update.

That should be:
Regards,
Marc Meumann

Hello Daniel, Thanks for sending through the example. In this particular case the DLL, ClassLibrary1, provides designtime functionality for use by the Windows application, WindowsApplication1 (ie. to allow it to be used in VS.NET and to be designtime compiled). A TeeChart DesignTime License should t...

Hello Daniel, The physical license used by TeeChart derives from Microsoft's System.ComponentModel.LicenseProvider class and is intended to prevent the use of TeeChart at designtime without the presence of the license. As your DLL offers TeeChart to a designtime environment then the physical license...

Hello Alex, It is unlikely that the ColorGrid Series might receive the kind of colour banding modification described in early stages of its development, as the Series, although similar to Surface in some respects, does have an extra level of complexity that makes it difficult to generically apply a ...

Hello Alex, I don't think we'll be able to offer you a short term solution for the colour banding requirement. We'll take a look if there is a modification we could make to the Surface Series for a future version. Please note there is a Surface property called Irregular Grid that is designed to help...

Hello Terry,

It wasn't there! Sorry. It's now on the customer download page. Accessible via:

http://www.steema.com/downloads/client_access.html

Regards,
Marc Meumann

Hello, With respect to the sample included a couple of posts ago, TeeChartLicense.zip. The setup is slightly different to the one we tested earlier in the thread. We set it up for a closer look. In this particular case, because the final development project is a .NET project, not VB6, then the licen...