We got updated ChartDirector control example projects for HiDPI and Xojo 2018r3 coming with next MBS Plugins:
When using our plugin, you can set CDBaseChartMBS.ScaleFactor to 2 to get our plugin to multiply all numbers by 2 and get you a higher resolution of the graph. This makes it easy to adapt an application for higher resolutions.
For MBS Plugin there is a little change we will apply to next plugin release: The list of data types for SQL in the Xojo plugin SDK was extended and now includes all variants of integer from 8 to 64-bit and signed/unsigned. We''ll update our MBS Xojo SQL Plugin to make sure we can pass right data type to Xojo for UInt16 and others. The plugin will stay with old behavior for older Xojo versions.
This Xojo release looks great so far and we are moving a lot of projects from older versions to the new Xojo 2018r3 release. The labels on Windows are a big improvement as well as the other changes to reduce flicker on Windows. And the new Xojo version works with Xcode 10, which we need for MacOS 10.14 Mojave.
There is a move in software development to get us 64-bit only on Mac. We like to avoid the annoying dialogs for 32-bit for our customers and soon start implementing the notarization for our apps. There is an AppWrapper update (3.9) coming to help there. But usually it will be a shell script to do the signing, the notarization and build a dmg. We want to automate the build process as much as possible.
For old Real Studio, it may come the time to say good bye. MacOS 10.15 may no longer support 32-bit and not run it.
This is a PDF preview in Microsoft Edge. The PDF in question uses an OpenType font with postscript outlines with the variant without CID Font operators and this format is not supported by the Microsoft Edge PDF viewer.
For MacOS, the preview app shows the PDF, but when you print it, you get an empty paper.
We got a workaround for using this type of font with DynaPDF functions in our FileMaker and Xojo Plugins. So if you like to use such a font and get a working preview above, you need to not use the unicode encoding, but pick one of the 8-bit code pages like 1252.
Query the properties for font via GetSysFontInfos (Xojo) or DynaPDF.SysFontInfo (FileMaker) and check what you get back for BaseType. If the base type is OpenType. If it is open type and CIDOrdering property is empty, please don't use unicode code page for loading that font.
Or as I assume most clients do, is to trash the font and use one with proper character collection information. Otherwise having a checkbox to fall back to 1252 code page could be a checkbox to include for PDF output.
For testing, we used both the Smart Card Reader from König (left) and the SmartTerminal ST-1144UB from Cherry (right). Both do the job with a little difference. For the left device, you can connect and query status, even if there is no card. The right one only allows to connect when you have a card inserted. Other readers work probably as this uses a standard interface and drivers are built into the operation system.
For Xojo we got the new CryptoTokenKit classes in MBS Xojo Mac64bit Plugin for the modern way Apple likes to handle this with asynchron operation and delegates. Beside this, we also go the older cross platform way via PCSC API and the ReadFile method in and SmartCardMBS class.
Whatever function you use, you can pass the right file ID and read the files you need from the smart cards. We also got a function to split the data into the parts. See SmartCard.SplitValues for FileMaker and SmartCardMBS.SplitValues function for Xojo.
As you may know all Belgians have an identify card. We recently added classes for CryptoTokenKit framework on Mac and translated a sample project from Swift to Xojo to read those card. Works very well to get basic information, address details and the picture of the person.
The same could have been done with our SmartCard classes. And as those classes use the PCSC interface on MacOS, Windows and Linux you could even get it done cross platform.
With last plugin release we enabled the option for CURL to disallow you passing user name and password. As URLs are sent to proxy and may be logged at the web servers, we prefer to not include credentials in the URL. And if you use the email address for user name, the name in the URL never worked.
So for the future, please separate them and put the credentials in the relevant options:
As you know MBS Xojo SQL Plugin can execute stored procedures. For that you normally just pass the name of the stored procedure instead of a SQL command. The plugin than queries the details for the stored procedure like the input and output parameters. You can set input parameters and call execute. After you got all the result sets read, the last data package from the server brings the return code and the output parameter values. Check this sample code: