I don’t use Microsoft Visual Studio, can I use the NumXL SDK and still get support? ANSWER: Yes, we will definitely do our best to answer your questions that is not tool-specific.
I wish to use NumXL with XYZ language, but I don’t see a wrapper library for it. Are you going to build one? ANSWER: The SDK is a collaboration between our engineers and users. Once we establish the demand for new languages, we will create a project repository on GitHub and invite you and others who expressed interest in this SDK to join.
We hope and encourage you and everyone interested will help us with development and testing.
Where do I find examples for using the SFLOG's functions in NumXL? ANSWER: Checkout the "examples" section in this site.
I have a technical issue/question with the SDK, who do I contact? ANSWER: Whether you’re looking for answers, would like to solve a problem, or just want to let us know how we did, you’ll find many ways to contact us right here:
Phone: +1 312.257.3777
E-Mail: suppo.nosp@m.rt@n.nosp@m.umxl..nosp@m.com
Please view our FAQ to find answers to your questions or send us an email for general questions!
We’ll help you resolve your issues quickly and easily, getting you back to more important things, like relaxing on your Lazy chair.
Are all NumXL runtime executables digitally signed and secure? Should I sign my application too? ANSWER: Yes: All our DLL are securely digitally and signed with our code-signing certificate. Also, all 3rd Party libraries are code-signed by their vendors.
You don’t have to digitally sign your custom application to use the NumXL SDK, but we highly recommend it, so that your Customers will not receive pop-up windows warning about unknown publishers.
My application is multithreaded. Are SFLOG's functions thread-safe? ANSWER: Yes; All NumXL function are thread-safe. You may invoke multiple NumXL functions from different threads, or have multiple threads concurrently invoke one function. To avoid log messages of the different threads getting mixed up, the thread unique identifier is stored alongside with the log message.
Does any of SFLOG's functions raise an exception? ANSWER: No; NumXL functions are standard C-API, so they report the status of operation via the return value. Any exceptions (C++ or Win32 structured) triggered during its operation are trapped (caught) and processed early on inside the function. In sum, you don’t have to worry about exceptions while calling NumXL functions.
Configurations
Can I change the logging file name? Answer: Yes, when you initailizae the logging system either via SFLOG_INITA (or SFLOG_INITW), set the value of the szAppName argument to correspond to your desired file basename. The file extension (.log) is not customizable.
Where does the SFLOG place the logging file, if I don't specify a location? Answer: The SFLOG defaults to the temp directory in the local profile of the current user. (e.g., C:\Users\*username*\AppData\Local\Temp)
License
Do I need a NumXL license to develop with the SFLOG? How about deployment? Answer: No; the SFLOG API does not require a license key to operate.
Nevertheless, you need to initialize it properly in order to use the rest of the NDK functions.
Deployment
What do I need to include in my deployment package, if my application uses the SFLOG functions? Answer: You'd need to ship the platform-specific SFLOG.dll that matches your application platform (x86 or x64). The SFLOG should be copied in the same folder as your executable (.exe or .dll)
Miscellaneous
Can I use the SFLOG function in my application for Mac? Answer: No; NumXL runtime environment (NRE) runs only on a Microsoft Windows operating system. It won’t run on Mac OS X.
Where can I get more information? How do I start? Answer: Read through our online getting started guide and reference manual. Next, try the examples included with the SDK. Finally, you can contact our support staff with any question or issue you may have.
