At 3:00 PM Friday February 24th, 2017 we completed posting an update to CHT Build 21A.03.02.
We hope you will read the following essay posted a few days ago:
HNDCLEAN.EXE: How To Set Up
That essay will help you set up HNDCLEAN.EXE as a utility available from the Clarion IDE's "Tools" menu. In a few words, HNDCLEAN.EXE will solve the the problem of how developers can guarantee that when they use the IDE's "Generate and Make Current Application" menu, their application will actually regenerate fully, not partially.
We have internally logged, with the current clarion 10 IDE, many situations where template interface settings were changed that were not reflected in the finished application on our first execution of "Generate and Make Current Application". This situation occurs when the .CLW file targeted for the template setting change that you made, was not regenerated when it should have been.
Our essay, linked above, explains how HNDCLEAN.EXE can help you truly "Clean" up the previously generated files created by your application so as to "force-regenerate" the application from scratch.
We've provided a new configuration field on our HNDCMP.APP to configure HNDCLEAN.EXE input parameters 2, 3, and 4 in a manner similar to the above settings applied to HNDCLEAN.EXE setup for the Clarion "Tools" menu. [Image 1 Below]
Note that only parameters 2, 3, and 4 are used in this configuration because HNDCMP.EXE already knows what application you're compiling and in which directory it is located, so in it's call to HNDCLEAN.EXE it adds the first parameter (P1) automatically, and appends your (P2 P3 and P4) parameters from your configuration on the pictured HNDCMP.EXE dialog.
All the other rules and behviours apply as explained in our HNDCLEAN.EXE: How To Set Up document, including the use of relative or co-relative paths and the correct configuration of your CLARION100.RED file as explained there.
When the HNDCMP.EXE "Perform Clean First?" switch pictured above, is checked, the application's compile log now contains also output from HNDCLEAN.EXE in the same manner that the IDE's output window does. [Image 2 Below]
CHT's Global Template AACHTControlPanel has a setup tab called "Global Auto-Backup" which will trigger your applications to be backed up periodically, on a configurable time interval, as you're working on them and changing them. [Image 3, Below]
The backup directory configured on this "Global Auto-Backup" tab is managed from a CHT utility application called HNDBACKUPCONFIG.EXE or CHT Auto-Backup Configurator. From here you can browse, search, archive, and restore .APP and .DCT files that were backed-up automatically as you worked on them.
Each backup retains the original name plus a date-time stamp to help identify it for easy temporal identification when the day comes to want to locate an app saved prior to its having been changed or damaged.
From this utility's interface you can browse, recent backups, still in date-stamped .APP and .DCT format or browse and search older, archived backups packed in zip files. [Images 4,5,6 Below]
Your backup-archives are always readily available when you attach HNDBACKUPCONFIG.EXE to the Clarion IDE's "Tools" menu. We'll review how to do that here. You probably already know how to do this, so we'll make it brief in the form of a two images. [Images 7,8 Below]
In our recent document JANUARY 2017: CHT TOOLKIT FACTS SHEET we talked about one of our goals for 2017 was to illustrate various ways of merging real-world data with HTML documents which are then, optionally printed to .PDF.
We've revised HNDDOCUMENTBUILDER.APP to illustrate one way this can be done and to provide you with a practical example of live, web-acquired data being merged into a payment-receipt document based on an .XML template we've provided in your \accessory\hnd\xml\ directory called 000chtreceipt.xml.
We've set up a CHT file and page server -- like HNDFILSV.APP -- and attached it to an SQLLite data table extracted from our accounts and subscriptions table. This table when we're done with it will contain the payments portion of your CHT Subscriber account.
To the server we added a single procedure which, is called after authentication, and returns your subscription payment details. Also on the server we added a single, ProccessUserCustomRequest template. This template upon receipt of a UCR$ request (i.e. "User Custom Request" or Remote Procedure Request) from HNDDOCUMENTBUILDER.APP.
Locally, HNDDOCUMENTBUILDER.APP merges the receipt data with 000chtreceipt.xml to produce a HTML receipt displayed in CHT HTML Previewer, from where you can save it to disk as HTML or print it to a .PDF file also saved to disk.
Here in pictures are the steps to viewing and printing your own CHT Subscription Payment receipt. [Images 9, 10, 11]
At time of writing, not all receipt accounts have been fully established. If receipt information is not available for your account when you try this, you'll be presented with partial information and along with a "not yet configured" message. Designated CHT Testers, you know who you are, all have their receipt information up to date. All others active subscriber accounts will follow.