search

xBimTeam / XbimWindowsUI

The home of XbimXplorer and WPF components for your desktop BIM applications.
Other
252 stars 149 forks source link

Update to latest/stable HelixToolkit.Wpf version #99

Open LucianoOhneO opened 5 years ago

LucianoOhneO commented 5 years ago

Hi everyone,

Do you plan an update of HelixToolkit.Wpf for the next release?

Thanks, Luciano

andyward commented 5 years ago

I had a quick look at upgrading Helixtoolkit and Propertytools as we're on an old version. Unfortunately there's some focus issues that I wasn't able to resolve -needs someone with a bit more WPF experience to take a look

Anything in particular you wanted from the latest version?

alex4wtr commented 5 years ago

Why isn't HelixToolkit.Wpf.SharpDX used?

andyward commented 5 years ago

That's probably one for @CBenghi but I'd guess it's just a case that it wasn't around when XBim.Presentation was first put together a few years back. Looks like we should take a look as DX should perform better. Not sure if the interface is the same - it might take a bit of work to refactor

JordanOlivet commented 3 years ago

Any update ?

It will be very nice if the latest stable version of Helixtoolkit was used.

We use xBim for the logic and SharpDx for the presentation but in order to do the transition from xBimWindowsUI to SharpDx, we have to have DrawingControl3D and Viemport3DX working side by side.

Unfortunately, we use Helixtoolkit.Wpf.SharpDx package for some logic within SharpDx and it needs Helixtoolkit 2.1.0. This setup brings two differents versions of Helixtoolkit and mess everything up.

I hope you'll be able to upgrade to Helixtoolkit 2.1.0.

CBenghi commented 3 years ago

Hi @JordanOlivet, If you have replaced the 3D frontend, can I ask why you need to retain WindowsUI in the project? Thanks, Claudio

JordanOlivet commented 3 years ago

Sorry for the late response @CBenghi,

As I said, we do not have the choice to keep WindowsUI because we want to do a transition between the two engines.

Indeed, the new SharpDx engine is very efficient and light but there is still some bugs here and there that prevents some files to be processed. The WindowsUI engine, as our legacy engine, works fine but it is pretty slow and memory eating.

Thereby, if we want to offer a new 3D engine to our customers, we have to have it running fine and bug less. This is not the case. So to prevents the customer to be blocked by this, we want to keep the legacy engine (WindowsUI) until we cant trust SharpDx 100%.

So the idea is to have both engines side by side and load one or the other depending of the result of the first loading of the file.

I hope it make sense, I'm not very good in english =).

CBenghi commented 3 years ago

I will try to do this in the coming weeks. There's quite a bit on my plate at the moment.

BTW, are you aware that we offer a high efficiency OpenGL based viewer as an alternative? That one is not free and needs a license but offers much richer APIs to control products, types (hide, show, isolate, color, richer selection visuals), and loads large files with much greater ease.

If you are interested you can ping me at claudio@xbim.it for info.

JordanOlivet commented 3 years ago

Oh I did'nt know that.

I will talk my company about it and will contact you if it's possible/interesting for us to buy a license for that.

Thanks for you time and great job =)

JordanOlivet commented 3 years ago

Any news @CBenghi ?