Thanks
They all are…
Thanks
They all are…
I’m on my phone so cannot download zip
Does the class .Inc have _defines_ in Module(,) Dll()? Did you add them in your project Defines? Look at they demo project Defines
Edit:
I downloaded and do not find defines required:
xlsxwriter CLASS, TYPE, MODULE('xlsxwriter.clw'), LINK('xlsxwriter.clw')
Maybe it has to do with the TPictureClass ?
xlsxwriter.Construct PROCEDURE
CODE
Self.FormatQ &= NEW(XLSX:FormatQ)
clear(Self.FormatQ)
COMPILE('***',_TPictureClassPresent_)
Self.Picture &= NEW(TPictureClass)
***
There are 55 pages on this thread that mentions " Taboga Native Excel template is installed, TPictureClass from there is used"
I do not find any defines in the demo project.
I have
“MODULE(‘WIN API’)
ShellExecute(UNSIGNED,*CSTRING,*CSTRING,LONG=0,LONG=0,SIGNED=1),UNSIGNED,PASCAL,RAW,NAME(‘ShellExecuteA’)
END”
inside the Global Map
and I have libxlsxw.lib as an external lib file.
But it is obvious that I am missing something here.
Just found out:
I had INCLUDE(‘xlsxwriter.inc’) in the wrong place.
No more Exception error, but I get “function parameter validation error” when writing to excel. I can continue, but I am not sure what that error means.
Updated to 1.4
For now, up to 100% of the original (documented) lib functionality is supported
It is a great product, but
When using the new update, I got these errors:
Unknown directive, ignoring: !CREATING
Unresolved External worksheet_write_formula_str in xlsxwriter.obj
Trond
Hi RaFaeL,
I am using your class for a number of projects. Thanks!
I noticed that you comment the use of the “TPicture” class. You are welcome to use it in this project. It should be helpful in translating clarion pictures to excel masks and viceversa. I use it in my projects with your class.
Best regards!
Another thing RaFaeL, I wanted to contact you to propose a couple of additions to the class which I added to what I use. I would much prefer for it to be on the original class if possible.
They are nothing that big, but I think are useful. Let me know how I can contact you, or if you want send me an email.
edgard remove-spaces . remove-spaces riba at gmail…
Hi RaFael,
I see there have been some nice additions, Worksheet tables, to libxlsxwriter (https://libxlsxwriter.github.io/changes.html).
If possible would you have time to implement them in libxlsxwriter for Clarion.
Regards
Johan de Klerk
RaFael made a release in December based on libxlsxwriter 1.1.4. Not sure whether the SourceForge link synced.
Hi Mike,
Thanks for the reply.
I just downloaded it.
The libxlsxw.dll still shows as 1 April 2021.
Attached is the libxlsxwriter.zip file I just downloaded.
libxlsxwriter (9).zip (261.2 KB)
Regards
Johan de Klerk
Maybe SourceForge link is deprecated. I see the version on clarionlife.net of
276.26 KB
https://forum.clarionlife.net/viewtopic.php?t=3830
Hi Mike,
Thank you very-very much.
Got the latest 30/12/2021 now.
Regards
Johan de Klerk
Hi Johan
looking down near the bottom of the thread Mike mentioned at
https://forum.clarionlife.net/viewtopic.php?t=3830&start=855
it looks like there might be a later update from 2nd April 2022?
libxlsxwriter_220402.zip (20.7 KB)
libxlsxwriter for Clarion 1.5.1 based on libxlsxwriter.dll 1.1.4
Hi,
Thanks for the info.
I would never have looked all the way down there.
I see only two files in this zip that was updated;
xlswriter.clw
xlswriter.inc
Regards
Johan de Klerk
At this moment, worksheet tables is the only function of the original lib that isn’t implemented in libxlsxwriter for Clarion, including the latest builds for the russian community
Hi RaFaeL,
Thank you very much for the reply.
Would you be adding it in the future?
Regards
Johan de Klerk
I think, yes, someday
Hi RaFaeL,
Thanks that will be great.
Regards
Johan de Klerk
Can I use xlsxwriter object as parameter? I have tried using it as a function with parameter like this
(*xlsxwriter xlsxObj,STRING pInputValue,SHORT pColumn,LONG pRow,LONG pAlignment,<LONG pCellHeight>,<STRING pFont>,<LONG pFontSize>,<STRING pFontStyle>,<LONG pFontColor>,<STRING pFormat>,<STRING pBorderType>)
but I got call stack error when xlsObj.WriteString is called. Using the same procedure in office inside (using oiExcel object) have no call stack error.