Clarion developers don’t need to add any code to support touch input. The C9 Templates generate all the code needed to respond to touch gestures, so existing Apps just need a regenerate with C9 to become touch-enabled. But its easy for Clarion devs to add more specialized responses and touch “features” to their apps by working with these new additions to the RTL –
For more details on what the RTL exposes to your apps I refer you to this previous post. If you don’t have the time to read it right now then I’d just like to point out this one excerpt:
They (Gartner) predict that Windows will grab 39 percent of the tablet market in 2016. You can be sure that you’ll have many users wanting to run your Clarion apps on their (Win8 Pro – x86 based) tablet.
So roughly speaking they are predicting there will be about 5 million users on Windows tablets. Even if they are off by a million or so, its inevitable that touch and tablets are in your future, and its a good bet that some of those tablet users will be your end users.
If those numbers catch your interest then you probably should download and build this example
The example shows how to use the interfaces contained in the touch.* source files (located in your .\libsrc folder). It provides a nice look at some of the new features your apps can now support for an optimal “touch” experience (above and beyond the support the RTL provides automatically).
An update to 9.1 is being released today, there are a few important fixes;
FIX: A random “missing pure virtual” exception could be thrown by the evaluator
FIX: Possible lockup if Listbox height is enough to show only one record but the row is multiple lines
FIX: SETDROPID could work incorrectly on dragging between 2 Clarion applications
FIX: The application generator could not open an app after you edited its dct and deleted a file that had aliases.
The complete list is here.
An update to 9.1 is being released today, here are a few of the more important fixes;
FIX: OLE Automation could be treated as side-by-side instead of an OLE server in a separate process
This fixes OLE server automation, such as automating MS Office components, and came about as a result of the support added for registration-free COM. Surprisingly even after months of beta testing this wasn’t found until after the 9.1 gold release.
And these two, related to problems with either unusually large amounts of Procedure data, or .APPs where templates have been unregistered without removing the associated embed code:
FIX: Possible IDE lockup when there is very large number (hundreds) of local/global variables/tables in the Procedure and the IDE is processing the closing of an embed.
FIX: Possible failure on closing APP if embed tree with orphan embeds has been touched.
There are many other fixes and changes, you can see the full list here.
And of note for those using SQL backends;
FEATURE: The Clarion to SQL converter now converts the following operators for the specific drivers –
% (Modulo) All drivers
^ (Power) Pervasive SQL, Oracle
& (Concatenate) All drivers. *Note that ODBC uses the ANSI standard ||
XOR (Exclusive OR) SQLAnywhere, MSSQL
After a long and very thorough test cycle involving thousands of users, Clarion 9.1 Gold is released today! From the implementation of support for the Win8 API for accepting Touch input, to the new support for Registration-Free COM, and the new i64 family of functions, this is a very important release. All told there were almost 350 public fixes/changes/features implemented.
The release today includes additional changes/fixes and enhancements since the last beta release. View the complete list here.
To learn more about 9.1 you can read some of these older posts:
A final pre-release for 9.1 is on it’s way out this afternoon. Next week we’ll release updates to all add-on products, and some new examples.
There’s a last batch of changes and fixes, as well as a few new features, and you can read the complete list here: http://softvelocity.cachefly.net/C9/readme_9.1.11129.txt
In the next release we changed how launching of the on-screen keyboard for text-like controls behaves.
From the HELP file;
The Touch support is built in to the RTL, and no explicit code is needed for your program to respond to Touch input. The RTL implementation is based on the Windows 8 API.
*Currently for Windows 8 and 8.1 Microsoft has removed the OS level functionality for Desktop apps to automatically show the On-Screen Keyboard when a text-like control (Entry, Textbox, Drop Combo, etc.) control gains focus. We have added support in the “Enhanced Focus” template code to workaround this limitation.
To enable your programs to automatically display the On-Screen Keyboard go to Global Properties->Actions-App Settings and check the box for “Provide visual indicators on control with focus”.
Then choose the desired radio button for the On Screen Keyboard.
The options are:
On - Your program will attempt to launch the On-Screen Keyboard on any device. If the On-Screen Keyboard isn’t available no error is displayed to the end user.
Off – Your program will not try to launch the On-Screen Keyboard.
Auto – Your program will ask the OS if the device supports Touch input. If the OS indicates the device supports Touch input the On-Screen Keyboard is set to activate on text-like controls, otherwise it is set to Off.
Enabling and disabling of the On-Screen Keyboard can also be set globally for the application at runtime by calling the SetOnScreenKeyboard() method of the EnhancedFocusManager class.
Today we are announcing general availability of the 9.1 Pre-Release! While 9.1 is a minor version number change, it is a major change to the Clarion IDE and Runtime library. The 9.1 release has close to 300 changes/fixes and features, and has been through months of beta testing with close to 150 beta testers (nine alpha/beta releases, not counting this pre-release).
One of the most significant changes is the implementation of support for the Win8 API for accepting Touch input. The Touch input support is built into the RTL, and requires
no changes to your code. When you rebuild your App with 9.1 your program is ready to accept and respond to Touch input on any Win8 device. The Touch support will continue to evolve as we get your feedback.
Another important feature is the new support for Registration-Free COM. This simply means that you can deploy your App that uses any COM controls without having to install and “register” the COM control. More details here: http://clarionsharp.com/blog/9-1-and-reg-free-com/
There are many other new features, from IDE enhancements to the new TopScan and TpsFix, as well as hundreds of important changes and fixes, and you can read the complete list here: http://softvelocity.cachefly.net/C9/readme_9.1.11014.txt
We strongly encourage you to get the new release and get to work with it. We’ll be following your feedback as we move to the official gold release of 9.1.
Note: The 9.1 release requires a one-time rebuild of all your Binaries (DLL and LIB). You need to download the 9.1 versions of any 3rd party addons that you use.
The new beta release is on its way out. You can read all that’s new here. We’ll take feedback until Wednesday (April 16) and if all is good we’ll offer a pre-release to all developers with current subscriptions. It looks like we have all significant issues resolved after adding the touch input support – and we’re pretty happy with the results for Clarion developers being able to offer full Win 8.1 desktop touch input support without having to change a single line of code. Of course there is complete low-level support for touch input with accompanying class wrappers so you can make your app do anything that Win 8.1 supports. There are just a few things that we expect to add to the templates that enhance the touch experience — those will come in the next release later this week.
The 6th beta is out today (March 27). There are ~50 fix/changes/new features added to this release. We expect that next week we’ll make a final pre-release available to all users. You can view the complete list here.
Some of the new features in this release –