Does the Flexcel component also work with macOS 64-bit target platform (Delphi 10.3.2)?
...and does it allow to create xlsx files without any grid involved (like OExport)?
Hi,
Ok, thanks. It seems to be exactly what I need, except "weeks" makes me headache, I cant put my product for weeks on ice :(
If you are not exporting charts to pdf/html/etc, we have a version right now that you can use and will work in OSX64. If you have a FlexCel license, just email me at adrian@tmssoftware.com and I'll send you a link for that version.
I did not purchase a license yet, but will now do. After that, I will email you. I dont need to export charts etc. to pdf and so on, all I need to so is writing some array content to xlsx files.
I've sent you the link by email, let me know if you have any issues.
Thank you, I am installing it at the moment. I will report back any issue I encounter. Again, thanks for the quick help with this!
Hm I encounter a huge slowdown in the IDE when I add the unit to the uses clause.
FlexCel is a big a complex library (it is a mini-embeded-Excel without the UI - more than 1 million lines of code). And most of that code can't be removed by the linker if you don't use it, because Delphi doesn't know if you will use it. For example, the calculation engine can calculate more than 400 functions: You are likely not using them all, maybe you aren't even using formulas, but we can't know which functions you will use, and you might open any arbitrary file, so all formulas must be included, and some are quite complex. Same goes for conditional formats, tables, charts, you name it. As they say, everybody uses a 10% of Excel, but everybody uses a different 10%, so we have no much option than to implement it all. I've been working almost 20 years in FlexCel almost daily (first native version is from 2001), and there is still a lot of stuff to add.
Another note: One way to speed up the linking might be to build with runtime packages, at least when developing. You can always disable the runtime packages when shipping your app.
All right, that explains it for me. I am using a 64GB Windows 10 PC, with an i) 9900K processor, so it should not do that, but code insight always cause the code insight to go non-responding. My project is way above 1mio. lines of code, plus FlexCel, but without FlexCel, code insight is instantly, with FlexCel, always non-responding. But thats minor, because I noticed that all other TMS components are also not yet updated to compile under macOS 64, so I will have to wait anyway.
macos64 support is added & ready in all TMS FNC products.
We plan to complete support for all FMX products next week.
Is there a beta of the FMX UI pack available? Currently, I cant use the grid at all. A beta where at least the grid is working would already solve some problems.
@Bruno Fierens: You mentioned FNC pack. If I get the FNC UI pack, I would not need to use any longer the vlc grid and fmx grid and could use the grid from the fnc pack for both, Windows vlc and macos 64 bit FMX apps, right?