Title: ClarionLive! Convert-A-Thon Wrap Up!

Date: 12/13/2013
Clarion Date:
Duration: Just a tad over two hours

Download Recording

Hosts: Arnold Young, John Hickey, Lisa Daugherty, Mike Hanson

Presenter: Bruce Johnson, Mike Hanson,, Mike Gorman

Phew! The 40 hour ClarionLive! Convert-A-Thon will be history, and we'll provide a recap of how it went and what we learned! Plus Wolfgang and Roberto will be showing us how to monitor for changes in a TPS file, and Mike Gorman as single-handedly resurrected AppRef (it's free now!) and will be demonstrating it for us all! An action-packed webinar for all!
0:35 Tips from the Convert-A-Thon
#1. For conversion open the DCT first, not the APP. Let DCT get converted, run Check Data Structures, review and save. In the C9 IDE with a DCT open on the Tools menu there is a new item "Check Data Dictionary Structures" It main checks the WINDOW and REPORT controls defined in the DCT are valid. Any changes would only affect newly populated controls from the DCT. Another advantage of converting the DCT separately from the APP you a message is from a DCT problem.
#2. It's best to make as many fixes as possible in the original C6 source and TPLs, then reconvert. Any code that is C9 specific should be implemented in the C6 source and framed by OMIT/COMPILE using the _C90_ equate. This way if you need to make revisions to your shipping App you can test them and release them. You can write the fix code in C9, but then you should copy the fixes to C6 and convert again and test. It's s good time to remove unused, dead and obsolete code.
#4 If you are including non-ABC Classes check the INC file CLASS lines MODULE(,flag) and LINK(,flag) to see if they are using flags other than _ABCDllMode_ and _ABCLinkMode_. If they use other flags you should verify that the converted C9 Project Settings, Compiling tab, lists those as Conditional Compile Symbols. If you fail to define those, or set the correct values, it is likely class code will compile fine but GPF as soon at you try to call a class member.
1:04 Mark Goldberg mentions a way to add Project Defines is to creat a .PR type project file and add it to your CWPROJ. Use these type lines (note it does not use "=", it uses "=>"): #pragma define (_ABCDllMode_=>1) #pragma define (_ABCLinkMode_=>0)
This would require have 2 PR's: one for the exporting DLL (0,1), one for the EXE and DLL that use them externally (1,0). See the Clarion Help file on #pragma. Note it is case sensitive so #Pragma Define() will not work. Another way would be to create a Template that uses the #PDEFINE() command.
1:08 Questions
1:11 Removing a template that is no longer needed and getting rid of multiple procedure child templates. MH suggests to unregister the TPL, open your app and resave. This could result in loss of functionality if the TPL inserted code like the cwHH template inserts code to open help.
1:17 C9 IDE tour of Generate and Build options. Most common is on the main toolbar below the menubar. It works on the current app only. There is a Build menu that has the toolbar options, as well as a Build using APP Pad options. The Application Pad has a toolbar that also has Generate and Build buttons that work differently, right clicking allows additional options for generation, also allows selecting specific apps to build. Right-click on App in the Solution tree also has generate and build options. It's the easy way to build one app (that is not the currently open app). In the solution tree you can right-click on a project and set it as the Start Up project i.e. the EXE to run if you click the build and run button.
1:52 Mike Gorman shows AppRef a Clarion utility that indexes App Local data and procedures using a utility template. The product is no longer supported or available.


Old Business: None

New Business: None


Topics Covered:

Additional Downloads: None

Slide Show:

Time Events:

Webinar Introduction

Webinar Recording

Fourth Rule Of The Webinar:


comments powered by Disqus