Upgrade from 8.5.1.1 to 10.3.2.2 problems

A forum dedicated to WPF version of LightningChart Ultimate.

Moderator: Queue Moderators

Post Reply
MirroZV
Posts: 45
Joined: Wed May 13, 2020 10:41 am

Upgrade from 8.5.1.1 to 10.3.2.2 problems

Post by MirroZV » Mon Nov 28, 2022 7:14 am

Hello,

we are trying to upgrade LightningChart form version 8.5.1.1 to version 10.3.2.2 but we have some problems with that. We tried that year before

viewtopic.php?f=16&t=2611&sid=4ee42cc19 ... 25266cfe89

and per your advice waited for newer version. Now it seems like, we should not wait any longer, to have proper support for windows 11 for our customers. We have prepared brief list of main issues, with attempted workarounds, and also demonstrator app of this issues called ChartControl (wrapper around lightning chart we used in our application). We have prepared two version of it, one with LightningChart 8.5.1.1 and one with 10.3.2.2 so you can clearly see what differences in behavior between them are. We can send them to you so can have a look, and advise us on fixing the issues, or to have testing platform for fixing these issues on your side.

Here is brief documentation of how to simulate problems with demonstrator app (from it is also apparent what the problems are)

After opening ChartControl solution setup Controls.Chart.Demo project as startup project. When you run it look at tab “Lightning Chart Bugs”. On screen you will see demo chart with various parts to show different issues we found so far. Also, there are some workarounds implemented to show, why some of them are not useful.

Issues:
Rendering of Labels
There is an issue regarding rendering of labels along axis of graph. It looks like numbers are chopped of at top and bottom. This issue is encountered only with specific configuration of graph. This specific configuration is default configuration i.e., rendering API DX11, label font size 12, rendering quality High. Change of any of these 3 parameters results in correctly rendered axis labels.
Caveats to changes in these three parameters:
• Change of rendering API – Change to rendering API DX9 results in incorrect rendering of some graphs and more difficult selecting of rendered lines in graph by mouse. Incorrect rendering consists of misplaced rendered lines and changing of their relative position when zooming on graph. You can try it by clicking DX9 button and zooming into center of graph where green and blue lines intersect. In high zoom, lines start to move around. This is unacceptable for our application. Also, Graph is visibly blurrier in DX9 mode.
• Change of rendering quality – Change of quality to medium or low results in very noticeable change in quality of text and some loss of quality of rendered lines in graph. Not shown in our demo, but it will not pass through our UX. Not usable.
• Change of font size – Change of font size to 11 or 13 has no apparent side effects, but it cannot pass through UX approval. 13 is too big and 11 is outside of UX guidelines, where 12 is lowest size we should use in OMNIS. Also change of size of Labels is bugged out. There are buttons for changing size “Make Lbls Smaller” and “Make Lbls Bigger”, and their respective buttons with workaround. After using them, size of labels doesn’t change until you move mouse over graph. This is also issue when you change size of graph in configuration. It can be easily bypassed (See workaround, or you can just replace whole WpfFont by new instance). But it worked in older version, and fact that WpfFont.Size is property with public set suggest it should also work in this newer version.
Disappearing name and λ is missing
After copying of graph, new graph is missing its name i.e., label in top left corner. Also, symbol lambda λ is missing from graphs, and it is replaced by “?”. These issues can be observed by clicking “Copy Chart” button and pasting copied chart somewhere (for example MS Paint). These issues appear, when chart is copied as vector. If you copy it them as raster, “Copy Chart No EMF WorkAround”, issues are not present, but we need to copy our charts as vector.

Also, there is one more issue that was hard to demonstrate in demo app, but we ale use bands in our application, and there is problem with null reference exception in some built in windows component, but it needs more investigation from our side, to be able to tell where the problem with bands.

For sending demonstrator apps, please write us how would you preferer to get this apps (source code). For obvious reasons, we do not want to post theme here on forum.

Thank you for your help

Stanislav Zubal

ArctionKestutis
Posts: 552
Joined: Mon Mar 14, 2016 9:22 am

Re: Upgrade from 8.5.1.1 to 10.3.2.2 problems

Post by ArctionKestutis » Mon Nov 28, 2022 2:07 pm

The primary channel of communication for users with active LightningChart subscription is direct email to Support ([email protected]). Just include subscription ID in your email.
Please send your application and any other additional information by email.

Alternative to direct email is our Portal. However, portal ticket system is less flexible in formatting (image insertion, attachments etc.).

All the best,
Kestutis

MirroZV
Posts: 45
Joined: Wed May 13, 2020 10:41 am

Re: Upgrade from 8.5.1.1 to 10.3.2.2 problems

Post by MirroZV » Tue Dec 13, 2022 7:40 am

Hello, just a quick follow up.

We have sent an email with details, subscription ID and attached demonstrators to your support email, and 2 weeks ago, and there is no reply. Not even that you registered incoming email.

So around week ago we have tried creating ticket in Portal, but after posting it, we can't even see it as ticket that we have created.

Can you give as update or advice on how to reach you properly.

Thank you.

Stanislav Zubal

ArctionKestutis
Posts: 552
Joined: Mon Mar 14, 2016 9:22 am

Re: Upgrade from 8.5.1.1 to 10.3.2.2 problems

Post by ArctionKestutis » Wed Dec 14, 2022 8:29 am

Sorry but we did not receive any email regarding this issue (nor ticket was created).
Alan (affiliated to the same company as you) reach our Support week ago. But issue have been different (about Bands).
Could you try sending email again? Maybe attachment size was too big (delete DLLs from project)?

Post Reply