I am having problems with finding information about creating heat maps for D3 version 7. May I know how does it differ from the older version?
Related
which version of threejs supports forge viewer?
I need to use threejs version 130 or higher, are these versions compatible with forge viewer?
Forge Viewer uses self-managed three.js r71. Currently, our engineering team is working hard to support the newer three.js. See here for some updates.
https://www.autodesk.com/autodesk-university/class/Forge-Road-Map-2021
However, you may check these two blog posts to know how to leverage newer three.js using the es5 module.
https://forge.autodesk.com/blog/consume-aec-data-which-are-model-derivative-api
https://forge.autodesk.com/blog/how-add-newest-threejs-features-forge-viewer
Based on Elasticsearch DSL docs (https://elasticsearch-dsl.readthedocs.io/en/latest/)
"you have to use a matching major version" of the library for compatibility.
Specifically:
For Elasticsearch 7.0 and later, use the major version 7 (7.x.y) of the library.
For Elasticsearch 6.0 and later, use the major version 6 (6.x.y) of the library.
What's the best practice then for upgrading from ES 6 to ES 7?
This seems to imply that you can't make your code forward compatible with ES 7 server without making it backwards incompatible with an ES 6 server at the same time.
I'm trying to avoid having two different versions of the code having to exist at the same time by making it forwards compatible in-place first, before upgrading the server. Has anyone done this?
(We have lots of analyzers, tokenizers, multiple Documents, etc that we really don't want to have to duplicate in the code in the middle of the migration.)
There's an upgrade path that you need to follow. There's no need to maintain two different code bases. You should first make sure to upgrade to the latest minor+patch version of the ES 6 releases (i.e. 6.7 or 6.8) and make sure your indexes are compatible with that version.
You should also migrate your clients to the same latest minor+patch version of the ES 6 release, as Elastic makes sure that that version is forward-compatible with the next major version (i.e. ES 7).
Once you've tested everything on ES 6.7/6.8 (and properly backed up your data), you can safely upgrade to ES 7 and your clients will continue to work. Once ES is upgraded, you can upgrade your client to ES 7 as well.
After creators update of Windows 10 (version 1703) we have a problem with misrepresentation of datetime pickers content:
Do you have any workaround for this problem? Enabling runtime themes is not an option for us (it solves the problem with garbled text, but it changes appearance of application too much).
This is a problem of Windows 10 Creators Update. Here is an answer from Microsoft regarding that problem:
This only occurs in applications that use the Date Time Picker
implemented on COMCTL32 V5. Any application using the COMCTL32 V5 Date
Time Picker on RS2 will encounter this problem, including MFC and
Windows Forms applications. Unfortunately, there is currently no
workaround for the issue when using the COMCTL32 V5 Date Time Picker
other than removing the RS2 update, if possible. Affected applications
could be updated to use COMCTL32 V6, but this is not a trivial change
due to the differences in the control implementations between V5 and
V6.
As you may notice, currently the only solution is to enable runtime themes or rollback the Windows update.
I can confirm rolling back to before Creators Update fixes the problem. We use Delphi 5.
Is Microsoft aware of this problem? This is a major problem for a developer with a large installed base.
I tried updating COMCTL32 to V6 through the command prompt, but Windows always undid my work.
I upgraded my machine from WinXP to Win7, and at the same installed Lattice Diamond 3.1. My more complex simulations hang, Active-HDL uses 100% CPU time and is obviously in an infinite loop. Stupidly I don't have the installation of Lattice Diamond 2.1 or 2.2, and unbelievably Lattice only allows you to download the latest version. No fallbacks!
Does anyone have an installation file for Lattice Diamond 2.1 or at a pinch 2.2? I can provide an FTP to put it on if some has. I know its a big file, probably 1G+.
Actually I was able to just copy the Active-HDL 9.2 directory from Win7 in a virtual box on another machine, and overwrite the Active-HDL 9.4 directory. I still wouldn't mind an old installation file but at least I can simulate now. And Diamond 3.1 its actually possible to eliminate bkm warnings and errors. There were 2 many bugs in 2.1, tech support actually admitted my warnings were Diamond bugs not flaws in my code.
Actually I found you can download older version from support -> Software archive
Actual link:
http://www.latticesemi.com/en/Support/SoftwareArchive.aspx
I have Teechart v7.10 that shipped with Delphi 2007, which is the standard version. Is it possible to add a trend line to my charts or do I have to use the Pro version?
Thanks
As you can see in the feature matrix, the Trend function is only supported in the Pro version, as the other functions.
However, you can always do the calculations yourself and add the calculated points to a new TLineSeries.