CapeSoft File Explorer Documentation

Welcome to File Explorer! If you are new to File Explorer, or if you have not used the product for a while, these steps should get you going in the right direction. File Explorer started off with fairly simple goals in mind (see the section called Product History for more info). Since its release in November 2000 it has evolved and expanded to the point where it's at today, which is a long way off from where we started. Because of this process of evolution the product has many diverse features, and can be quite difficult to get your head around. For this reason, the easiest and best way to familiarize yourself with it is to simply have a look at the feabc.app example application, which demonstrates most of the features at any moment in time.

Compile the feabc.app (see the section titled Examples for more info) and spend a few minutes having a look at the various things which the application can do. Once you have found something which looks exciting, have a look at the code / templates which the examples application uses, and then turn to this document should you require more help how the templates, methods, properties and logic works (although most of the time the example application is fairly clear about what it's doing). For some users the templates that ship with File Explorer will be enough to achieve what you want to do. For users who want to scratch below the surface (highly recommended), have a look at what code the templates generate. The templates simply generate code that implements the various classes that make up File Explorer. Those classes are all outlined in this document. If you are still unsure about something after you've looked at the feabc.app example, and read the documentation, feel free to contact us for further assistance or to be pointed in the right direction. The Frequently Asked Questions is another useful reference to read through once in a while, and be sure to read the product's Version History regularly to see what we're working on.

FileExplorer 5 introduces two existing new classes. The new default Media class is feMedia2, this class fully supports the new interface available with Windows Media Player 7 and up, and maintains backward compatibility with older versions of Media Player (if the new interfaces are not available it will fall back to the old ones). The new default editor is feEditor, which replaces the now deprecated feHtmlEditor. The new editor is faster, more stable, and far richer than the old editor. It is fully Vista compatible and no longer relies on the MS DHTML Editing control, or anything else other than Internet Explorer. The new editor:

Compatible with all version of Windows, including Windows Vista and Windows Server 2008.
Requires only Internet Explorer 5.5 or later on the machine, there are no other dependencies.
Generates HTML with Internet Explorer 5, 6, 7 and Gecko browser (Mozilla / Firefox / Netscape) compatibility
XHTML 1.0 support (generates clean, standard compliant XHTML code)
Font formatting: type, size, color, style, bold, italic, etc
Text formatting: alignment, indentation, bullets list, etc
CSS (cascading style sheets) support for a better integration with web sites, and cleaner, faster, small code with better consistency
What You See Really Is What You Get. Pages are rendered by IE as you edit them, so the rendering is very accurate.
Cut, Paste and Past as Plain Text, Undo and Redo
Paste from MS Word cleanup with auto detection
Link creation
Anchors support
Image insertion
Table creation and editing (add, delete rows, etc) - one of the best systems in the market.
Table cells editing (size, colours, etc)
Form fields
Right click context menus support
Complete toolbar customization
Easy menu customization and skins (add your own styles, font-formats, etc ...)
Skins support.
Plug-in support.
Spell checker integration via SpellerPages (additional built-in spell checking options coming soon!)
Multi-language support, including Right to Left scripting.
Complete page editing, including visually setting the overall page properties
Lightweight and fast
Automatic browser detection and support for IE 5.5 and upwards.
Load from memory or disk, or URL
Save to memory or disk
Full access to the editor and editor data programmatically
Easily customizable, fully skin-able, and can be modified without requiring a recompile of the application
Easily customizable toolbars, including runtime customization and additions (no recompile required).
Ability to get and set the text or HTML simply by calling a method.
Much, much more!
Full access to the DOM of the edited page coming soon!

Important: The new editor requires that you ship the following files with your application (place these in the application or Data directory for your application). All of these files are shipped in the example folders: Clarion\3rdparty\examples\FileExplorer\Editor Files\. See the Distribution section for more information.

This template is Copyright by CapeSoft Software, 2019. None of the included files may be distributed. Your programs which use File Explorer can be distributed without any File Explorer royalties.

Each developer needs his own license to use File Explorer. (Need to buy more licenses?)

This product is provided as-is. Use it entirely at your own risk. Use of this product implies your acceptance of this, along with the recognition of copyright stated above. In no way will CapeSoft Software CC, their employees or affiliates be liable in any way for any damages or business losses you may incur as a direct or indirect result of using this product.

While writing CapeSoft Mailer, we were looking for a way to display html documents as if they were being viewed through IE, rather than just viewing the HTML 'text'. After much scratching and testing we implemented an object using the Internet Explorer OCX. With this initial work under our belts we started looking at what other doors similar OCX integration could open, and started writing what was to become the File Explorer. We added support for html browsing and editing, and support for pdf, sound, movies, and flash.

Since we released the first version of File Explorer the product has evolved and grown into a fairly large product, as you will see if you have a look at what the feabc.app example application is capable of doing. Enjoy...!

In November 2000 we released the first version of File Explorer for Clarion 5. At that time we started building a control to browse html pages, using the Internet Explorer "WebBrowser" OLE control, and the CW OLE container control to host it. This proved unstable, and although we wrote huge amounts of "don't fall over and die" code, the File Explorer control (at that time called Html1) was always subject to the OLE control's problems.

Then in March 2002 we moved to using COM and wrote a new control for browsing html pages, based on pure COM (not the OLE control / container which we had been using). The improvement in terms of speed and stability was mind blowing. Since then FileExplorer has come an long way and expanded to include the feBrowser control for viewing HTML and web pages, feHtmlEditor for editing HTML (soon to be replaced by the brand new, greatly improved, feEditor), feFlash for viewing Flash content, fePDF for PDF documents and feMedia which provides a full media player.

Simple to add a control to your program in a matter of minutes.
Each "Viewer" control can play any number of file formats, you choose while file formats are supported for each control
Auto load a file into a control as the window opens
Supports multiple controls per window, so you can play MP3 files while browsing the web!
Optionally enable "smart loading", where the user can select a file to load / play, and the Viewer Control detects the file type and handles the ocx / com initialization by itself...
Supports allocating variables to each control (or a single variable shared across multiple controls), so you can code controls to disable themselves if the variable equals true or false or whatever...
Full callback-function support with examples...
Browse html...
- Browse pages from disk or the internet
- Templates that drop standard browsing buttons (back, forward, refresh, save, print etc etc) onto your windows
- When a user clicks on a hyperlink you can see where that hyperlink is navigating to, and either navigate there, cancel the navigation, or navigate somewhere else...
- Easy to implement a status bar
- Read from and write to html fields in an html form from your app!
- Trigger the "submit" button on an html form
- Get a list of all the fields in an html form
- Uses Internet Explorer and can hence display anything that IE can.
- Full control over loaded page contents via the HTML DOM.
Edit html...
- Compatible with all version of Windows, including Windows Vista and Windows Server 2008.
- Requires only Internet Explorer 5.5 or later on the machine, there are no other dependencies.
- Generates HTML with Internet Explorer 5, 6, 7 and Gecko browser (Mozilla / Firefox / Netscape) compatibility
- XHTML 1.0 support (generates clean, standard compliant XHTML code)
- Font formatting: type, size, color, style, bold, italic, etc
- Text formatting: alignment, indentation, bullets list, etc
- CSS (cascading style sheets) support for a better integration with web sites, and cleaner, faster, small code with better consistency
- What You See Really Is What You Get. Pages are rendered by IE as you edit them, so the rendering is very accurate.
- Cut, Paste and Past as Plain Text, Undo and Redo
- Paste from MS Word cleanup with auto detection
- Link creation
- Anchors support
- Image insertion
- Table creation and editing (add, delete rows, etc) - one of the best systems in the market.
- Table cells editing (size, colours, etc)
- Form fields
- Right click context menus support
- Complete toolbar customisation
- Easy menu customization and skins (add your own styles, font-formats, etc ...)
- Skins support.
- Plug-in support.
- Spell checker integration via SpellerPages (additional built-in spell checking options coming soon!)
- Multi-language support, including Right to Left scripting.
- Complete page editing, including visually setting the overall page properties
- Lightweight and fast
- Automatic browser detection and support for IE 5.5 and upwards.
- Load from memory or disk, or URL
- Save to memory or disk
- Full access to the editor and editor data programmatically
- Easily customizable, fully skin-able, and can be modified without requiring a recompile of the application
- Easily customizable toolbars, including runtime customization and additions (no recompile required).
- Ability to get and set the text or HTML simply by calling a method.
- Much, much more!
- Full access to the DOM of the edited page coming soon!
View PDF files...
- Easily load and view PDF files
- Includes functionality to save, print, find, zoom etc etc
- Use either the native Adobe Acrobat toolbar, or hide that toolbar and use the File Explorer templates to drop your own controls onto the window...
Play sound files...
- Supports MP3, Wav, Snd, Au, MID, M3U and MPE formats
- Complete with standard play, pause, stop buttons
- Control volume, play rate, number of times a file plays (loops) etc etc
- Access file properties such as duration, title, author etc etc
Play "movie" files...
- Supports MPEG, Mov, AVI, WMV and QT formats
- Standard stop, play, pause buttons
- Set volume, play rate, number of times a movie plays (loops) etc etc
Play Macromedia Flash files...
- Great way to jazz up your apps. Why not play a Flash file in the background on your "intro" window, or help screens... Sky's the limit.
- Stop, pause and play buttons
- Methods for handling current frame etc.
Other cool tools...
- Store multiple multimedia files in a single TopSpeed file...
- Methods for playing sound files using Window's API calls
- Read and write to the Window's registry
- Send messages to the system debugger

Your questions, comments and suggestions are welcome. Check our web page (www.capesoft.com/accessories/downloads.htm) for new versions. You can also contact us in one of the following ways.

CapeSoft Support
Email
Telephone	+27 87 828 0123
Fax	+27 21 715 2535
Post	PO Box 511, Plumstead, 7801, Cape Town, South Africa

File Explorer may be purchased from:

CapeSoft Sales
Web	www.capesoft.com
Email
Telephone	+27 87 828 0123
Fax	+27 21 715 2535
Post	PO Box 511, Plumstead, 7801, Cape Town, South Africa

Buy Online
Web	www.clarionshop.com

File Explorer is fully compatible with Windows Vista, Windows 7 and Windows Server 2008.

The Browser control works well with Internet Explorer 5.5 through to 8 and above, the Media Player supports Windows Media Player 6 through to 11 and above, and the PDF and Flash viewers use components provided by Abode (Adobe Reader and Flash Player respectively).

The current HTML editor (feEditor) relies only on Internet Explorer. We recommend IE 7 or above for maximum functionality and security.

The old (deprecated) HTML editing class feHtmlEditor relies on the MS DHTML editing control, which is not shipped with these operating system, however it is provided as a redistributable, which can be shipped with your application. The FileExplorer installer places a copy of the Microsoft MSI redistributable in \Clarion\3rdparty\bin\DhtmlEd.msi. This can be included with your installer, and can be run silently. We recommend using the new HTML editor provided by FileExplorer, which is faster, more flexible, standards compliant (CSS, xhtml etc.), and simple to configure and customise. It also does not rely on anything other than Internet Explorer.

The various File Explorer classes require the following to be installed. While File Explorer (or parts thereof) may work on earlier versions than those indicated below, these are considered to be the minimum system requirements.

Microsoft Internet Explorer (5.5 or later)
Adobe Acrobat Reader (4 or later)
Windows Media Player (6.4 or later)
Adobe Flash Player

Run the supplied installation file.
For PDF functionality ensure that Adobe Reader or Acrobat is installer. For Flash functionality ensure that Adobe Flash Player is installer.

Adding a File Explorer Control to your Application is this easy...

Add the File Explorer Global Extension Template to your application.

Load your application in the Clarion IDE
Click the Global button
Click the Extensions button
Click the Insert button
Select the Activate_File_Explorer template from the Select Extensions list that appears.

Select the Select button and the File Explorer Global Extension's prompts appear on the right-hand portion of the Extension and Control Templates window.
Leave all the template options as they appear. The default's are fine for now. You can always come back and change them later...
Click OK a couple times until you're back in your app, then compile... That's it!!!

Once the Global Extension template has been added to your application, you can add other templates, call dll functions, etc etc. You should start by compiling the example application ( click here for info ) called "feabc.app". Look at what this example can do, and then have a look how we did it. Use this document to lookup additional information and hopefully the pieces will start fitting together.

DLLs required (Standalone mode compiles)
Clarion Version	DLL required
Clarion 6.1	C60FEX.DLL and PWUTIL.DLL
Clarion 5.5	C55FEX.DLL and PWUTIL.DLL

DLLs required (Local mode compiles)
Clarion Version	DDLL required
Clarion 6.1	PWUTIL.DLL
Clarion 5.5	PPWUTIL.DLL

When using the feEditor class

Important: The new editor requires that you ship the following files with your application (place these in the application or Data directory for your application). All of these files are shipped in the example folders: Clarion\3rdparty\examples\FileExplorer\Editor Files\. See the Distribution section for more information.

CapeSoft HyperActive - HyperActive allows you to easily make any control into a url, that opens a page in your default web browser. HyperActive also supports sending a control's url directly to your File Explorer control. Place buttons or a list box on the same window as your File Explorer control, and use those controls to load urls into your File Explorer control.
CapeSoft NetTalk - One of NetTalk's features is full Email support from within your app. Use File Explorer to create html documents, and NetTalk to send the html "source code" as an email, along with embedded graphics, attachments etc. If you already own both NetTalk and File Explorer there are two examples of using FileExplorer and NetTalk:

EmailHtml - Clarion\3rdparty\examples\FileExplorer\EmailHtml\

This demonstrates loading and HTML from disk using the feFile class; embedding images using feEditor; automatically creating a text version (the example uses NetWebClient, however the feBrowser class provides an excellent option for doing this); and of course, sending the email with the HTML part, text part, and any local images embedded.
FE and Nettalk - Clarion\3rdparty\Examples\File Explorer\FEand NetTalk\

A simple demonstration of how to send and receive email using these two tools.

Andy Ireland for developing the brilliant COM classes which File Explorer makes use of..
Carl Barnes for input with the hand coded examples, lists of features to add to File Explorer, and occasionally sending info on how to write those features too <g>.
Kevin Erskine for suggesting we support Mike Hanson's Resizer template, and writing the template code to do it..

Activate File Explorer
Summary	Global Extension Template Activate CapeSoft File Explorer Features in your application Required
What does it do?	You must add this template to your app or no other templates / objects will work. This template sets up the File Explorer classes (dll / lib) so that other templates can implement those classes.
Prerequisites	None
How do I implement it?	1. Open your app 2. Select "Global Properties" from the "Application" menu 3. Click the "Extensions" button 4. Click the "Insert" button Select "Activate_File_Explorer" ( found under "Class File Explorer" ) 5. Click the "Select" button ( you can leave all default settings, these are discussed below ) 6. Click "OK" 7. Click "OK" again
What are my options?	Folder for temp files File Explorer may need to generate temporary files while your app runs. If it does, by default it uses the same folder as your exe. You can change this here to be either the same folder as the exe (default), or the system temporary folder ( normally "c:\windows\temp" or similar ). Do not generate any code No template code will be generated at compile time, however any controls which you have populated will still appear. Do not automatically generate map Does not add anything to your global map at compile time. Do not automatically call feDispose By default, File Explorer will generate a line of code which calls the feDispose function as your application closes. If for some reason you do not want this function to be called, you can tick this option here. If you're not sure, don't tick this.

Document Viewer
Summary	Control Template View Html, PDF, and SWF files Optional
What does it do?	Populate this control onto a window in order to be able to view and / or edit HTML, PDF, or SWF files in it.
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	On the window where you want to use this control, choose "Control Template..." from the "Populate" menu. Look for the section called "Class FileExplorer", then select the item in that section called "DocumentViewer". Click on your window to populate this control.
What are my options?	"General" Tab Object Type This control used to be able to load more than one file type. As the functionality evolved we had to break it up to support only one file type per control. Choose the File Type here. "Common" Tab Initial Document If you want this control to load a file as the window opens, enter the file name here. Tick "Variable?" if you want to enter a variable instead of a filename. Provide 'All Files' Option in File Lookups If the user uses the template's 'File Lookup' button to find files (much like the DOS File Lookup Clarion control), enabling this option will result in the lookup including 'All Files' as a supported file type. "Browse Html" Tab - only available if you choose Html Browsing on the first tab Auto-Resize control Have the Viewer control automatically resize when the window resizes, selected by default. Implement Callback Events Callback events are handled "internally" by File Explorer, which calls a virtual method called EventCallback each time an event is fired. If you want to enable Callback events, simply tick this option here. (Note: Enabling Callback events will add some overhead to the object, so theoretically it will slow it down, however the speed difference should not be noticeable). "Edit Html" Tab - only available if you choose Html Editing on the first tab Auto-Resize control Have the Viewer control automatically resize when the window resizes, selected by default. Implement Callback Events Callback events are handled "internally" by File Explorer, which calls a virtual method called EventCallback each time an event is fired. If you want to enable Callback events, simply tick this option here. (Note: Enabling Callback events will add some overhead to the object, so theoretically it will slow it down, however the speed difference should not be noticeable). "PDF" Tab - only available if you choose PDF on the first tab Show Toolbar Decides whether or not the native PDF toolbar is displayed when you view documents. Show Scrollbars Decides whether or not scrollbars are displayed when you view documents. Initial Zoom Sets the initial zoom percentage for the object. Preferred Acrobat Version Because it is possible to have more than one version of Adobe Acrobat installed on your PC, and because some methods only work with Acrobat 4 ( as described in the methods and properties sections of this document ), we enable you to specify which version of Adobe Acrobat should be loaded. If the version you choose here is not installed on the PC, any available version will be loaded. "Flash" Tab - only available if you choose Flashon the first tab Loop Files Plays the file repeatedly if enabled "Object" Tab Object Name Each Viewer Control instantiates a File Explorer object (from the File Explorer class), which it uses to "work". These File Explorer objects need names. The templates will automatically name the objects for you (typically something like ThisViewer1, ThisViewer2 etc), but you can rename the object here if you have reason to. Var to Disable Optionally create a variable (Byte) which can be set at runtime, which will disable this object if set to 1 (True), and enable it if set to 0 (False). You can point all objects in your app to a single override variable allowing a single 'switch' for the user to disable all controls, or use multiple variables allowing the user 'switches' to disable specific controls or groups of controls at run-time. Don't Generate Any Code No code will be generated for this particular object at compile time.

Media Viewer
Summary	Control Template Play sound and video files Optional
What does it do?	Populate this control onto a window in order to be able to play sound and video files
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	On the window where you want to use this control, choose "Control Template..." from the "Populate" menu. Look for the section called "Class FileExplorer", then select the item in that section called "MediaViewer". Click on your window to populate this control.
What are my options?	"General" Tab ( no options ) "Common" Tab ( File Types ) The top two sections of this tab allow you to choose which file types this control will be allowed to play. Provide 'All Files' Option in File Lookups If the user uses the template's 'File Lookup' button to find files (much like the DOS File Lookup Clarion control), enabling this option will result in the lookup including 'All Files' as a supported file type. Initial Document If you want this control to load a file as the window opens, enter the file name here. Tick "Variable?" if you want to enter a variable instead of a filename. "Advanced" Tab Auto-Resize control Have the Viewer control automatically resize when the window resizes, selected by default. Implement Callback Events Callback events are handled "internally" by File Explorer, which calls a virtual method called EventCallback each time an event is fired. If you want to enable Callback events, simply tick this option here. (Note: Enabling Callback events will add some overhead to the object, so theoretically it will slow it down, however the speed difference should not be noticeable). "Other" Tab Auto-Rewind Sets whether the Media Files automatically rewind once they have finished playing. Allow Zoom Changing Sets whether the user can right-click on the media file while it is playing, and adjust the zoom properties. Auto-Start Sets whether the Media Files start playing automatically once loaded. Mute Sound Mute the sound. Times to Play Set the number of times a file plays before stopping. Playback Rate Set the control's playback rate. 100 plays files at their 'normal speed' of 100%. Entering a value of 50 or 200 would play files at 50% or 200% of their 'normal' speed. Zoom Sets the zoom for the video clip. Select one of 50%, 100% or 200% (relative to the default playing size of the media clip); 'Full Screen', 'Fit', '1/16th Screen Size', '1/4 Screen Size' or '1/2 Screen Size'. Note that some zoom sizes (such as 'Full Screen') will only work if the file which you load supports that resolution. Also, note that setting the zoom to 1/2 of the screen size will not work if your FileExplorer control is not large enough to hold that size. Start Time By default, files start playing at the beginning (0.0). Setting this to 10.5 would start playing the file 10 and a half seconds into the clip. There is also a property called 'End At', and 'Duration'. See the 'Properties' section in these docs for notes on how to implement these. Position (Left, Right, Bottom) When loading a file into the MediaViewer control, the ocx may resize itself to fit the size of the file it is loading (visual size). To clean this up you can set these three sizes here. Immediately after the file loads (and the ocx resizes itself), File Explorer will resize the ocx so that there are these units of space between the control's left, right and bottom borders, and the left, right and bottom borders of the parent window. Auto-Resize Set this to true if you want the control to automatically resize itself each time a new file is loaded. The control will increase or decrease in size so that it is large enough to contain the loaded file (assuming your window is large enough!). By default this is set to 'false'. "UI" / "User Interface" Tab Show Toolbar Sets whether or not the native Media Viewer toolbar is displayed. Enable Toolbar Enables / disables the toolbar. The 'Show Toolbar' option must be checked to use this. Show Slide Bar Sets whether or not the "Slide Bar" control appears. This is the control which you can use to "move around" inside the playing file. Enable Slide Bar Enables / disables the slide bar. The 'Show Slide Bar' option must be checked to use this. Show Position Controls Sets whether or not the "Position Controls" inside the toolbar are displayed. The 'Enable Toolbar' and the ' Show Toolbar'options must be checked in order to use this. Show Info Window Sets whether or not the 'Additional Information Window' is displayed. This window shows information such as 'Artists Name' and 'Copyright Information'. By default this is not activated. Show Goto Bar Sets whether or not the "Goto" drop list is displayed. By default this is not activated. Right Click Menu When the user right-clicks on the control (assuming a file has been loaded into it), a popup menu appears, allowing the user to set various options. This is a native Microsoft popup menu. If you want to turn off this menu (so it does not appear), do that here. "Object" Tab Object Name Each Viewer Control instantiates a File Explorer object (from the File Explorer class), which it uses to "work". These File Explorer objects need names. The templates will automatically name the objects for you (typically something like ThisViewer1, ThisViewer2 etc), but you can rename the object here if you have reason to. Var to Disable Optionally create a variable (Byte) which can be set at runtime, which will disable this object if set to 1 (True), and enable it if set to 0 (False). You can point all objects in your app to a single override variable allowing a single 'switch' for the user to disable all controls, or use multiple variables allowing the user 'switches' to disable specific controls or groups of controls at run-time. Don't Generate Any Code No code will be generated for this particular object at compile time.

Background Media Load Button
Summary
( No longer supported - please use the CallFe_MediaAPIMethod ccode template instead )

Document Print Button
Summary	Control Template Prints the currently loaded document Optional
What does it do?	This template drops a button onto your window, which prints the loaded document when you click it. You will need to have already populated a Viewer Control onto the window before you can populate this template. It currently supports printing html pages (feBrowser, feHtmlEditor) and also PDF documents (fePDF).
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	1. On the window where you want to use this control, simply choose "Control Template..." from the "Populate" menu.
What are my options?	Don't show "Printer Options" dialog window By default this is not checked, and you will be presented with the standard "Printer Options" screen before printing (if supported), where you can set paper size etc. You can select this option here, which will result in the document printing "straight to the printer" instead. Document Type (obsolete) NOTE: For an example, have a look at the "simple_fePDF" procedure in the feabc.app example application.

Flash Control Buttons
Summary	Control Template Used with the Document Viewer template Optional
What does it do?	This template populates a "Play", "Pause", and "Stop" button onto your window, to control the playing of Flash files in the Document Viewer control.
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	1. On the window where you want to use this control, simply choose "Control Template..." from the "Populate" menu.
What are my options?	There are no additional options for this template.

Html Background Color Button
Summary	Control Template Used with the Document Viewer control Optional
What does it do?	Use this template to change the background color of an html document (Html editing, not browsing), using the following steps ( assuming you have already populated a Viewer Control and have set it up to support "Html Editing" ).
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	1. On the window where you want to use this control, simply choose "Control Template..." from the "Populate" menu.
What are my options?	Reload Document After Updating IIf you select this, the html document will be saved, and then reloaded each time you change its background color. The reason this may be necessary is that graphics in the html page which do not contain "full" paths ( such as " subfolder1/image1.gif " ) will not display once you change the background color - an ocx refresh issue. Turning this option on gets around that problem by effectively "reloading" the html document ( and all the graphics ) each time the background color changes.

Html Edit Buttons
Summary	Control Template To Do Optional
What does it do?	To Do
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	1. On the window where you want to use this control, simply choose "Control Template..." from the "Populate" menu.
What are my options?	(( none )

Html View Buttons
Summary	Control Template To Do Optional
What does it do?	To Do
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	1. On the window where you want to use this control, simply choose "Control Template..." from the "Populate" menu.
What are my options?	(( none )

Media Buttons
Summary	Control Template To Do Optional
What does it do?	To Do
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	1. On the window where you want to use this control, simply choose "Control Template..." from the "Populate" menu.
What are my options?	(( none )

CallFe_EditMethod
Summary	Control Template To Do Optional
What does it do?	In order to use this code template, you must have already populated one of the Viewer Controls onto your window. Use this template ( typically behind a button ) to implement the File Explorer "Edit" method.
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	To Do
What are my options?	Parent Object This drop list lists all the current File Explorer objects which are present in your procedure. Select the object which should load this file. Look in the Viewer Control's properties, on the "Class" tab to see its object name if you are unsure. Document Type The various "Edit Options" (see below) vary depending on the type of document you are going to load ( and hence edit ). Select the document type here. Edit Option Select one of the options from the drop list, e.g. "Find", "Copy" etc. NOTE: For an example, have a look at the "Advanced_feBrowser_CodeTemplates" procedure in the feabc.app examples.

CallFe_LoadMethod
Summary	Control Template To Do Optional
What does it do?	In order to use this code template, you must have already populated one of the Viewer Controls onto your window. Use this template ( typically in the event::accepted for a button ) to load a file into an existing Viewer Control.
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	To Do
What are my options?	Parent Object This drop list lists all the current File Explorer objects which are present in your procedure. Select the object which should load this file. Look in the Viewer Control's properties, on the "Class" tab to see its object name if you are unsure. File to Load Enter the name of the file which you want to load ( e.g. c:\MyFile.htm). Is Variable If you have entered a variable in the "File Name" field above, then check this option. Treat Unknowns As ( Obsolete ) NOTE: For an example, have a look at the "Advanced_feBrowser_CodeTemplates" procedure in the feabc.app examples.

CallFe_MediaAPIMethod
Summary	Control Template Optional
What does it do?	The template is typically used to play MP3 files in the "background" while your app is running (you don't lose focus while the file plays). It is typically used behind a button, but could also be used as your window opens to start playing an MP3 file "automatically" as the window opens. The code generated by this template calls functions in the File Explorer dll, which in turn implement the MCI (Windows Media Control Interface API), so no File Explorer objects need to be instantiated, and you do NOT need to have Windows Media Player installed, as we do not use the Media Player ocx at all here, only standard Win32 API calls.
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	See the feMedia_MCIExamples procedure in the feabc.app example application that ships with File Explorer.
What are my options?	Option This drop list lists all the options that the "MediaApi" method exposes. Pick one. File Name If you select the option "Play MP3" option from the "Option" drop list, then use this field to enter the name of the MP3 file which you wish to play, e.g. c:\myfile.mp3. If you selected "Stop MP3" from the above drop list, then simply leave this field blank. Is A Variable If you enter a variable in the "File Name" field above, then check this option.

CallFe_NavigateMethod
Summary	Control Template To Do Optional
What does it do?	In order to use this code template, you must have already populated one of the Viewer Controls onto your window. Use this template ( typically behind a button ) to implement the File Explorer "Navigate" method, and navigate to a specific page within the loaded document.
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	To Do
What are my options?	Parent Object This drop list lists all the current File Explorer objects which are present in your procedure. Select the object which should load this file. Look in the Viewer Control's properties, on the "Class" tab to see its object name if you are unsure. Navigate To Choose one of the positions to navigate to. Note that the "Go Back 1" and "Go Forward 1" options may behave differently depending on the type of file you are navigating. Typically these will navigate to the previous / next page or frame. PageNumber If you select "SpecificPage" as you "Navigate To" option, then you need to enter the page you want to navigate to in this field. NOTE: For an example, have a look at the "Advanced_fePDF_CodeTemplates" procedure in the feabc.app example application.

Declare FE Object
Summary	Control Template To Do Optional
What does it do?	This very simple code template simply instantiates (in code) a new object for the File Explorer class. When you use the "main" control templates (Viewer Controls etc) they create File Explorer objects for you, which you could then reference from your own code ( eg. ThisViewer1, ThisViewer2 ... ). You may want to write code that references the File Explorer class in a procedure which does not already have any File Explorer templates present, in which case you could either make (instantiate / declare) the object yourself, or simply use this template.
Prerequisites	You need to have added the Active_File_Explorer global extension template to your application.
How do I implement it?	To Do
What are my options?	Object Name Defaults to "ThisViewer1". You can rename the object if you prefer something else. All objects within the same procedure must have unique names. Object Type Select an object type from the drop list. NOTE: For an example, have a look at the "About" procedure in the feabc.app example.

Below are various functions that can be called from anywhere inside your application, so long as you have added the File Explorer Global Extension template.

fe_ClassVersion
fe_DebugString
fe_GetHtmlGraphicsInfo
fe_GetIEVersionInfo
fe_GetOSVersionInfo
fe_GetRegValue
fe_MCIPlay
fe_MCIStop
fe_OnlineStatus
fe_OnlineStatusConnectionName
fe_ShellExecute
fe_StartIE
feDispose

fe_ClassVersion

fe_ClassVersion ( byte Flag=0 )

Description

This method returns a string, containing File Explorer version information.
The information it returns depends on the (optional) Flag parameter.
- If you pass no parameter, or the value 0, the method returns the File Explorer Class Version - as seen at the top of the documentation.
- If you pass the value 1, the method returns the incremental dll version, as explained in the File Explorer Version Numbers section of the docs. This is useful for checking the dll version in your app, as you can use mathematical operators on the value that is returned.
- If you pass the value 2, the method returns a descriptive string containing the version details (as shown above).

Example

Example
MyString = fe_ClassVersion ( ) ! eg. '3.12' MyString = fe_ClassVersion (1) ! eg. '48' MyString = fe_ClassVersion (2) ! eg. '3.12 Beta'

fe_DebugString

fe_DebugString (string DbgMessage)

Description

See the section titled Using DebugView. This sends a debug message from within your own app. Usefulextra.

Example

Example
fe_DebugString('Hello World')

fe_GetHtmlGraphicsInfo

fe_GetHtmlGraphicsInfo (*cstring HtmlSource)

( not yet implemented )

fe_GetIEVersionInfo

fe_GetIEVersionInfo ( byte pTranslate=false ) ,string

Description

Returns the currently installed version of Internet Explorer.
If you pass true (1) for the pTranslate parameter, then the product name will be returned (if possible) - see the examples above.
See the Internet Explorer Version Info section for more info.

Example

Example
loc:TempString = fe_GetIEVersionInfo() ! 4.72.3612.1713 loc:TempString = fe_GetIEVersionInfo(true) ! Internet Explorer 4.01 SP2

fe_GetOSVersionInfo

fe_GetOSVersionInfo ( ),string

Description

This function returns the current Operating System. The syntax of the string returned is as follows:OS.MajorVersion.MinorVersion.BuildNumber; e.g. NTS.0005.0001.0000. We always return the string in the format XXXX.XXXX.XXXX.XXXX, to make string processing easier (i.e. ReturnString[1:4], ReturnString[6:9], ReturnString[11:14], ReturnString[16:19] ). Note that the OS component could be preceded by blank spaces ( e.g. " 95" ) to make string processing easier, while the remaining components will be preceded by zeros ( 0 ) if they are not 4 characters long, or will be clipped to the first four characters if they are longer. This may sound complicated but it makes coding much easier (as illustrated above).
The OS component of the string returned will be one of the following:
- 31 (Windows 3.1)
- 95 (Windows 95)
- 98 (Windows 98)
- ME (Windows Millennium)
- NTW (NT Workstation)
- NTS (NT Server)
- W2KP (Windows 2000 Professional)
- W2KS (Windows 2000 Server)
- 0000 (Four zeros indicates an unknown OS, please notify )

Example

Example
loc:TempString = fe_GetOSVersionInfo() if loc:TempString [3:4] = '95' ... loc:BuildNumber = loc:TempString [16:19] DisplayTextForScreen = left(loc:TempString)

fe_GetRegValue

fe_GetRegValue (string ParentFolder, string NameOfKey, string NameOfValue) ,string

Description

Reads a value from the Windows registry.

Example

Example
MyString = fe_GetRegValue ('HKEY_CURRENT_USER', 'Software\Microsoft\Internet Account Manager', 'Default Mail Account' )

fe_MCIPlay

fe_MCIPlay (string pFileName ) ,byte

Description

Every MCI (Media Control Interface) multimedia device supports a core set of MCI commands in a way that makes sense for that device. For example, the play ( MCI_PLAY, see MSDN for more info on the various Windows' API calls for this) command causes the open device to play a file or track, no matter what kind of data the device works with. File Explorer has wrapped up a lot of this functionality into two simple functions which you can call from anywhere in your Clarion application, fe_MCIPlay and fe_MCIStop.
fe_MCIPlay is used to play a variety of sound or video files, including MP3's (see the example above).

Example

Example
fe_MCIPlay ('c:\test.mp3')

fe_MCIStop

fe_MCIStop (<string pFileName> ) ,byte

Description

Every MCI (Media Control Interface) multimedia device supports a core set of MCI commands in a way that makes sense for that device. For example, the play ( MCI_PLAY, see MSDN for more info on the various Windows' API calls for this) command causes the open device to play a file or track, no matter what kind of data the device works with. File Explorer has wrapped up a lot of this functionality into two simple functions which you can call from anywhere in your Clarion application, fe_MCIPlay and fe_MCIStop.
fe_MCIStop is used to stop playing whatever file you started playing by calling the fe_MCIPlay function.
The omittable pFileName parameter is not currently supported, simply call this function as documented in the example above.

Example

Example
fe_MCIStop ()

fe_OnlineStatus

fe_OnlineStatus ( byte pOption=0 ) ,byte

Description

This function's purpose is to establish whether you are currently connected to the internet. The behaviour / result of the function is determined by the parameter pOption.
If pOption is omitted (or passed as zero), this function will simply return true (1) or false (0), indicating whether you are connected or not.
if fe_OnlineStatus() = 1
message ('I am connected!')
end
If pOption is passed as 1, 2, 3 or 4, this function returns the following:
- pOption=1; returns true / false indicating whether the local system is in offline mode
- pOption=2; returns true / false indicating whether the local system uses a modem to connect to the internet
- pOption=3; returns true / false indicating whether the local system uses a local network area to connect to the internet
- pOption=4; returns true / false indicating whether the local system uses a proxy server to connect to the internet
if fe_OnlineStatus(4) = true
message('You are connected through a Proxy Server')
end
If the function returns a negative number it indicates that an error occurred.

Example

Example
fe_OnlineStatus() ! see below

fe_OnlineStatusConnectionName

fe_OnlineStatusConnectionName ( byte pOption=0 ) ,string

Description

Use the fe_OnlineStatus function to establish whether you are connected to the internet. Use this function (fe_OnlineStatusConnectionName) if you want to know the name of the current connection (assuming there is one).

Example

Example
fe_OnlineStatusConnectionName()

fe_ShellExecute

fe_ShellExecute ( string Parm1 )

Description

( "Semi-private" function,called by the fe_StartIE function, wraps the ShellExecute API function )

fe_StartIE

fe_StartIE ( string URL )

Description

This function simply uses the ShellExecute API call to launch Internet Explorer and load a webpage.
TIP: Have a look in feabc.app's "Comments" procedure to see how to use this function to make urls on a window "live"...

Example

Example
fe_StartIE ('www.CapeSoft.com')

feDispose

feDispose()

Description

This function is used to clean up after File Explorer, and is called by the Global Extension Template as your app closes, to make sure File Explorer does not cause any memory leaks.

Example

Example
feDispose()

A couple of weeks ago Adobe released a "minor" update to Adobe Reader, version 11.0.07.

Unfortunately this build effectively drops support for directly embedding PDF's in Win32 programs.

This will affect Clarion programmers using the File Explorer PDF control in the app. All File Explorer versions, and all Clarion versions are affected.

Immediately after the release a number of threads about this issue appeared on the Adobe forums. This is affecting all existing Win32 programs, especially those written in VB6 and Delphi (not to mention Clarion) and is impacting users of apps that are no longer supported. At first Adobe appeared to be surprised by the problem, but the responses since then have been less encouraging that a fix will be found. (1)

Indeed a document issued into the knowledgebase appears that they have closed this subject, unfortunately without sorting out the root problem;

http://helpx.adobe.com/acrobat/kb/vb-60-64-bit-issue-11007.html

Indeed their document contains this simple gem;

"Because VB 6.x offers no 64-bit support, applications built with the VB6 environment no longer work."

So if you're running a VB6 app which includes the use of the Adobe OCX control - well, bummer for you. And the prognosis for Clarion programs is not a lot better (2).

Of the suggested work-arounds the one which seems to be the most practical is to simply swap the PDF control to a Browser control, and then open the PDF document in the browser. This approach requires a recompile of your application, but does not require any update to File Explorer. This change is trivial to implement (3) and will work for cases where you are just displaying the PDF - and allowing the user to navigate using the PDF viewer controls. At this stage it is not clear if any interactions with the PDF are possible - for example where you have created your own navigation or print buttons.

update (26 may): Peter Hermansen points out that another option is to open the PDF control outside the application in the PDF Reader itself. This can be done with the call fe_shellExecute(PdfFileName)

In the short term users who have upgraded to 11.0.7 can install either version 10.x (4) or 11.0.6 (5) as a temporary fix - however it's unlikely they will be able to remain on these old versions for ever.

(1) : Some threads about this issue on forums.adobe.com;

https://forums.adobe.com/thread/1475449

https://forums.adobe.com/message/6390890

https://forums.adobe.com/thread/1474731

https://forums.adobe.com/message/6400731

https://forums.adobe.com/message/6381248

(2) There is a _possibility_ that it may be possible to use what they are shipping directly in a Clarion app - we are looking into this, but honestly at this point I am not hopeful. Also, any possible fix we find in this area is likely to involve the need to release a new build of File Explorer. This would almost certainly be a problem for Clarion 6 users - I'm not sure we have the ability to make Clarion 6 builds anymore.

(3) Go to the Procedure Extensions, to the File Explorer Extension. On the General Tab, in the Object Type section, unselect the PDF (fePDF) option and select the HTML Browsing (feBrowser) option.

(4) Installing Adobe 10.x

a) Uninstall Adobe 11.0.7.

b) Make sure the folder C:\Program Files (x86)\Common Files\Adobe\Acrobat\ActiveX has been deleted (or� C:\Program Files \Common Files\Adobe\Acrobat\ActiveX for 32 bit versions of Windows.)

c) http://get.adobe.com/uk/reader/download/?installer=Reader_10.1.4_English_for_Windows&os=Windows%207&browser_type=KHTML&browser_dist=Chrome&d=McAfee_Security_Scan_Plus_Chrome_Browser&dualoffer=false

(5) Installing Adobe 11.0.6

a) Uninstall Adobe 11.0.7.

b) Make sure the folder C:\Program Files (x86)\Common Files\Adobe\Acrobat\ActiveX has been deleted (or� C:\Program Files \Common Files\Adobe\Acrobat\ActiveX for 32 bit versions of Windows.)

c) download and install 11.0.0 from http://www.adobe.com/support/downloads/detail.jsp?ftpID=5507

d) Then install the 11.0.6 update (manually) from http://www.adobe.com/support/downloads/detail.jsp?ftpID=5716

Tips & FAQ

Note: The old "Tips and FAQ" section can be found in the "fe_oldFAQs.htm" document. This section is being rewritten for the new classes.

General / Product FAQ's

1.1 When I click on the "Help" button for a template (Actions tab) I get an error saying "The topic file does not exist. Contact your application vendor for an updated Help file"...
You have an old copy of the File Explorer help file (c55fex.hlp). Search for all copies of this file, delete all of them, then reinstall the latest version of File Explorer.

1.2 "Link Error: Unresolved External Fe..." - how to handle these (compile) errors...
Several users who are using MultiProj to generate dlls which contain File Explorer have asked about this. In your app's Global Extensions, go to "Activate MultiProj Support", to the "Versions" tab, "Properties", "Resources", and make sure that you've included "c55fex(l).lib" as a resource.

1.3 Compile errors?
a) See the section "Considerations if upgrading...".

b) Also, check that your app is 32 bit, that you don't have bits of an old version of FE lying around, and that your redirection file is pointing to the paths where File Explorer is installed (3rdParty/bin, 3rdParty/libsrc etc).

c) Also, there seems to be an issue whereby some C55 installations (only C55 "G" as far as I know) have a window.tpw file which does not set up the %LocalClassDefinition embed point, which our templates use. It might be caused by running the "gold to G" patch, but this has not been confirmed. Contact

for the template.

1.4 Having multiple Viewer Controls on one window...
You may need to INIT the controls at window open and close at kill. Basically, you should only call the kill method for the controls that were inited.

1.5 Since upgrading my app won't compile - I get a compile error saying "Syntax error: Illegal data type" FEOLDBROWSER"
If you get this please email us at

.

1.6 Is there a way to see if a user has a live internet connection?
Yes. Have a look at the fe_OnlineStatus function.

1.7 I have a procedure that contains a File Explorer control. I pass a filename to this procedure and the control loads it. It used to work fine, but now it isn't working (loading the file)! What's happened?
In one of the earlier versions of File Explorer we used to initialize the onjects in ThisWindow::Init (after the window opens). Due to complications with some objects we moved this code (template generated) to after the event "after window opens". We sent out an email to let everyone know at the time..

1.8 On one of my test machines FE runs perfectly. On another machine the window containing the File Explorer control croaks as soon as it opens. Any ideas?
A user reported this and it turned out to be that he had an old version of the Windows "OLEPRO32.DLL" in his testing directory. Once he removed that dll all was fine.

1.9 I've noticed that in my c55\3rdParty\examples directory there is one folder called "FileExplorer" and another called "File Explorer"...
Please delete the one called "FileExplorer" (one word), it is from an early version of File Explorer - sorry about that..

1.10 I'm getting an error message "Entry Point Not Found / procedure entry point could not be located in the DLL PWUtil.dll"
Your app is using an old version of the file called "pwutil.dll". Use whichever version of this dll shipped with the version of File Explorer that you used when compiling the app.

1.11 I've heard that some Developers are using File Explorer with a Panel control rather than the Clarion OLE control, what's up with that???
This FAQ is no longer a recommended FAQ, since build 3.70 Gold you must change all old OLE controls to be PANEL controls or you will get compile errors. Click here for more information on this and for instructions on how to do this.

1.12 Is it possible to use SetPosition to move a File Explorer Viewer control? I can't get it to work...
Yes, but because of how we built File Explorer if you ever move or resize or hide or unhide the Panel control you need to tell File Explorer that you have done so, using our Resize method, as follows:
SetPosition (?feControl, 50, 50, 200, 250)
ThisViewer1.Resize()

FeBrowser FAQ's

2.1 When I try to browse a web page File Explorer does not "trigger" my "dial up networking" window! It just says that it can't find the webpage.
Enable the Dial Up Networking features from your Global Extension options.

2.2 I need to implement Callback events for the feBrowser object, where do I start?
Have a look at the "Advanced_feBrowser_SimpleCallbacks" procedure in the feabc.app example application.

2.3 I need to know when the loading page is done.
Check the feDemo example application the Callbacks examples for the browser demonstrate the use of the DocumentComplete callback. Also see DocumentComplete in the feBrowser documentation.

2.4 Can I detect when the control is going to load a new page, then change the url so it navigates to a different page?
Yes! How cool is that! Have a look at the "Advanced_feBrowser_SimpleCallbacks" procedure in the feabc.app example application. That example also shows how to simply cancel navigation to certain urls.

2.5 When I set ?feControl{prop:hide} the WebBrowser control is not hiding...
This is because unlike some of the File Explorer objects, the WebBrowser does not actually use the Clarion OLE control - we simply get window coordinates from its position and then create our own control "on top of it". You need to do the following in order to hide the control:

?feControl{prop:hide} = true
ThisViewer1.hidecontrol(1) !Where ThisViewer1 is the name of the FileExploreBrowser object in your procedure.

To unhide the control:

?feControl{prop:hide} = false
ThisViewer1.unhidecontrol(1) !Where ThisViewer1 is the name of the FileExploreBrowser object in your procedure.

2.6 "My app is working great on hundreds of installations, except one PC, where calling the FE window GPF's the app! Any ideas?"
A client reported this to me and all that fixed the problem was to have the client install all the latest IE critical updates from Microsoft. The case mentioned above was an installation of IE 6.0.2800.1106, on a Win 2K box.

2.7 I'm using File Explorer to complete a form... One of the text fields seems to be "un-settable"...
Use the feabc.app examples' "Accessing the DOM" example procedure to get a list of all the elements on the page. If the element you're trying to set is of element type "file" in the list, it is actually an HtmlInputFileElement (the html around that field will look like this: <INPUT type="file"... ), which Microsoft seem to have made a read-only object since Internet Explorer 5.0, for "security reasons". If anyone knows a way around this please let me know, otherwise there's not a lot that we can do here...

2.8 When I browse a webpage I get an "Internet Explorer Script Error" message popping up... Can I stop this from happening?
Yes. Have a look at the feBrowser::Update method, for the option called "SilentMode". See also question 2.18.

2.9 I have some html in a variable and I want the user to view it but not edit it. Is this possible?
Absolutely. At this stage only the feHtmlEditor object can load html directly from a variable (although we are working on the Browser). You will need to use the feBrowser::VarToFile method to create a temporary file from the html in the variable, then use the feBrowser::Load method to load that temporary file into the File Explorer control.

2.10 Is it possible to disable the popup menu in Internet Explorer (i.e. when a user right-clicks on a page)
Yes. There are two approaches to doing this. The first approach involves implementing the IDocHostUIHandler interface, which we plan on doing in a future release (which would enable us to actually add items to the popup menu, but requires a fair amount of time to code). The second approach is to simply use javascript. The javascript approach works well, but will obviously require you to add some script to your html pages. An example of how to do this can be found in the 3rdParty\Examples\File Explorer\Demo folder, as an html file called "no_popup_menu.htm".

2.11 In your feGoogle.app example you use File Explorer to fill in a search string and press the "Search" button on the Google site. Can I send the search string "directly" instead?
Yes. Use the Load method as follows:
ThisViewer.Load (' http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=%2BCapeSoft+%2BSoftware&btnG=Google+Search')

2.12 Does the feBrowser.Load method do a HTTP Post or a HTTP Get?
If you pass a string in the pPostData parameter the method will do a Post, otherwise it does a Get.

2.13 Is it possible to set which printer the WebBrowser control prints to without user intervention?
The PrintMe method prints the currently loaded document. If you call PrintMe(false) the document goes straight to the default printer. The only way we've found to change this behaviour (i.e. print to another printer) is by temporarily changing the default Windows printer. This will affect other software so only do this is you really need to. In the ThisViewer.PrintMe method, before the parent call, you would code as follows:

TempString = fe_GetRegValue ('HKEY_CURRENT_USER', 'Software\Microsoft\Windows NT\CurrentVersion\Windows', 'Device')
self.SetRegValue ('HKEY_CURRENT_USER', 'Software\Microsoft\Windows NT\CurrentVersion\Windows', 'Device', 'Fax602,winspool,FAX:')

and then after the parent call you need to restore the default printer to what is what originally, as follows:

self.SetRegValue ('HKEY_CURRENT_USER', 'Software\Microsoft\Windows NT\CurrentVersion\Windows', 'Device', TempString)

Note: This example will not work on all versions of Windows, a google search will reveal where the various versions of Windows store this setting in the Registry.

2.14 The GetInfo method can return the full html for the loaded page, using OuterHtml as the parameter I pass in. What if I only want a certain part of the html (for instance, the '<body>' tag) ?
Get the full html using GetInfo, then use INSTRING to get what you need from that html.

2.15 I want to use FE to fill in a form on a website, but the page does not appear to have any elements. Any ideas?
Use the feabc.app example's "feBrowser_DOM" procedure to get a list of the page's elements. If no elements are listed, set the "frame" spinbox on that example to 1, then 2, then 3 etc to make sure there aren't frames. Also right-click next to the fields you want to fill in, and choose "Properties" (in Internet Explorer) and check the URL. Sometimes login screens load separate html pages "inside" the parent page - if this is the case use that address (URL).

2.16 I am getting crashes opening certain pages multiple times.
If you are having problems with pages crashing when closing and then reopening a web site then please make sure the setting on the FileExplorer Extension "Implement Delayed Close" on the "BrowseHTML" tab is on. This is now the default option, however for existing controls it should be set manually when needed.

2.17 My website looks different when displayed in the FE browser in comparison with the IE browser installed.
IE seems to default to IE7 mode when the page does not explicitly say it's ready for IE10 - when the control is embedded in a program. This is best dealt with on the server side. If your webserver is built with NetTalk, then you need to upgrade your webserver to use NetTalk version 7.17 which has a work-around for this. Otherwise, you need to request the webserver administrator, to add the following meta-tag in the html header:

'<meta http-equiv="X-UA-Compatible" content="IE=10" />'

FeEditor FAQ's

Please see the feEditor documentation for usage of the feEditor, along with guides, example and documentation for all class methods.

3.1 How can I get a "new page" when using the feditor object?
Call the NewDocument method. Note that you do not need to call NewDocument unless you wish to clear the existing document and create a new one, as the editor starts with a new blank document. Also note that the EditorReady method must have been called before you can call any of the editor methods.

3.2 Is it possible to load html into the feEditor control, where the html contains images???
The HTML does not contain images, it simply links to them. You can call the SetHtml() method to load HTML from a string into the editor, or the Load() method to load an HTML file.

3.3 I need to implement Callback events for the feEditor object, where do I start?
The editor always has callbacks implemented see the Callbacks and Events documentation

3.4 Does the FeEditor object allow me to save the html I'm editing to a database field? I don't want to have to write to a file and then save that file in a database.
Yes, you call SetHtml to set the HTML for the editor and GetHtml to retrieve the HTML from the editor. The documentation for both methods includes example code which stores and retrieves HTML from a field in a database.

3.5 Does the FeEditor have a "Save As" method?
Yes, see the feEditor.SaveAs documentation.

3.8 Is there a way to check whether a page which I load has been edited by the user?
Use GetHtml to retrieve the HTML from the editor. The HTML content can be compared against the original content to check for changes.

3.9 On one machine the feEditor Control just doesn't work at all - or displays a message "Cannot find 'file:////T://feEditor.html". Make sure the path o Internet address is correct"
The editor requires the feeditor.html file and feeditor directory. See the Distribution section of the documentation. Note: In some circumstance you cannot use a mapped drive for the feEditor.html path, this will cause the "Cannot find" error.

3.10 Is it possible to get cleaner code back from the html, or without so much white space?
No, the editor returns what the HTML DOM provides. White space is ignored, and compresses well, so there is no real need to remove it. You can remove extraneous white space if you need to, in fact CapeSoft StringTheory has a 'squeeze' method which does just that.

3.11 The Editor gives me a strange path in the image URL.
The editor uses the path provided, it does not have any built in paths. It defaults to the current application path, unless the .editorPath property is set, in which case it uses that path as the default for the editor files.

3.12 I get different html code back (some with strange characters) back from the editor when using different PCs.
That would be the result of different versions of the DHTML editor and different character set and Unicode handling setting for the Operating Systems. If you are using invalid HTML characters (like the sterling pound sign) then you should encode that character, as they are invalid in HTML, and you can get a variety of incorrect rendering behaviours.

3.13 On one computer, no images are displayed (just show up with a red X). How do I fix this?
It is almost certainly a path or filename issue.

On the computer where it is not working, try putting the mouse over the image that has the X and right-click. Then look at the Properties to see the filename and path. Most likely you will find it incomplete, or perhaps with an extra backslash between the path and name, or just plain wrong (referring to a path or drive that is not available on that machine).

Or perhaps the Internet Explorer Settings on that machine is set to "not display images". Run IE and see if you see images there (and for what "zones").

Or possibly the local intranet settings are disabling the loading of the image. Your settings should be set as follows:

3.14. When I open the Editor window, my application crashes on certain PCs.

Try updating windows. Sometimes there are windows patches that cause the IE control to crash. Also, make sure that you include compatibility more for Windows 8 (and up) for your application.

FePDF FAQ's

4.1 When I load a PDF file I get an error message saying "There was a version error trying to launch the pdf control, version error 6.x"
This was an incompatibility between FE and Internet Explorer 6. Fixed in File Explorer version 2.5c.

4.2 I have the fePDF object on a tab. Each time I select another tab then return to that one my document has disappeared!
This is an issue with the ole control. In the future we will redo the PDF object from scratch (which will hopefully take care of this problem); but until then have a look in the feabc.app example app, at the "MultpileObjects_Example1" procedure which shows how to fix this until then.

4.3 The PrintMe method does not seem to work!
As documented <g>, this method only works if you set the "Use Acrobat 4" setting in the template. See the docs.

4.4 I can't seem to view PDF files...
If you double-click on a PDF file in Windows Explorer does it open? Can you view PDF files on your computer using Internet Explorer? If not then the problem is with your Adobe Acrobat installation, not with File Explorer. We can't use components that are not installed, or are installed but not working. Try reinstalling Acrobat Viewer from adobe.com.

4.5 I get a GPF when I try and load a PDF file
There were a couple of versions of Adobe 9.5 that displayed this issue. Upgrading to Adobe 10 or higher should resolve this.

4.6 I've disabled the toolbar, but I still get the floating toolbar, which offers me the ability to turn the toolbar on. How do I disable this?
The floating toolbar only appears when a document is in "Read Only" mode. Adobe default settings state to open in "Read Only" mode. In Adobe under Edit/Preferences/Internet (on side bar menu) ensure that the "display in read mode" is unchecked. Now when opening document via FileExplorer with the toolbar hidden, the floating toolbar does not appear. Unfortunately (at the time of writing this) there is no access to manipulate this setting through the COM control.

A caveat: the above settings to Adobe are profile specific so if you login with profile 1 make changes, then login as profile 2 the settings are not there. Login as profile 1 again and they are still in effect.

FeMedia FAQ's

5.1 When I type a filename into the Entry control and press the Tab key it loads, but if I press the Enter key nothing happens...
This can be fixed by simply deleting the feMedia control from the window, closing the window, reopening the window, and repopulating the feMedia control.

5.2 How do I know when a music file has finished playing so that I can load another one from code?
Have a look at the feabc.app example --> under the FeMedia menu there is an example of how to use the EventCallback method to watch for when songs finish playing.

NetTalk / FileExplorer FAQ's

6.1 I am using NetTalk and File Explorer to write an email program. I'm having a problem getting something to work...
Have a look for the demo app called "fenetalk.app" that came with File Explorer. It's a simple app showing the basics of getting File Explorer and NetTalk to "work together", demonstrating how to use NetTalk to send and receive emails, and File Explorer to view and edit the emails.

6.2 How do I embed images into the mail composed by FileExplorer?
You need to call the EmbedImages method to modify the HTML and embed the images. The HTML needs to be modified so that the image references are in the embedded "cid" format. See EmbedImages for details.

The undocumented feStorage Class FAQ's

7.1 I am using the feStorage class, but it does not work with the current version.
This class has not been supported since FileExplorer 2, and has been permanently deprecated in FileExplorer 5. The functionality is trivial to implement, and examples will be provide of implementing this very simply.

Examples

When you install File Explorer, several demo applications are installed in your C55\3rdParty\Examples\File Explorer folder. These examples are listed below, in alphabetic order.

BackgroundPrint

Demonstrates loading a page and printing it in the background, without any user interaction required.

"Demo" (important) - abc, feabc.app
This is the main example application. It shows off most of File Explorer's objects and features. We highly recommend going over this example application.

"Demo Legacy" - legacy, feleg.app
This is similar to the feabc.app example, but is written using the legacy templates (not ABC), and doesn't show off nearly as many features as the feabc.app example. The same classes are used for both Legacy and ABC, so we recommend using the ABC example as your primary reference.

Editor Files (important)

This is not an example, but it contains the files that are required for the HTML editor. The contents of this folder should be copied to your application directory when using the editor.

EmailHtml (requires Nettalk) (new)

This demonstrates loading and HTML from disk using the feFile class; embedding images using feEditor; automatically creating a text version (the example uses NetWebClient, however the feBrowser class provides an excellent option for doing this); and of course, sending the email with the HTML part, text part, and any local images embedded. (this app will not compile unless you own CapeSoft NetTalk, available here).

Full Screen - abc, fullscrn.app
This example shows how to play a media file (movie) using the entire screen to show the movie.

LoadFromList

Loads the feBrowser from a Clarion List control. When an entry in the list is selected, that entry is loaded into the feBrowser control. This is one of the many common uses of the Browser control.

NetTalk (requires Nettalk)

This example shows the overlap between File Explorer and another CapeSoft product, called NetTalk (this app will not compile unless you own CapeSoft NetTalk, available here).

Office Inside - abc, FeOi.app
This app demonstrates how to integrate File Explorer with CapeSoft Office Inside (this app will not compile unless you own Office Inside, available here).

RtfToHtml (new)

Converts an RTF file to HTML using the feEditor object. The resultant HTML can be displayed or edited as required. Does not required any tools other than Clarion and FileExplorer, and only requires Internet Explorer to be installed on the machine. This is a Clarion 6 example, although the same technique can be used with any version of Clarion that FileExplorer supports (5.5 and up).

�

Upgrading from FileExplorer 4 to FileExplorer 5

FileExplorer 5 introduces a number of exciting new features (check out the What's new In FileExplorer 5 section in this doc for details), and at the same time we have built in backward compatibility.

What must I do to upgrade?

You need to purchase an upgrade from www.clarionshop.com (Why is Capesoft charging for an upgrade?)
Run the FileExplorer 5 installer (you've probably done that if you're reading this).
By default any HTML editor controls will use the new feEditor class and any media controls will use the new feMediaPLayer2 class. If you want to use the old version of either of these controls, simply go to the local FileExplorer extension template and tick the checkbox to use the old version under the Actions for the control.

As much as possible the new classes implemented a backward compatibility layer, so most things will continue to work. The feMedia2 class has a number of areas where the functionality of the control changed to such an extent that there are no direct equivalents of the old methods, in this case class implements functionality that is as close to the old class as possible and calls the ErrorTrap() method with a warning message.

The documentation also lists which methods are still under construction, so if you come across something that is not working please email us so that we can correct the issue.

My saf password does not work on the latest File Explorer install. Where do I get a new password?

In File Explorer version 5.00 Capesoft introduced a paid-for upgrade, which means that the unlock code changed. You can continue using File Explorer 4 and downloading the necessary install files with your existing File Explorer 4 saf code, or you can upgrade to File Explorer 5 (and make the most of all the functionality offered in the File Explorer 5 package). For information on how to upgrade go to.

Considerations if upgrading from a version earlier than 3.70 Gold

Version 2.9 Beta of File Explorer saw the first changes that made the product non backward-compatible. After two years of evolution, we reached a point where our initial design was severely restricting future design, so we decided to clean things up and restructure File Explorer where necessary. Below is a list of what we've changed, the compile errors you will see, and explanations as to why we changed certain things and what you need to do to get your code to work. Version 3.70 Gold was the first Gold build in almost two years, and should see the end of changes that cause backward-compatibility issues. Below is an outline of what you need to change in your applications if upgrading from an old version of File Explorer (prior to 3.70 Gold), and a list of compile errors you could get and how to correct the code that causes these errors.

We followed the instructions below to convert our feabc.app example app, which contains over 40 windows which host FileExplorer controls, it took 7 minutes to make all the necessary changes and get it to compile...

What you need to do to your existing apps that use a version of FE earlier than 2.9 Beta

Open each window (one by one) which contains a File Explorer Viewer control.
File Explorer would have populated an entry control on this window ( see "A" below )...
...which will be "Use"-ing a variable called "fepath" ( see "B" below )...
You need to change this as follows: If you only have one Viewer control on a window, change it from "fePath" to "?fePath1". If you have more than one Viewer control on a window, change the controls as follows; "?fePath1", "?fePath2", "?fePath3" etc. It doesn't matter if ThisViewer1 has ?fePath4 (although I'd recommend matching the use variables to the Object names to make the code cleaner), so long as each entry control has a unique use variable.

Compile Errors and how to fix them:

Compile Error 1Error:
Syntax error: Unknown identifier: FEPATH
Syntax error: Unknown identifier: FE_APPPATH
Syntax error: Unknown identifier: FE_LASTPATH
Syntax error: Unknown identifier: FE_CURRENTPATH
Syntax error: Unknown identifier: FE_CURRENTCONTROL
Syntax error: Unknown identifier: FEHEIGHT1
Syntax error: Unknown identifier: FEWIDTH1
Syntax error: Unknown identifier: FEHTML1BUSYRECOVERING
Syntax error: Unknown identifier: FEPRIORLASTEVENT

Cause:
You have written code that makes reference to one of the above variables (Fe_AppPath, Fe_LastPath, Fe_CurrentPath or FePath ) which no longer exist. Or, in the case of the FEPATH error, you need to run through the section above titled "What you need to do to your existing apps..."

Fix:
You need to replace any code where you refer to these variables with the new properties, as shown below:

Replace fe_AppPath with ThisViewer.fe_AppPath
Replace fe_LastPath with ThisViewer.fe_LastPath
Replace fe_CurrentPath with ThisViewer.fe_Path
Replace fePath with ThisViewer.fe_Path
Replace fe_CurrentControl with ThisViewer.fe_CurrentControl
Replace feHeight1 with ThisViewer.fe_Height
Replace feWidth1 with ThisViewer.fe_Width
feHtml1BusyRecovering (global variable) is no longer used, simply delete your code, it is no longer necessary.
fePriorLastEvent (global variable) is no longer used, simply delete your code, it is no longer necessary.

Note: If your object is not called "ThisViewer" you will need to use its name instead. You can find out what an object is called by clicking on the "Object" tab, from the "Actions" tab or your File Explorer control. By default objects are named "ThisViewer1", "ThisViewer2" etc.

Compile Error 2

Error:
ASSERT: Procedure "(procedure name)" is using an OLE control, not a panel

Cause:
File Explorer started off using the Clarion OLE control. Due to stability issues, we eventually moved all code in File Explorer to use the Plugware OLE container code, so File Explorer no longer uses Clarion's OLE control at all. Any File Explorer controls that you added to your app prior to version 2.9 would have populated a Clarion OLE control onto your window, which now needs to be changed to a PANEL control.

Fix:
First, please backup your app. Once you have done that, simply go to each procedure that contains an old File Explorer control (which still uses an OLE control, not a PANEL - the compile errors above will list which procedures contain the OLE controls), right-click on a procedure, choose Properties, then click on the ellipsis button immediately to the right of the Window button, this will let you edit the window definition for that procedure. Look for the code that looks like this:

OLE,AT(114,101,299,135),USE(?feControl),#SEQ(17),#ORIG(?feControl)
END

This is the OLE control that needs to be changed to a PANEL control. Simply delete the two lines of code (above), and replace them with this single line of code (note, all you're doing is changing OLE to PANEL, and deleting END) :

PANEL,AT(114,101,299,135),USE(?feControl),#SEQ(17),#ORIG(?feControl)

That's it!

Other changes you need to know about:

We are no longer supporting the Background Media Load Button control template, please use the CallFe MadiaAPIMethod code template instead.
Callback events are now done completely differently. Please see the example apps and look at the EventCallback methods to see how this is now done. Any code you have in the old callback event embed points will need to be redone, and will more than likely now be orphaned.

Internet Explorer Version Info

( This information was found at http://support.microsoft.com/default.aspx?scid=kb;en-us;164539 )

4.40.308	Internet Explorer 1.0 (Plus!)
4.40.520	Internet Explorer 2.0
4.70.1155	Internet Explorer 3.0
4.70.1158	Internet Explorer 3.0 (OSR2)
4.70.1215	Internet Explorer 3.01
4.70.1300	Internet Explorer 3.02 and 3.02a
4.71.544	Internet Explorer 4.0 Platform Preview 1.0 (PP1)
4.71.1008.3	Internet Explorer 4.0 Platform Preview 2.0 (PP2)
4.71.1712.6	Internet Explorer 4.0
4.72.2106.8	Internet Explorer 4.01
4.72.3110.8	Internet Explorer 4.01 Service Pack 1 (SP1)
4.72.3612.1713	Internet Explorer 4.01 Service Pack 2 (SP2)
5.00.0518.10	Internet Explorer 5 Developer Preview (Beta 1)
5.00.0910.1309	Internet Explorer 5 Beta (Beta 2)
5.00.2014.0216	Internet Explorer 5
5.00.2314.1003	Internet Explorer 5 (Office 2000)
5.00.2614.3500	Internet Explorer 5 (Windows 98 Second Edition)
5.00.2516.1900	Internet Explorer 5.01 (Windows 2000 Beta 3, build 5.00.2031)
5.00.2919.800	Internet Explorer 5.01 (Windows 2000 RC1, build 5.00.2072)
5.00.2919.3800	Internet Explorer 5.01 (Windows 2000 RC2, build 5.00.2128)
5.00.2919.6307	Internet Explorer 5.01 (Also included with Office 2000 SR-1, but not installed by default)
5.00.2920.0000	Internet Explorer 5.01 (Windows 2000, build 5.00.2195)
5.00.3103.1000	Internet Explorer 5.01 SP1 (Windows 2000)
5.00.3105.0106	Internet Explorer 5.01 SP1 (Windows 95/98 and Windows NT 4.0)
5.00.3314.2101	Internet Explorer 5.01 SP2 (Windows 95/98 and Windows NT 4.0)
5.00.3315.1000	Internet Explorer 5.01 SP2 (Windows 2000)
5.50.3825.1300	Internet Explorer 5.5 Developer Preview (Beta)
5.50.4030.2400	Internet Explorer 5.5 & Internet Tools Beta
5.50.4134.0100	Windows Me (4.90.3000)
5.50.4134.0600	Internet Explorer 5.5
5.50.4308.2900	Internet Explorer 5.5 Advanced Security Privacy Beta
5.50.4522.1800	Internet Explorer 5.5 Service Pack 1
5.50.4807.2300	Internet Explorer 5.5 Service Pack 2
6.00.2462.0000	Internet Explorer 6 Public Preview (Beta)
6.00.2479.0006	Internet Explorer 6 Public Preview (Beta) Refresh
6.00.2600.0000	Internet Explorer 6 (Windows XP)
6.00.2800.1106	Internet Explorer 6 Service Pack 1 (Windows XP SP1)
6.00.3663.0000	Internet Explorer 6 for Microsoft Windows Server 2003 RC1
6.00.3718.0000	Internet Explorer 6 for Windows Server 2003 RC2
6.00.3790.0000	Internet Explorer 6 for Windows Server 2003 (released)

Header / Footer Strings for IE Page Setup

If you open Internet Explorer and click on "Page Setup" ("File" menu), then click on the question mark on the "Page Setup" dialog window's title bar, then click in the "Header" field, you should see a list of possible settings.

This list in IE 5.5 contains the following:

&w	Window Title
&u	Page address (URL)
&d	Date in short format
&D	Date in long format
&t	Time (as per Control Panel)
&T	Time in 24-hour format
&p	Current page number
&P	Total number of pages
&&	A single ampersand (&)
&b	Text to follow is centered
&b&b	Text after the second "&b" is right-justified

Using DebugView

"DebugView" by SysInternals is an application that lets you monitor debug output on your local system. I use DebugView when developing because it gives an accurate picture as to what's happening in your code (as opposed to "messages" or "stops"). If you start your application (any application into which File Explorer is compiled) with the following command line parameters, debug output will be generated accordingly, which you can then monitor using DebugView.

MyApp.exe	same as MyApp.exe /fedebugoff
MyApp.exe /fedebugoff	almost no debug output
MyApp.exe /fedebugmin	minimum amount of debug output
MyApp.exe /fedebugmax	maximum amount of debug output

TIP: I'd recommend using debug output only when you're testing something. It can be quite annoying for other programmers to work on a system where there are a dozen different apps generating debug output at the same time! To make life easier, all File Explorer debug messages are prefixed with "FE", as shown below. You can set DebugView to ignore all messages that do not contain "FE". You will also take a performance hit when running an app with debugging turned on.

debug view screenshot

File Explorer and The Future (The "ToDo" List)

Over the years, the vast majority of features on this list have been added. If there is something that you feel is missing, or would be a valuable addition, please email us. We value our user feedback, and many of the changes and new features are based entirely on user feedback.

File Explorer Version Numbers

Please ensure that you are using the latest release of File Explorer and all the current DLLs, including pwutil.dll. The bulk of all support requests regarding FE are a result of old DLLs, LIBs or source files.

pwutil.dll - version 2.5.0.0 (This file must be shipped with all FE application. It is backward compatible, so it is advised that you always ship the most recent release.)

All other files (binaries etc.) will reflect the current version number in the History section.

Version 5.68 - 24 May 2021

First Clarion 11.1 build

Version 5.67 - 23 December 2019

Change: PWDISPATCH renamed to CSPWDISPATCH to match OfficeInside.

Version 5.66 - 11 October 2019

Fix: Ability to attach data to a Post. (Thanks to Rick Martin.)

Version 5.65 - 14 March 2019

Fix: (maybe) - IE hanging on keyboard input in Windows 10 1809 release.

Version 5.64 - 28 November 2018

Fix: Fixed unresolved external TRACE@F6FEFILEsb error.

Version 5.63 - 13 Sept 2018

Add: Clarion 11 to install.

Version 5.62 - 18 May 2017

Trace method added to most classes.
Some internal refactoring

Version 5.61 - 20 October 2016

Renamed GetProperty method to feGetProperty. Renamed SetProperty method to feSetProperty (method names were causing a problem when compiling in apps with H5).
Fix: Media control would choke when playing two different media files.

Version 5.60 - 24 December 2015

Extended string so URL can be longer than 255 bytes in callback methods.

Version 5.59 - 25 February 2015

Removed unnecessary calls to %cwversion - better for Clarion 10 support.

Version 5.58 - 24 February 2015

Clarion 10 compatible build.

Version 5.57 - 2 October 2014

Fix: If an Html Editor control was not visible when the window opened, then EditorReady event would not fire, and some Script error messages were possible.

Version 5.56 - 17 July 2014

Fix: If the program was run from a root drive location, then the htmlEditor files would not load.

Version 5.55 - 10 February 2014

Include C9.1 binaries
Tweak to handle unhiding the FE Control (which does not have a parent).

Version 5.54 - 27 September 2013

Include C6 binaries (old versions required updating)

Version 5.53 - 28 August 2013

Include C9 binaries for 10324 support.
get_durationString returns 'Error' if duration is not valid.
Improved support for linking - use correct name (instead of including %V% and %L% - cwproj does not always resolve these correctly).
Improved setting of template generated media control properties (use update method rather than the properties directly)

Version 5.52 Gold (26 April 2013)

Update: HTMLEditor (CKEDITOR) updated from version 3.x to version 4.x.

Version 5.51 Gold (25 April 2013)

MultiProj fixes for C7 and up - adds the correct clafe lib to the project (and the pwutil.lib as well).
c7 and up fix - Copies the clafe.dll to the output on exe compile.
Add Don't generate any code (to the DocumentViewer local template on the general tab) and allowed positioning of the controls when adding the control template.
Prevent GPF if SetFileName is passed a blank filename (just dir, or no filename).
FeBrowser.Load class treats file:// as a local file.
Clarion 9 DLL included in install

Version 5.50 Gold (29 February 2012)

General

Updated the Demo example and removed old code and procedures

feMedia

Added: New callback handling to the feMedia2 class.
Added: TranslateEventID method to translate an event ID into a human readable string describing the event
Added all new events to the new event callbacks
Added parameter support for all new events. See the feMedia2.EventCallback method for more information.
The following events are now supported:
- fe:DISPID_WMPCOREEVENT_OPENSTATECHANGE 'Open Stated Changed'
  fe:DISPID_WMPCOREEVENT_STATUSCHANGE 'Status Changed'
  fe:DISPID_WMPCOREEVENT_PLAYSTATECHANGE 'Play State Changed'
  fe:DISPID_WMPCOREEVENT_AUDIOLANGUAGECHANGE 'Audio Language Changed'
  fe:WMPCOREEVENT_SEEK_BASE 'Seek Based'
  fe:DISPID_WMPCOREEVENT_ENDOFSTREAM 'End Of Stream'
  fe:DISPID_WMPCOREEVENT_POSITIONCHANGE 'Position Changed'
  fe:DISPID_WMPCOREEVENT_MARKERHIT 'Marker Hit'
  fe:DISPID_WMPCOREEVENT_DURATIONUNITCHANGE 'Durantion Unit Changed'
  fe:DISPID_WMPCOREEVENT_SCRIPTCOMMAND 'Script Command'
  fe:DISPID_WMPCOREEVENT_DISCONNECT 'Disconnected'
  fe:DISPID_WMPCOREEVENT_BUFFERING 'Buffering'
  fe:DISPID_WMPCOREEVENT_NEWSTREAM 'New Stream'
  fe:DISPID_WMPCOREEVENT_ERROR 'Error'
  fe:DISPID_WMPCOREEVENT_WARNING 'Warning'
  fe:DISPID_WMPCOREEVENT_CDROMMEDIACHANGE 'CD ROM Media Changed'
  fe:DISPID_WMPCOREEVENT_PLAYLISTCHANGE 'Playlist Changed'
  fe:DISPID_WMPCOREEVENT_MEDIACHANGE 'Media Changed'
  fe:DISPID_WMPCOREEVENT_CURRENTMEDIAITEMAVAILABLE 'Current Media Item Available'
  fe:DISPID_WMPCOREEVENT_CURRENTPLAYLISTCHANGE 'Current Playlist Changed'
  fe:DISPID_WMPCOREEVENT_CURRENTPLAYLISTITEMAVAILABLE 'Current Playlist Item Available'
  fe:DISPID_WMPCOREEVENT_CURRENTITEMCHANGE 'Curernt Item Changed'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONCHANGE 'Media Collection Changed'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONATTRIBUTESTRINGADDED 'Media Collection Attributes Changed'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONATTRIBUTESTRINGREMOVED 'Media Collection Attribute String Removed'
  fe:DISPID_WMPCOREEVENT_PLAYLISTCOLLECTIONCHANGE 'Playlist Collection Changed'
  fe:DISPID_WMPCOREEVENT_PLAYLISTCOLLECTIONPLAYLISTADDED 'Playlist Added'
  fe:DISPID_WMPCOREEVENT_PLAYLISTCOLLECTIONPLAYLISTREMOVED 'Playlist Removed'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONCONTENTSCANADDEDITEM 'Content Scan Added Item'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONCONTENTSCANPROGRESS 'Content Scan Progress'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONSEARCHFOUNDITEM 'Search Found Item'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONSEARCHPROGRESS 'Search Progress'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONSEARCHCOMPLETE 'Search Complete'
  fe:DISPID_WMPCOREEVENT_PLAYLISTCOLLECTIONPLAYLISTSETASDELETED 'Playlist Set As Deleted'
  fe:DISPID_WMPCOREEVENT_MODECHANGE 'Mode Changed'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONATTRIBUTESTRINGCHANGED 'Attribute String Changed'
  fe:DISPID_WMPCOREEVENT_MEDIAERROR 'Media Error'
  fe:DISPID_WMPCOREEVENT_DOMAINCHANGE 'Domain Changed'
  fe:DISPID_WMPCOREEVENT_OPENPLAYLISTSWITCH 'Open Playlist Switch'
  fe:DISPID_WMPCOREEVENT_STRINGCOLLECTIONCHANGE 'String Collection Changed'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONMEDIAADDED 'Media Added'
  fe:DISPID_WMPCOREEVENT_MEDIACOLLECTIONMEDIAREMOVED 'Media Removed'
Added documentation for parameters for common events.

Version 5.40 Beta (05 January 2012)

General

Changed: The feHtmlEditor FAQ section in the documentation references the old feHtmlEditor class. This has been updated to the new feEditor class.
Updated: The GetHtml and SetHtml method documentation has been simplified and new examples added.
Added: Versions of the GetHtml and SetHtml methods which store and retrieve the HTML to and from BLOB fields. This allows HTML to be loaded into a BLOB field with a single line of code:
HtmlEditor.GetHtml(MyTable.BlobField)

and to be retrieve from a BLOB and loaded into the editor:

HtmlEditor.SetHtml(Mytable.BlobField)
Added: The new GetHtml and SetHtml methods for BLOBs to the Demo example
Updated: The Demo example to simplify some of the editor code and better demonstrate using GetHtml and SetHtml.

Version 5.39 Beta (24 October 2011)

General

Added: Quick Guides section to the documentation that covers easily implementing common functionality.
Fixed: Template support for Multi-Proj adding the correct LIB files

Version 5.38 Beta (10 August 2011)

General

Updated: Modified LIB to prevent duplicate symbol errors in C7.3 and C8 when compiled in LIB mode with OfficeInside in the same project.

Version 5.37 Beta (6 June 2011)

General

Fixed: Compatibility with OfficeInside in Clarion 8 (resolved duplicate symbol _vtbool error in C8)

Version 5.36 Beta (24 May 2011)

feEditor

Fixed: The feEditor Image dialog was missing the Browse button that allows files to be selected from the local machine

Version 5.34 Beta (19 May 2011)

feEditor

Updated: The editor has been updated to support CKEditor 3.6.0.
Fixed: The feEditor.GetHtml() method was being derived by the template without the return type in the prototype.
Fixed: The ckeditor.js file was damaged in the previous installer. This resulted in the editor not loading correctly.

Version 5.33 Beta (13 May 2011)

feEditor

Updated: The editor has been updated to support CKEditor 3.5.3.

Important: Please update your editor files to those in the \Examples\FileExplorer\Editor Files\ directory.
Added: Additional event handling to allow the NewPage event to be trapped. When the New Page button is pressed the TakeEvent method will fire with 'newpage' as the event string.
Updated: The Maximize button is no longer hidden using the DOM, which provides better reliability when editing the toolbar.
Updated: Verified the behaviour for GetHtml and GetText is correct in the latest release when the contents of the control are deleted (the document is returned as empty, and not as the contents before the delete was performed).

Version 5.32Beta (5 May 2011)

feEditor

Fixed: The closedown code generated for the Editor control was occuring too early when used on an ABC form procedure, which would cause the editor's Kill method to be called when the window close event fired but the window was not closed. If the user cancelled the form close this would result in the editor already having been killed and a blank control would be displayed.

Version 5.31Beta (4 April 2011)

feEditor

Updated: The SpellCheck HTML example application which demonstrates spell checking using OfficeInside:
- Requires OfficeInside 3.
- Removed old code
- Initial HTML populated into the control to demonstrate the use of the EditorReady method as well as populating the control for formatted HTML with a number of spelling errors for spell checking.
- Updated the Editor Files being used by the example

Version 5.30 Beta (28 March 2011)

Added: feMedia.setMode method
Updated: feMedia.getMarkerTime method to return the marker time more accurately.
Added: feMedia.isReadOnlyItem method.
Added: feMedia.put_name method.
Added: feMedia.setItemInfo method.
Updated: The documentation for the feFlash and feMedia classes.
Added: FeBrowser.SaveAs() method. Saves the currently loaded to disk as an HTML file using the file name specified. Optionally appends to the file rather than overwriting it (if it exists)
Updated: The feBrowser documentation. Added new methods, improved consistency, added JavaScript based dynamic code highlighting.
Added: New examples using FileExplorer with OfficeInside:
- HtmlSpellCheck - Spell checking HTML using OfficeInside and the feEditor
- WebToDoc - Save a loaded page as a Word Doc
- Word to MHT, EML - Save a Word Doc as an MHT (Web Archive) or EML (MIME format Email) and display the result using FileExplorer

Version 5.29 Beta (08 February 2011)

Fixed: Duplicate symbol errors with Nettalk 5.15 in Clarion 7.3

Version 5.28 Beta (13 December 2010)

This version is compatible with Clarion 7.3

Version 5.27 Beta (09 September 2010)

Changed

FeFlash.GetSWFHeader - opens the file in Read mode, to prevent failures when write access to the file is not available (the method requires only read access to the file).
The feFile.Save procedures have been modified to prevent ambiguity in the call
Fixed the feEditor.Save method saving to the application folder even when the file was loaded from another location.
Added a feEditor.fullPath property that contains the full path and file name of the loaded document.

Version 5.26 Beta (10 May 2010)

New

Clarion 7.2 compatibility

Fixed

Resolved duplicate symbol error in C7.1 in local (lib) mode for apps using FileExplorer and OfficeInside.
Resolved a duplicate symbol error in C7.1 in local mode when using both the Topspeed and DB4 file drivers and Insight Graphing with OfficeInside and FileExplorer.

Version 5.25 Beta (04 March 2010)

New

feEditor: Added .initialDocument property. Setting this will load this document when the editor completely initialisation. Calling Load() before the editor is ready now sets this property and returns. The document will then be loaded once the editor has completely loading.
feEditor: Added support back to the template for the Initial Document setting. Existing code continues to function exactly as per previous releases.
feEditor: Added a Browse option to the Image dialog to allow the image to be selected from disk. This will be improved further in future releases.
feEditor: Editing mode now uses the full page by default (rather than just the body). This can be configured in the feeditor.html by changing the fullPage setting to true ot false.
feEditor: The editor no longer inserts a <base> tag to set the base path. The editor internally sets the base href for relative URLs when a document is loaded or saved.

Fixed

Duplicate symbol errors and compilations issues.
feEditor: Fixed incorrectly set base path when using the editor, which was resulting in the base path always being set to the application (current) directory (note: this functionality has now been superceded).
feEditor.currentPath missing a slash between the path and file name.
feEditor loading a blank page after the Save command is used from the toolbar.
feEditor: When a document was loaded, and then F5 was used to refresh/reload the browser, the document file name was still stored by the editor, so using the Save command would save the newly blanked documented.
feEditor: The <base> tag would be inserted each time a document was opened.

Notes

feEditor: The PreTakeEvent() method is disabled in this version.

HTML Editor Additions

Introduced the full page editing support (from <html> to </html>).
Introduced the Shared Spaces feature.
Introduced the new powerful pasting system and word cleanup procedure, including enhancements to the paste as plain text feature.
Introduced the new native PHP API, the first standardized server side support.
Added CKEditor plugin for jQuery.
Added 'div' dialog and corresponding context menu options.
Added the table merging tools and corresponding context menu options.
Added the email protection option for link dialog.
Added inline CSS support in all places where custom stylesheet could apply.
Added color dialog for 'more color' option in color buttons.
Added the 'showborder' plugin.
Make the anti-cache query string configurable.
Added the 'htmlEncodeOutput' config option.
Introduced the bodyId and bodyClass settings to specify the id and class. to be used in the editing area at runtime.
Introduced the baseHref setting so it's possible to set the URL to be used to resolve absolute and relative URLs in the contents.
Added support to fake elements for comments.

HTML Editor Fixes

Fixed invalid link is requested in image preview.
Fixed toolbar separator line along side combo enlarging the toolbar height.
Fixed image re-size lock buttons aren't accessible in high-contrast mode.
Fixed editing tables using table properties dialog overwrites original style values.
Fixed IE6 JavaScript error when editing flash by commit 'Flash' dialog.
Fixed 'wysiwyg' mode causes unauthenticated content warnings over SSL in FF 3.5.
Fixed open context menu in IE throws js error when focus is not inside document.
Fixed applying 'Headers' to existing table does not work in IE.
Fixed unexpected margin style left behind on content cleaning up from MS-Word.
Fixed paste nested list from MS-Word with measurement units set to cm is broken.
Fixed unable to undo pre-formatted style.
Fixed when paste happen from dialog, it always throw JavaScript error.
Fixed paste plain text result incorrect when content from dialog.
Fixed unable to undo 'New Page' command after typing inside editor.
Fixed table alignment style is not properly represented by the wrapping div.
Fixed switching mode when maximized is showing background page contents.

Version 5.23 Beta (29 January 2010)

New

New EmailHtml Example (requires NetTalk)

This demonstrates loading and HTML from disk using the feFile class; embedding images using feEditor; automatically creating a text version (the example uses NetWebClient, however the feBrowser class provides an excellent option for doing this); and of course, sending the email with the HTML part, text part, and any local images embedded. Requires NetTalk for email sending.
New Explorer example.
This example demonstrates how to build Windows Explorer into a window within your application. It supports navigation of the file system, copying and pasting files, renaming etc. It also allows dragging and dropping of files into your Clarion application and so on.
New: Cleaned up the toolbar, removed extraneous options and reduced the space required.
New: New section in the docs describing toolbar customisation, how to switch between toolbars, and further information on customising the editor.
New: Added a full and minimal toolbar to the feeditor file. The toolbar can be easily customised, and the different toolbars can be switched between without recompiling the application (or even restarting it, simply close the window that contains the editor and open it again). This process is described in the Customisation section.
New: Added the var keyword to JavaScript variable declarations to ensure that all JavaScript used is strict JS compliant.

Fixed

Fixed: Assert statements incorrectly firing for some versions of Clarion 7.
Fixed: the feEditor.GetText() method only returning the first line.

Version 5.23 Beta (18 January 2010)

New documentation section on customising the new CKEditor3 based HTML editor (more to come soon). See Customising the New Editor.
Build Changes:
- The undocumented feStore class is now deprecated for FileExplorer 5 in all versions of Clarion.
- Changed _ABCLinkMode_=>1 set to 0 in C7.1 build for the LIB compile.
- Fixed a problem in the template that resulted in the compile error: "File Can not be found - PWUTIL.LIB" in Clarion 6.
- Template includes CWSYNCHC.inc in the global includes, for C6 and up only.
- The pwutil.lib file is now included with the installer, and linked at the project level.
- Update Multi-Proj linking.
- Switched to release mode to work around assert bug in Clarion 7.0.
- Modified Assert statements throughout to prevent incorrect firing in Clarion 7.0 as a result of a bug in the Assert() call in 7.0.
Tested and fixed initial document loading using the template "initial document" option.
Tested initial document loading from disk (feEditor.Load) and memory (feEditor.SetHtml) using theEditorReady() embed provided the feEditor class.
Note: It is recommended that you add code after the call to the parent.EditorReady() method to ensure that the control is fully initialised.
Tested CollapseToolbar() when the editor initialises. We recommend adding code after the parent call, which functions as expected.
While calling CollapseToolbar will toggle the toolbar to collapsed when the editor initializes, the toolbar may still "flash" the expanded version before the editor resizes and displays with toolbar contracted. In order to start the editor will the toolbar minimised by default, the feeditor.html file can be edited as follows:

In CKEDITOR.replace function in the file, all the settings are defined, and you can add the toolbarStartupExpanded: false setting (shown below, with the code added in black):customConfig : '', // Ensure no external config file is load. All customisation is done here
extraPlugins: "Open", // Add all custom plugins to this list (comma seperated string)
skin: 'kama', // Set the skin. Can be: black, kama, office2003, v2, or any other skin installed
uiColor: '#DDDDDF',
toolbarStartupExpanded: falseAdd a comma after the last setting, and then add your own settings. You can add as many as you like, they are simply a comma separated list. See Customising the New Editor in the HTML Editor documentation for additional options.

Built and tested in Clarion 5.5 Local and Standalone modes, and tested for regressions.
Built and tested in Clarion 6 Local and Standalone, and tested for regressions.
Built and tested in Clarion 7.0 Local and Standalone modes, tested for regressions.
Built and tested in Clarion 7.1 Local and Standalone modes, tested for regressions.
Tested the new HTML Editor in Legacy.

Version 5.22 Beta (08 January 2010)

Cleaned up documentation on distribution and required files.
Removed the deprecated and undocumented feStorage class. This has been deprecated since FileExplorer 3.
Fixed a bug in the template that was hiding the "initial document" template prompt except when the feEditor was used. This has been corrected and the prompt is now available for all classes except the feEditor. To load a document when the editor loads use the provided EditorReady() method embed and call the Load() method to load from file, or SetHtml() to load from memory.
Fixed a problem with the template linking the incorrect files in Clarion 7.1, causing compile errors in Local (EXE mode). Standalone (DLL) Mode is unaffected.
Fixed a missing LIB file in the C7.1 distribution (not required for prior versions of Clarion).
Cleaned up example documentation.
Removed deprecated sections of the docs that no longer apply.
Fixed Clarion 7.1 compile error relating to the Topspeed driver being required (only the DOS file drive is required, and is included by the template automatically).

Version 5.21 Beta (04 January 2010)

Clarion 7.1 Compatibility release.

Version 5.20 Beta (31 December 2009)

FeEditor

New: New CKEditor. The underlying editor used by FileExplorer has been updated to the latest CKEditor (formerly FCKEditor) version 3. The new editor is a complete replacement for the previous FCKEditor 2 base. It features improved performance, is more compact, is easy to customise and interact with, fully support callbacks and allows all functionality provided by the editor to be called from your application. Upgrade is transparent, however the old editor files should be removed and replace with the new ones.
- Old editor files (remove these):
  - The editor directory, feEditor.html, fckconfig.js, fckeditor.js, feconfig.js, fckpackager.xml, fckstyles.xml, fcktemplates.xml
- New Files:
  - Clarion\3rdparty\examples\FileExplorer\Editor Files\.
    
    These files can either be in the current path for your application, or you can use set the feEditor.editorPath property to the directory that contains them before the call to the feEditor.Init() method initialises the editor.
- Note: This is a Beta release, and the new editor's functionality is being expanded and tested.
- Important: The new editor uses an online spell checking API via spellchecker.com. This functionality may be replaced in future versions.
Changed: Significant performance improvements in the feEditor, including saving, opening and otherwise interacting with the editor.
Fixed: The Legacy (Clarion template chain) Resize code was being generated for the new feEditor object even when it was not enabled.
Added: feEditor.ReplaceInString() method, which allows one or more instances of a sub string to be found and replaced in a passed string.
New: feEditor.EmbedImages(*string html) method. This method allows image references in the HTML passed to optionally be converted to the form used for embedded images in email, and returns a list of the file name for the images used. This method does not alter the contents of the editor, and does not retrieve the HTML from the editor. It can be called completely independantly without requiring an editor control, or the object to be initialised by calling the Init method. Note that the feEditor.EmbedImages() method is still available, and does the same thing, except that it fetches the HTML from the editor, and optionally updates the editor with the new HTML once complete.
New: Updated the EmbedImages documentation to include an example of the new version of the method, as well as to demonstrated loading HTML from a BLOB into a string, embedding the images, and sending the result using NetTalk
New: CallCommand method allows any of the new editor functionality to be called from the object, including printing, formatting etc. All command provided by the editor (including all toolbar commands) are now supported.
Improved cleanup, and added explicit destruction of the JavaScript editor.
The PrintMe method is now supported by the feEditor class to print the contents of the editor.
Note: You cannot call code that uses the editor before the EditorReady() callback method has been called. Use the EditorReady method to execute any code that should run when the editor has finished initialising. This is by far the most frequent problem that people have using the editor.
Change: The "Old MS DHTML Editor" tickbox is no longer ticked by default when selecting the HTML Editing control type on the template options.
Major overhaul of the main Demo example. More coming soon!
Added: GetSelection() method to return the HTML for the current selection (Beta, not tested in this release).
Added: GetData() method, this generic method allows full interaction with the underlying editor by triggering an event, which the editor then responds to, and then fetching any data that the editor returns as a result.
Updated: Update the GetText() method.
Updated: The template no longer provides an "initial document" prompt for the feEditor. Call the Load() method in the provided EditorReady() embed point to load a document when the editor starts. Alternatively call SetHtml() to load the editor from memory rather than from a file on disk.

Other

Fixed: feFile class FileNameFromPath and PathOnly methods.
New (recommended): FeMerge example application. Demonstrates the following techniques:
- Using the new FeEditor class for HTML editing.
- Loading from memory or disk directly after the editor has finished initialising.
- Retreiving the HTML contents from the editor, setting the content of the editor, and dynamically allocating memory for retrieving the contents of the editor.
- Inserting text into existing HTML documents.
- Dynamically populating a list with fields from any table using Who() and What().
- Dynamically locating fields in a table by name, and retrieving the values of field in a table.
- Replacing the inserted place holders with the actual fields values.
- Writing a modified HTML document back to disk as a new file.
- Using the feFile generic file handling class.
- Displaying HTML documents on a new thread using the feBrowser class.
Updated the main Demo application. Cleaned up old example, revamped the feEditor example, renamed the procedures to be more consistent, added a large amount of new functionality to the feEditor, new event handling examples and more.
Example cleanup and improvement

Version 5.11 Beta (24 July 2009)

Fixed: The feEditor.InsertText() method was not working correctly on all systems due to an underlying JavaScript error.
Fixed: Incorrect template version being included in he installer.

Version 5.10 Beta (11 June 2009)

Fixed: The feFile.NameOnly() method was returning the entire path instead of just the name.
Fixed: The feEditor.InsertText() method was failing because of an undefined JavaScript variable.
Added: A new Legacy example for the feEditor class.
Updated: A number of small template changes to optimise code generated for the new editor.
Added: An "Editor Files" directory to the Examples folder that contains all the files required for the new editor (copy these to your applications data directory in order to use the new editor).
Updated: The feEditor documentation.
Added: New commands to the Edit() method to allow the page and text zoom properties to be controlled:
fe:Browser_Zoom:The text zoom value, takes an integer value between 0 (smallest) and 4 (largest) with 2 being the standard size (normal).

fe:Browser_OpticalZoom: Windows Internet Explorer 7 and later. Sets the zoom factor of the browser. Takes an integer value in the range of 10 to 1000 (percent).

Note: When adding the new editor control, you should delete the additional control populated by the template (the path, prompt and lookup buttons). These will be removed from future releases.

Version 5.08 Beta (7 November 2008)

Fixed: Incorrect template shipped with the previous release (incorrect method prototypes).

Version 5.07 Beta (7 November 2008)

Clarion 7 compatible release

Version 5.06 Beta (26 August 2008)

Fixed: The feEditor.Save() method was not working as the wrong feFile.Save method was being called to write the file to disk.
Added: The feEditor.editorPath property, which alows the path to the editor (feEditor.html) to be set. This needs to be set to the path to the feEditor.html file before the call to the Init() method. If this property is not set then the current application path is used. This should be set to an absolute path, it does not support relative paths.
Updated the documentation for the feEditor to include class properties.
Fixed: Compile errors in Legacy template becuase of incorrect prototypes being generated.

Version 5.05 Beta (01 August 2008)

Fixed: The feEditor.EmbedImages() method was not returning a list of embedded images.
Fixed: Potential memory leak in EmbedImages().
Added: Documented the new feFile class , which allows you to load and save files to and from memory rapidly and simply. The documentation covers the feFile class basics, but it is very simple to use:

htmlFile class(feFile)
end
code
if not htmlFile.Load(fileName)
Message('Load', 'Loading the file failed.')
end

! The loaded file is stored in the htmlFile.binData property
! and htmlFile.binDataLen is the size of the buffer allocated

!--- Write the file back to disk
htmlFile.Save(fileName)

Version 5.04 Beta (11 July 2008)

Fixed a typographical error that was preventing feEditor.ExpandToolbar() and feEditor.CollapseToolbar() from working (please ensure that the feEditor.html file is updated in order to apply this fix).
Added a Distribution section to the feEditor documentation.
Fixed: Fixed an error loading WMV files that did not contain DRM information. This is an error with the Windows Media Player OCX control that ships with Windows Media Player 11 and results in a dialog box being displayed a number of times with an error message when loading WMV files. We have implemented a workaround to suppress these error messages. The error is actually erroneous that is caused by any non DRM protected media.

Version 5.03 Beta (13 June 2008)

New feEditor methods:
- Debugging()
- Log()
- ErrorTrap()
- GetHtml()
- GetPageTitle()
- EmbedImages()
- Load()
- Revert()
- SetHtml()
- SetPageTitle()
- IsReady()
- SetFileName()
- SetSkin()
- CollapseToolbar()
- ExpandToolbar()
- EditorReady()
- BeforeEditorLoad()
The documentation incorrectly listed the following feMedia methods as unsupported, whereas support was added in 5.02:
Major documentation update for the feEditor class. Listed all methods, added new methods and expanded all sections of the documentation, including usage of the new editor, differences between the old and new editor, shipping requirements and more.
Added: feEditor: The Revert() method now supports the use of the promptUser property
Added: feEditor: Reload() is now implemented.

Version 5.02 Beta (06 June 2008)

Fixed: feEditor leaking memory becuase the feFile class destructor was not being called
Added: feFile.CleanUp() method to clean up allocated memory
Changed: The Delayed Close has no affect on the feEditor, as it is not needed and can potentially cause problems and innefficiency on close, and if the Close was not done according to the template generated code (with Kill called twice) then this could result in the parent Kill() method not being called and resource not correctly deallocated.
FeMedia2 Added Support for the following methods:
- get_attributeCount ()
- get_duration ()
- get_durationString ()
- get_imageSourceHeight()
- get_imageSourceWidth ()
- get_markerCount()
- get_name ()
- get_sourceURL ()
- getAttributeName ()
- getItemInfo ()
- getItemInfoByAtom ()
- getMarkerName ()
Exposed the IWMPPlayer2 interface and methodsL
- get_stretchToFit() ! Retrieves a value indicating whether video will stretch to fit size of the Windows Media Player control video display.
- get_windowlessVideo ()! Retrieves a value indicating whether the Windows Media Player control renders video in windowless mode.
- put_stretchToFit ! Specifies whether video will stretch to fit the size of the Windows Media Player control video display.
- put_windowlessVideo ! Specifies whether the Windows Media Player control renders video in windowless mode.
Fixed: feMedia: A number of methods that were not working such as put_Mute() and get_Mute()

Version 5.00 Beta (11 April 2008)

This is a brand new major release of FileExplorer and is being released in Beta. There are features that are still a work in progress, and the documentation for the new classes is being worked on, as well as updates the example applications etc. We have been using the new class internally for some time, so in our experience they are robust and work very well. You should test your application with FileExplorer 5 before releasing it.
New feMedia2 class replaces the old feMedia class. The new class automatically uses the new version of the Windows Media Player interfaces if they are available and falls back to the old version. Implements backward compatibility for existing code, although some methods may not work with the new Media Player control because of changes in the underlying Media Player control. The new media player features almost a hundred new methods for interfacing with Windows Media Player and there is still a significant amount of additional functionality that will be added.
Major documentation update and rearrangement
New documentation for the new feMedia and feEditor classes
Moved all documentation towards XHTML and CSS based, without any inline formatting.
New feFile class that provides file loading and saving using the Windows API, as well as providing functions to manage file names and paths. New methods: Load, Save, ErrorTrap, FileNameFromPath, PathOnly.
Completely new HTML Editor (the old editor is still supported, but deprecated). Provides a fast, robust and feature rich editor. A few of the features of the new editor:
- Compatible with all version of Windows, including Windows Vista and Windows Server 2008.
- Requires only Internet Explorer 5.5 or later on the machine, there are no other dependencies.
- Generates HTML with Internet Explorer 5, 6, 7 and Gecko browser (Mozilla / Firefox / Netscape) compatibility
- XHTML 1.0 support (generates clean, standard compliant XHTML code)
- Font formatting: type, size, color, style, bold, italic, etc
- Text formatting: alignment, indentation, bullets list, etc
- CSS (cascading style sheets) support for a better integration with web sites, and cleaner, faster, small code with better consistency
- What You See Really Is What You Get. Pages are rendered by IE as you edit them, so the rendering is very accurate.
- Cut, Paste and Past as Plain Text, Undo and Redo
- Paste from MS Word cleanup with auto detection
- Link creation
- Anchors support
- Image insertion
- Table creation and editing (add, delete rows, etc) - one of the best systems in the market.
- Table cells editing (size, colours, etc)
- Form fields
- Right click context menus support
- Complete toolbar customisation
- Easy menu customization and skins (add your own styles, font-formats, etc ...)
- Skins support.
- Plug-in support.
- Spell checker integration via SpellerPages (additional built-in spell checking options coming soon!)
- Multi-language support, including Right to Left scripting.
- Complete page editing, including visually setting the overall page properties
- Lightweight and fast
- Automatic browser detection and support for IE 5.5 and upwards.
- Load from memory or disk, or URL
- Save to memory or disk
- Full access to the editor and editor data programmatically
- Easily customisable, fully skin-able, and can be modified without requiring a recompile of the application
- Easily customisable toolbars, including runtime customisation and additions (no recompile required).
- Ability to get and set the text or HTML simply by calling a method.
- Much, much more!
- Full access to the DOM of the edited page coming soon!
Important: The new editor requires that you ship the following files with your application (place these in the application or Data directory for your application). All of these files are shipped in the example folders: Clarion\3rdparty\examples\FileExplorer\Demo
- The whole Editor\ folder (Clarion\3rdparty\examples\FileExplorer\Demo\editor\)
- feEditor.html
- fckpackager.xml, fckstyles.xml and fcktemplates.xml
- fckconfig.js, fckeditor.js, feconfig.js

Version 4.03 (17October 2007)

Added support for Clarion 7.
Changed some internal code that was originally added for C7 support but was not needed (and was causing problems with the control continuing to work, send events etc. but no longer refreshing, loading files, resizing and so on).
Added a Multi-DLL example

Version 4.02 (17 October 2007)

Fix a damaged DLL in the installer that was causing a GPF when the main installer was used with Clarion 6 9056 (the 9054-9056 binary installer did have the correct DLL).

Version 4.01 (11 July 2007)

New section in the FeBrowser documentation on using JavaScript and FE to control HTML documentation and utilize the HTML DOM to create dynamic pages and interfaces (using HTML for dynamic forms with your application). A full example application is coming soon.
New example application - there are no longer a separate examples for C55 and C6. All functionality has been merged into a single feabc.app example in the Demo folder. The example has been cleaned up, improved and expanded on (for the example main Html Editing window now has a Source tab as well as the editor and demonstrated reading and writing the HTML data, and syncing the Editor with a Text control displaying the Source).
New "How To" in the feBrowser documentation: How to remove parts of a loaded page before displaying it to the user
New feBrowser.LoadFromStream() method now allows data (such as HTML) to be loaded into the Browser control directly from memory!

Version 4.00 (21 February 2007)

Fixed the FeFlash.GetSWFHeader method deleting the Flash file after retrieving the header information.

Version 3.99 Gold (15 February 2007)

Provide information about installation and support for the HTML Editor control under Windows Vista. See here for more information.
Fixed problems with the C6 demo, where the incorrect file was shipped, resulting in compile errors when OfficeInside was not also installed.
Fixed incorrect icon path in Demo application.
Added feSWFHeader group type and a GetSWFHeader method to retrieve the header information from SWF files. Thanks to Geoff Spillane for providing the header reading code.
New signed installer.
Updates documentation for the Flash class. Added new methods, added a Data Types and Equates section as well as a Properties section, start updating documentation, adding examples, adding descriptions to the method and property listings etc. All documentation will be rewritten in future releases, every method will be fully described along with the parameters, return values, data types, equates and a functional code example.
Compatibility with Office Inside for spell checking (example to follow in the next release)
FE no longer outputs any debug information unless the /fedebugmin or /fedebugmax flag is passed on the command line.

Version 3.98 Gold (10 January 2007)

Fixed the Internet Explorer version function and added support for Internet Explorer 7 and above.
Fixed build problems where web was not updated and the template was reflecting the incorrect version (3.92).

Version 3.97 Gold (06 January 2007)

New "Background Printing" example application and updated documented in the Browser docs on how to do background printing. The example allows a file/URL to be loaded and then printed in the background on a hidden window using a FE Browser control. Once the print is complete the window is closed. The example starts the print procedure on a new thread, although it could also be called without Starting it on a thread.
Updated the section on background printing.
Fixed Registry access functions, add additional error handling, fixed the incorrect error being reported.
New Windows Version function
Fixed Windows version retrieval and added support for new version of Windows (function simply returns the version of Windows without a interpreted name if it is an unknown version).
Fixed registry initialization and fetching. The incorrect key was being checked
Replaced the fe_GetHtmlGraphicsInfo() function with a new function which handles HTML that contains JavaScript and CSS styles, and correctly fetches the image listing, as well as differentiating between local links and links to HTTP addresses (which are not placed in the list).

Version 3.96 Gold (16 November 2006 )

Updated the C6 example (Html Editor not has a Source and Edit tab and they are automatically kept in sync etc.)
Updated the C55 example, improved the layout. The C6 and C55 example need to be merged into a single C55 example that contains all of the functionality.
New the feBrowser.Edit() method that allows a third parameter to be passed for setting filenames etc.
Completely new document for the feBrowser.Edit() method
Add new equates for passing the feBrowser.Edit() method to determine it's behavior. Renamed the second parameter to pAction to reflect it's use.
Update the documentation, improve the documentation on the callback methods to list all callbacks and their use etc.
File Explorer is not compatible with Office Inside objects on the same window and thread. Note that you need to set the 'Activate compatibility with File Explorer' checkbox on the Office Inside local extension when FE is used on the same window as Office Inside. Not changes are need to the manner in which File Explorer is used.

Version 3.95 Gold (30 July 2006 )

First new revision of the documentation (many more changes to come)
Added a properties section for the feMedia class
Add documentation for the MPVersionNumber property that allows newer versions of Windows Media Player to be used
Todo: Compatibility with Office Inside spell checking
Todo: Jspell and Fe example application
Todo: Updated look of example
Todo: Use new version of Windows Media Player in example application (allow switching between old and new).

Version 3.93 Beta: ( 25 April 2006 )

Updated the C6 example application, first revision of a cleaner look a feel and easier to use layouts, as well as an updated HtmlEditor example - there is now a Source tab that displays the source for the FE Html Editor, this can be used to modify the html source code and have the changes reflected in the editor and visa versa.

Version 3.92 Beta: ( 25 April 2006 )

An old file was shipped in the C55 build that could cause a GPF on opening a window with an FE control on it.

Version 3.91 Beta: ( 25 April 2006 )

Fixed regression in lib (introduced in 3.90) - caused a duplicate procedure error on compile

Version 3.90 Beta: ( 25 April 2006 )

Updated the example application, which was missing some of the test HTML, SWF, JPG etc. files for loading into the FE control, as well as ensuring that the example uses the types provided by FE rather than redeclaring the queues, which can cause problems when the type'd queue declaration changes.
Added WinErrorCode( ) and WinError( ) methods. WinErrorCode returns the error code for the last API call on the current thread, WinError converts the error code to an error message when passed the code. These methods exist in all the FE classes.

Version 3.89 Beta: ( 07 April 2006 )

Increased the maximum length of the values that FeBrowser.GetElementQ returns for the DOM objects in the document, the maximum length have been changed from 255 characters to all allowing values up to 2048 characters long. The tag information has been changed from 100 to 256 characters (name, tagname, type, id etc.).

Version 3.88 Beta: ( 24 March 2006 )

Changed the way that the OLE libraries are linked in local mode. This works around a linker problem that occurs when multiple libraries, linked in local mode, link to the same library. This allows compatibility with other third party products such as EasyCom2Inc that use the same libraries. If you get duplicate symbol errors you will need to update both FileExplorer and the other accessories utilising these libraries. Standalone compiles remain unaffected.

Version 3.87 Gold: ( 24 March 2006 )

New installer built with a number of fixes and improvements.
Verified that the DocInnerText and InnerText properties of the HtmlEditor class are working correctly and being populated in C6.
Updated docs, especially the callbacks for the feBrowser class
Added a namespace ('fe') to all API calls for future compatibility and improved compatibility with other third-party products.

Version 3.86 Gold: ( 03 March 2006 )

Fixed issues with the new build system and DLL versions (incorrect DLL version and runtime incompatibilities)

Version 3.85 Gold: ( 17 February 2006 )

Fixed the SetFocus method, it now sets the focus to the actual control rather than to the parent window which the control is placed on.
Fixed crash of FileExplorer HTML viewer with pages that contained flash objects and scripts.
Changed default for FileExplorer HTML Viewer to default to delayed close. If you are having problems with pages crashing when closing and then reopening a web site then please make sure the setting on the FileExplorer Extension "Implement Delayed Close" on the "BrowseHTML" tab is on. This is now the default option, however for existing controls it should be set manually when needed.
Fixed loading of URLS longer than 500 characters (the maximum length is now the IE maximum - 2088 characters).

Versions 3.84 Gold: ( 16 November 2005 )

First build compiled with Clarion 6.2.9048 (and Clarion 6.1.9031)
Several minor internal improvements.

Versions 3.83 Beta: ( 11 October 2005 )

Fixed an issue in the feBrowser.Load method.

Versions 3.82 Beta: ( 5 October 2005 )

Tidied up the fe.inc file.
Fixed an issue with FE not reporting the installed version of Acrobat Reader correctly (just a string update, does not affect any functionality)
Added a new checkbox to the feBrowser object's template properties, labeled 'Implement Delayed Close' - work in progress.

Versions 3.80 Beta: ( 15 July 2005 )

Deleted the 'KillCalled' property from the feBrowser class, this property was already defined in the feCOM class which the feBrowser class is derived from.
New property: feBrowser.GetInfo_SelectedHtml; feBrowser.GetInfo_SelectedOuterHtml
New: FeBrowser.GetInfo, and feHtmlEditor.GetInfo methods both now support new options: fe:SelectedHtml; fe:SelectedOuterHtml
Updated: Added new items into the feabc.app example application's feBrowser_MainExample procedure menu to show off these new features (above).
Change: feBrowser and feHtmlEditor classes are both now derived from a new class called 'FeGenericHTML'
New: feHtmlEditor.Update now supports 'SelectedOuterHTML' as the first parameter. Not yet documented, still testing.
Fixed: feBrowser.SetValueByID was not working correctly.
Change: feBrowser.SetValueByID improved (internally), and a third parameter called pHTML has been added. Not yet documented, still testing.
Change: feBrowser.GetValueByID improved (internally), and a second parameter called pHTML has been added. Not yet documented, still testing.
Numerous other internal changes. Not yet documented. Currently being tested. Will document in the next release.

Versions 3.79 Beta: ( 3 June 2005 )

Fixed a compile error in the festorage.app example (tpl).
Several internal changes / improvements, mostly in the feMedia class, not yet documented.
The DOM code now supports "<button>" elements.
First build compiled with Clarion 6.1 9034, and Clarion 6.2.

Versions 3.78 Beta: ( 11 April 2005 )

Started adding support for Media Player 9 and 10, still busy with this, simply set feMedia.MPVersionNumber = 10 before calling Init if you want to try this code out. Still defaults to using Media Player 6.4. Will document this and add it to the template (and make it default to 10 or the latest installed version) as soon as the following issues have been resolved in the feMedia class:
- Update ('AllowChangeDisplaySize') - not yet working
- Update ('medshowinfowindow') - not yet working
- Update ('medshowtoolbar') - not yet working
- Update ('medshowslidebar') - not yet working
- Update ('medshowgotobar') - not yet working
- Update ('medenableslidebar') - not yet working
- Update ('medenabletoolbar') - not yet working
- Update ('medshowpositioncontrols') - not yet working
- Update ('medautorewind') - not yet working
- Update ('medautoresize') - not yet working
- Update ('medzoom') - not yet working
- Update ('medstartposition') - not yet working
- Update ('medendposition') - not yet working
- GetInfo method (all)
- Callback Events
Added support for Easy ResizeAndSplit to File Explorer. Tested with Easy ResizeAndSplit 2.07
New method: feBrowser.SelectElementByID
New method: feBrowser.SelectElementByName
Improved: My DOM code now returns the HREF property of LINK objects in the ElementValue field of the queue that you get back. See my feabc.app example's "Accessing the DOM" procedure. This means that you can now easily get a list of all the URLs (hyperlinks) in a loaded html document.
Improved: My DOM code (see above) also now includes "All-FE" and "All-IE" under the example's "Tag to search for" drop list. The "All-FE" option is the old "All" option, which returns all objects found (and supported) by FileExplorer. The new "All-IE" option returns all objects directly from Internet Explorer - some of which may not be supported by File Explorer. If you see anything in the IE list that you need (that is not in the FE list) let us know.

Versions 3.77 Gold: ( 24 March 2005 )

New template symbol called %FEBuild - other templates can use this to check the FE version number
FeHtmlEditor.Update method now supports ShowDetails, and ShowBorders.
Deprecated the feHtmlEditor_Update procedure in the feabc.app example. Moving this code into the feHtmlEditor_MainExample procedure. Going to be revamping the main example for the next release.
Numerous internal improvements (nothing risky, all well tested, just optimized code in some areas and fixed an possible issue when closing down some of the objects).

Versions 3.76 Beta: ( 7 March 2005 )

Minor template improvement (Do not generate code template option was still generating some recently added code)
Improved the feabc.app and feleg.app examples (changed the toolbar icons to 32X32 - thanks Sean! Also changed the legacy frame toolbar and About screen to look like the abc example's, and improved the look of most of the windows in the legacy app)
Fixed an issue File Explorer had pertaining to being hosted inside GROUP controls! Rewrote the code used to manage how FE controls deal with being on Tabs, in Groups, and so on, changes included:
- Deprecated several template generated routines: feWatchingZOrdering, feWatchingParentPropHideStatus, and feFixLeakingThroughTabsOnWindowOpen
- Several internal changes
Cleaned up a lot of code in the dll

Versions 3.75 Beta: ( 28 Jan 2005 )

New: Now supports Acrobat Reader version 7
Improved: Minor template improvement
Improved: New method (all classes) called "_WindowClosing". Work in progress, not yet documented. Is implemented by the templates though.

Versions 3.74 Beta: ( 24 Jan 2005 )

Fixed: Compiler warning 'Field label is duplicated, first used' under Clarion 6.1 build 9031 (HTMLURL Line840, HTML2SOURCE Line1047)
Changed: Internal property called Debugging changed to DebugLevel (applies to all classes)
FeDUN class completely removed
Improved: Major internal (dll) change (architecturally)
Improved: Template improved
Changed max length of URLs from 255 to 1024 (fe:URLStringSize)
New: Two new events (virtual methods) in the feBrowser class: EventClick, and EventDblClick. These required a major internal change in File Explorer, so please test this release before releasing to customers - it seems to work fine from what we've seen. This is currently considered work in progress, and will not be enabled unless you tick "Implement More Callback Events" in the template properties for the feBrowser control. As soon as we're sure this is stable we will incorporate it into the "normal" events, and will remove this template option.

Versions 3.73 Beta: ( 20 Dec 2004 )

First build compiled with Clarion 6.1 Build 9031

Versions 3.72 Beta: ( 16 Dec 2004 )

New: Several internal changes for better integration with CapeSoft Office Inside (more to follow in subsequent builds)
Improved: New internal method called feMedia.DbgMsg (internal improvement)
Improved: Template code pertaining to feMedia object, especially when another FE object coexists on the same window
First build compiled with Clarion 6.1 Build 9030

Versions 3.71 Gold: ( 29 Nov 2004 )

Fix: Media Viewer template was not implementing AllowZoomChange, Mute, RepeatTimes and StartPosition properties
Fix: Template was causing compile errors on the (now disabled) DUN code

Versions 3.70 Gold: ( 22 Nov 2004 )

First Gold release since 12 Dec 2002! Have rewritten virtually the whole of File Explorer twice since then.. We now don't use the Clarion OLE control / code at all, anywhere in File Explorer. There is nothing that was in the last Gold release that is not working as well or considerably better in this release.
The template no longer supports using the Clarion OLE control, you must change all Clarion OLE controls to Panels, see the section titled Considerations if upgrading from a version earlier than 3.70 for more info (look for Compile Error 2). Clarion's OCX.CLW file is no longer linked in. You no longer need to ship C55OLEX.DLL with your apps.

Versions 3.60 Beta: ( 15 Nov 2004 )

New: feBrowser entry control now alerts for CtrlEnter, like Internet Explorer, so you can type in google (CtrlEnter), or www.google.com (Enter) (New undocumented method built for this called _FormValidURL. Template changed to implement this automatically).
New: New property for all objects called EntryControl (used internally by templates)
Deprecated: The CallFe_LoadMethod template had a setting called Viewer Control, this is no longer necessary
Deprecated Procedures In feabc.app example:
- Advanced_feBrowser_CodeTemplate (Now included in feBrowser_MainExample)
- Advanced_feBrowser_StatusBar (Now included in feBrowser_MainExample)
- Advanced_feBrowser_Tabbing (Moved to the BenchMark example application)
- Advanced_feBrowser_Tabs (Moved to the BenchMark example application)
- Advanced_feBrowser_TwoViewers (Moved to the BenchMark example application)
- Advanced_feBrowser_ThreeLaunchesExample (Moved to the BenchMark example application)
- Advanced_feBrowser_TwoWinsOneThread_Parent (Moved to the BenchMark example application)
- Advanced_feBrowser_TwoWinsOneThread_Child (Moved to the BenchMark example application)
- Advanced_feBrowser_GetInfo (Now included in feBrowser_MainExample)
- Advanced_feHtmlEditor_CodeTemplates (Now included in feHtmlEditor_MainExample)
- Advanced_feHtmlEditor_GetInfo (Now included in feHtmlEditor_MainExample)
Improved: Numerous parts of the dll code optimized, cleaned up, etc.
Improved: The CallFe_LoadMethod code template now updates the parent object's entry control if present
Improved: CallFe_EditMethod code template revisited

Versions 3.52 Beta: ( Released 3 Nov 2004 )

Improved: Major template cleanup
Improved: Several methods improved internally, including:
- feMedia.Load
- feMedia.Init
- feMedia.Update
- fePDF.Load
- feFlash.Load
- feFlash.Update
Improved: feMedia properties (e.g. self.MedAllowZoomChange, self.MedMute) now retain their values when loading new media files into the Viewer Control
Improved: fePDF properties (e.g. self.PDFZoom) now retain their values when loading new documents into the Viewer Control
Improved: feFlash properties (e.g. self.FlashLoop) now retain their values when loading new documents into the Viewer Control
Deprecated Properties (have not actually been used in over a year): feMaster.fe_Height, feMaster.fe_Width, feMaster.fe_TreatUnknownsAs

Versions 3.51 Beta: ( Released 22 Oct 2004 )

Changed the template generated code for the fePDF object. ( Would love to redo this code and lose all the routines that get generated.. ) Now all initialization properties are only set after the call to fePDF.Init. Properties like PDFZoom used to have to be set each time we called the Load method - this is no longer necessary. Also (due to demand), I now let you set PDFZoom to any value you like (no longer validate it to between 0 and 100).
Started cleaning up the template

Versions 3.50 Beta: ( Released 4 Oct 2004 )

Bug Fix: An internal method was not always decrementing object counters correctly under Clarion 6.1, which could have caused some objects to GPF the second time they were initialized. (Bug in GetElementQ) ( ElementID is currently not being returned )
Internal Improvement: Event Handlers are now disabled earlier in the "Kill" logic for all classes
Internal Improvement: Updating fields in feBrowser DOM code is now much more efficient
Internal Improvement: fe_GetCStringFromBstr function improved
New property for the feBrowser class called DoNotLoadAboutBlankInInit ( Not yet documented )
Internal Improvement: IIDisp objects no longer self-Release under the current C61 build ( must update other products accordingly )
fe_GetIEVersionInfo now takes an optional parameter
feDispose is now obsolete. The template no longer generates calls to this function. This fixes an issue under C6.1 causing GPFs as apps were closing down.
Need to check all method prototypes in the tpl to make sure they're right (see HtmlEditor.Load)
Several new virtual methods have been added to the template to make processing feBrowser events easier:
- EventNavigateComplete2
- EventDocumentComplete
- EventOnQuit
- EventOnVisible
- EventOnToolBar
- EventOnMenuBar
- EventOnStatusBar
- EventOnFullScreen
- EventOnTheaterMode
- EventWindowSetResizable
- EventWindowSetLeft
- EventWindowSetTop
- EventWindowSetWidth
- EventWindowSetHeight
- EventWindowClosing
- EventClientToHostWindow
- EventSetSecureLockIcon
- EventFileDownload
- EventNavigateError
- EventPrintTemplateInstantiation
- EventPrintTemplateTeardown
- EventUpdatePageStatus
- EventPrivacyImpactedStateChange

Versions 3.49 Beta: ( Released 27 August 2004 )

First build compiled with Clarion 6.1 Build 9027

Versions 3.48 Beta: ( Released 16 August 2004 )

The feMedia.AutoSize method became obsolete several releases ago (replaced with the feMedia.Resize method). There was still a reference to the old method in the templates which has now been removed. There was also an embed point before and after a call to the feMedia.Wait method which has been removed, as because we are now using COM (not Clarion OLE) there is no need to use the Wait method. Please check your code for any orphaned embeds here.

Versions 3.47 Beta: ( Released 12 August 2004 )

Several properties are now obsolete: fe_CurrentControl (used in most objects), DisableWait (used in most objects)
feMedia events are now passing in the correct parameters
Documented the fe_MCIPlay and fe_MCIStop functions
First build compiled using Clarion 6.1 Build 9025

Versions 3.46 Beta: ( Released 23 July 2004 )

First build compiled with Clarion 6.1 Gold (Build 9024)

Versions 3.45 Beta: ( Released 16 July 2004 )

feBrowser EventBeforeNavigate2, EventNewWindow2 and EventCommandStateChange methods now return longs. Made several internal improvements to the way File Explorer handles callback events.
fe_OnlineStatus and fe_OnlineStatusConnectionName functions improved.
Removed the obsolete FeViewer class.
Improved several examples, including Advanced_feBrowser_AdvancedCallbacks.

Versions 3.44 Beta: ( Released 14 July 2004 )

Template fix - feHtmlEditor, feFlash and fePDF might have been leaking through tabs. Thanks to Trevor Cocks for finding this bug.
Internal fixes in the FeBrowser BeforeNavigate2 and NewWindow2 events.
First build compiled with C6.1 RC6

Versions 3.43 Beta: ( Released 28 June 2004 )

New FAQs : 2.12
Updated Docs : feBrowser.Load
First build tested with Clarion 6.1 RC4

Versions 3.42 Beta: ( Released 10 June 2004 )

Fixed a bug causing a GPF as your exe closed when compiled with Clarion 6.1.

Versions 3.41 Beta: ( Released 8 June 2004 )

New method - feMedia:EventCallback (supports callback event from the Windows MediaPlayer ocx).
First build to support Clarion 6.1 CR2

Versions 3.40 Beta: ( Released 4 June 2004 )

Fixed: feMedia object was not always resizing correctly
Fixed: feFlash object was not resizing at all in the last release
The feMedia::GetInfo method now takes an optional parameter
Updated the feoi.app example (Office Inside / File Explorer in same app)
First build to support Clarion 6.1 CR1

Versions 3.39 Beta: ( Released 28 May 2004 )

Complete rewrite of the fePDF object!
Big news : Templates now implement a Panel control rather than the Clarion OLE control. File Explorer no longer uses the Clarion OLE control for ANYTHING.
FeFlash::EventCallback method improved. Please see FAQ 1.11 for more info.
New methods: FeFlash::SetVariable, FeFlash::GetVariable
Changed FePDF::Init method's parameters
Tidied up documentation and templates

Versions 3.38 Beta: ( Released 26 May 2004 )

FeBrower::Update improved
FeFlash - major overhaul.. Now using Plugware classes rather than Clarion OLE, and Callback Events are now working!
- Init method now takes different parameters - changed from (<long CurrentControl>) to (long ParentControl, <string LoadPath>, long Handle1=0, long Handle2=0, byte SkipCallbacks=false).
- New methods - Kill, EventCallback
- Template now has two new checkboxes which you need to manually set - "Auto-Resize control" and "Implement callback events"
- Improved Flash examples in the feabc.app example app.
No longer supporting the Background Media Load Button control template, please use the CallFe MadiaAPIMethod code template instead. Major overhaul of the CallFe_MediaAPIMethod code template, much cleaner now.
Changed the install exe to backup your old examples before replacing them with new ones.

Versions 3.0 Beta 1 to 3.37 Beta: ( Last released 19 May 2004 )

All the improvements / changes made during the 2.9 releases.
Rewrote the feBrowser class! Improvements / changes include:
- Even faster, even more robust..
- Several methods had size restrictions on their parameters. No longer! Methods include feBrowser:: Load, ...
- You can now have multiple objects (Viewer controls) on the same window, and scroll large files safely (were some issues here in the past).
- The issue reported with browsing Disney.com has been fixed.
- The FeBrowser::Refresh method now takes an optional parameter, allowing you to specify the "level" of refreshing you want done.
- The FeBrowser::Edit method now takes a second (optional) parameter.
- New property (used internally, currently undocumented) called LastLoadedDoc, which will replace LastLoadedDocument and CurrentPath for the Webbrowser class. No size restrictions.
- feBrowser::Load; from (long ParentControl, <string LoadPath>, <long Handle1>, <long Handle2>, <byte SkipCallbacks>) to (long ParentControl, <string LoadPath>, long Handle1=0, long Handle2=0, byte SkipCallbacks=false). Improved ability to pass (new) optional parameters, and the way this code works.
- FeBrowser::GetInfo method(s) now take a parameter allowing you to specify a FrameNumber. ( See the Advanced_feBrowser_GetInfo example procedure in feabc.app, which now shows how to use GetInfo with frames ). Added new properties (&cstring's) which GetInfo now updates and returns pointers to, better way of doing this as there are now no size limitations. All properties auto-clean in the Kill method, note these are read-only properties - see the fedemo.app (abc) - Advanced_feBrowser_GetInfo procedure for implementation.
- FeBrowser::Resize method now takes longs as parameters, not shorts.
- FeBrowser::GetElementQ method parameters changed from ( < *cstring TagName >, fe:QParam_Type QParm ) to ( <string TagName>, fe:QParam_Type QParm, long FrameNumber=0 ). This method now supports frames.
- FeBrowser::SetValueByName method parameters changed from ( string ElementName, string ElementValue, byte ElementType=0 ) to ( string ElementName, string ElementValue, long FrameNumber=0 ). ElementType was never documented / implemented, so this will not affect any existing code. This method now supports frames.
- FeBrowser::GetValueByName method parameters changed from ( string ElementName ) to ( string ElementName, long FrameNumber=0 ). This method now supports frames.
- FeBrowser::SubmitForm method parameters changed from ( <string FormName> ) to ( <string FormName>, long FrameNumber=0 ). This method now supports frames.
- Updated the Advanced_feBrowser_DOM example (feabc.app) to demonstrate using the improved GetElementQ, SetValueByName, GetValueByName and SubmitForm methods (with frame support).
- SetValueByName now supports dealing with duplicated field names (new 6th parameter).
- FeBrowser::Load changed - now if you pass CurrentPath as '' (empty string) it loads "about:blank", rather than just ignoring you which is what it did in the past..
- The feBrowser::Update method now supports setting the "SilentMode" parameter.
- The feBrowser::EventCallback method now returns *cstrings, not *strings. This was never documented prior to this version so it won't affect anyone.
- Can now read / set html CheckBoxes from your code
- feBrowser::GetHtmlGraphicsInfo method improved (internal fixes)
- New methods:
  - FeBrowser::SetFocus - used to restore focus to the Viewer control Window.
  - FeBrowser::ClickByName - which enables you to click buttons in html pages! Cool...
  - FeBrowser::Home
  - FeBrowser::SearchPage
  - FeBrowser::NumberOfFrames
  - FeBrowser::NameOfFrame
  - FeBrowser::HideControl
  - FeBrowser::UnhideControl
  - FeBrowser.ClickByRecordNumber
Rewrote the feHtmlEditor class! Improvements / changes include:
- No longer using any "Clarion OLE".. All pure early-bound COM. Many many many advantages to speed, stability, and new features we can now add.
- Changed the Init method's parameters from (<long CurrentControl>) to (long ParentControl, <string LoadPath>, long Handle1=0, long Handle2=0, byte SkipCallbacks=false). Updated the templates to take this into account.
- Changed the Load method's parameters from (string CurrentPath, <long CurrentControl>, <byte LoadFromVar>) to (string CurrentPath, long CurrentControl=0, byte LoadFromVar=false). Updated the templates to take this into account.
- "Save" method improved.
- ThisViewer1.Load ('') now has the same effect as ThisViewer1.NewDocument(). In the past ThisViewer1.Load ('') did nothing.
- feHtmlEditor::GetHtmlGraphicsInfo method improved (internal fixes)
- New methods:
  - FeHtmlEditor::SetFocus - sets the focus to the window that the FE control is on
  - FeHtmlEditor::HideControl
  - FeHtmlEditor::UnhideControl
  - FeHtmlEditor::InsertTable
  - FeHtmlEditor.TableLayoutWindow
Rewrote the FeMedia class! Improvements / changes include:
- Init method used to take a single optional parameter. Method now takes several parameters. Template code updated, but your own source code will need to be changed.
- Several methods now return an optional byte, including: Play, Pause, Stop, Load, Init
Methods which now return an (optional) byte, indicating success / failure:
- FeBrowser::Back, FeBrowser:Forward, FeBrowser::Refresh, FeBrowser::Stop, FeBrowser::Edit, FeBrowser::PrintMe, FeBrowser::Init, FeBrowser::Kill, FeBrowser::Load
- FeHtmlEditor::Load, FeHtmlEditor::Edit, FeHtmlEditor::NewDocument, FeHtmlEditor::PrintMe
New Functions:
- fe_GetRegValue (string ParentFolder, string NameOfKey, string NameOfValue),string
- fe_GetOSVersionInfo ( ),string
- fe_DebugString (string)
New examples:
- feabc.app: Advanced_FeHtmlEditor_GetInfo
- feoi.app: Showing how to integrate File Explorer with CapeSoft Office Inside
Removed the following methods:
- Deleted an old (undocumented) form of the FeBrowser::Edit method, which took a string and a long as the two parameters... Don't expect any problems from this deletion.
- Deleted an undocumented method called FeBrowser::_LoopThruElementsByTagName, and an undocumented method called FeBrowser::OleControlSite_Invoke.
Removed the following properties:
- feBrowser.UseLateBinding, feBrowser.DontInitializeHtml1, feBrowser.NavigateMethod
Changes to the templates:
- Viewer Control - Html Editor options - new option called "Auto-Resize control", enabled by default.
Fixed some issued with compiling in local mode.
FeMediaAPI::Play method now supports long file names.
Fixed an issue in the (undocumented) FeStorage class, and added a section for this class (and this issue) to the FAQ's.
Worked on C6 compatibility
fe_ShellExecute function improved
New method: feMedia::EventCallback (callbacks now working for Media Player object)
Updated the Media Player template and examples where the new EventCallback method is now working
New method: feHtmlEditor::EventCallback (callbacks now working for Html Editing object)
Updated the Html Editor template and examples where the new EventCallback method is now working
Improved feHtmlEditor::GetInfo (now supports self.ObjType again)
Rewrote the feHtmlEditor::KeyPressed method, now working again
Commented obsolete template code, including:
All references to OCXRegisterEventProc, OCXRegisterPropChange, and OCXRegisterPropEdit have been commented
Local variables "feLastEvent" and "feLastKeypress" are now obsolete
No longer including the "OCXEVENT.CLW" file
OcxCallbackDeclarations code no longer used / needed
Any code which you embedded into the "Event Handler Callback" embed points will now be orphaned. Please move this code to the new "EventCallback" method, or email us if you need help doing this.
The fe_UnloadCOM function (internal) is now obsolete, the internal _ThreadQ is also now obsolete, as is the private glo_UsingOldClasses variable
The feInit function is now private (was once used by the Global Extension template, no longer necessary)
Expanded the FeHtmlEditor::Edit method to support Tables
FeBrowser "DOM" code now supports IMG tags also
Changed the data type "fe:QParam_Type" in order to return more data via the feBrowser::GetElementQ method (this is the only method that uses this data type), you might need to change your code accordingly if you are using the feBrowser::GetElementQ method
Improved / expanded the fe_OnlineStatus function, and added a new function called fe_OnlineStatusConnectionName
Fixed an issue in the DOM code (GetElementQ, SetValueByName etc) which caused GPFs if dealing with very large webpages. Several other internal improvements here. (Ver 3.26)
Internal improvements to the feBrowser, feHtmlEditor and feMedia "Init" methods.
Fixed a possible problem with the way the feBrowser object was closing down it's callback-event handler
When using the Viewer Control to browse html pages (feBrowser), the FileDialog dialog window used to select which file to view now shows the following (note, methods such as GetInfo also work with mht, xml and eml files!) :
- "HTML Files" - *.htm, *.html, *.mht
- "Text Files" - *.txt
- "Image Files" - gif, jpeg, png, art, au, aiff, and xbm
- "XML Files" - *.xml
- "EML Files"
API calls to CreateCompatibleDC were failing in apps using FE - Fixed
The feBrowser::ClickByRecordNumber method should now also support "Input" element types
New function called fe_SetFocus. Not yet documented or supported.
Fixed issue with DOM code where element collections contain more than 127 elements (handled by the dll, no changes needed to your code)
Changed the FeBrowser::EventCallback method parameters - This will break your current code, please see the docs for how to change your code
New approach and new methods for handling callback events for the FeBrowser object, see the docs for more info ( 32 new methods to handle IE events )
The DOM methods SetValueByName, SetValueByID etc now cause the "OnChange" and "OnBlur" events to fire in the html container when you set the value in an html list-control (SelectElement) or input element from your code! This means that if the html calls a function (e.g. javascript / vbscript) when the user chooses something in a droplist or enters some text into a field, then that function will be called when your code changes the droplist selection or input field also! This is all done automatically inside the dll, so you don't need to change any existing code. Real life example: I had a page with two droplists. The second list got populated with options based on what you picked in the first list - done via a JavaScript function fired on the OnBlur event of the first list. Using FE to select something in the first list will now trigger the script function to fire, which fills the second list, which you can then select from using FE as per normal.
Bug Fix : TextArea elements were not being returned in the Element Queue if you selected "all elements"
New method for feBrowser, feHtmlEditor, feMedia - SetFocus
feHtmlEditor::Edit method now supports fe:HtmlEditor_Outdent parameter
Documentation improved (broken into several smaller documents)
Seem to have fixed the problems with using FileExplorer and OfficeInside in the same apps (standalone mode only, local mode still not working)
Internal improvements to the FeMediaAPI.Play and FeMediaAPI.Stop methods
New functions: fe_MCIPlay and fe_MCIStop
Some Win 98 first edition issues.. - think they're fixed in Beta 2
Changing focus between windows hosting multiple WebBrowsers all implementing Event Handlers croaks the app.. - fixed in Beta 2
FeBrowser::Update method has been broken - fixed in Beta 4
Html Browser and Html Editor controls show "through" tabs - fixed
FeMedia object wasn't working under Win XP in beta 1 and beta 2, fixed in Beta 3
HtmlBrowser and HtmlEditor had an issue with legacy resize implementation, fixed in Beta 3
feBrowser::GetElementQ partly broken in Beta 1 - fixed in Beta 4
Submitting forms broken - fixed in Beta 4
Saving html from the feHtmlEditor control to a variable broken in beta 4 - fixed in Beta 5
FeBrowser event callbacks are broken. -fixed in 3.44
Callbacks broken for Media object ( see feabc.app "Advanced_Video_Callbacks" ) - fixed in Beta 17
Callbacks broken for HtmlEditor object ( see feabc.app "Advanced_feHtmlEditor_Callbacks", and "Advanced_feHtmlEditor_TabAndRightClick" ) - fixed in Beta 17
Finish the remaining FeHtmlEditor methods not yet using the new engine:
GetInfo (just a few items not yet done, almost all were never documented) - fixed in Beta 17
KeyPressed - fixed in Beta 17
Seems to be an issue with having my Viewer control inside a (boxed) group, see the feabc app's "Advanced_feBrowser_Tabs" procedure. For now you can temporarily work around this issue by not having Viewer controls inside (boxed) groups. - fixed in Beta 19
Issue with the feBrowser object "leaking" through tabs as the window opens - fixed in Beta 19
Issue with the feHtmlEditor object "leaking" through tabs as the window opens - fixed in Beta 19, requires some code
Support for FE / Office Inside co-existing in same apps - seems to be fixed in 3.38 Beta
Adobe Acrobat 6 support - needs to be tested - no known issues by 3.44
feMedia events not passing in correct parameters - done in version 3.47
Filling in fields contained in frames - done
Submitting forms contained in frames - done
FeHtmlEditor docs need to be updated - mostly done
FeBrowser has been reported to "show through" tabs in legacy apps - partly fixed in 3.11
Ability to "push" buttons via code (feBrowser) - done
Revisit and document the SilentMode property - done
Setting radio buttons from code using feBrowser - done
Flash - control what happens when Flash buttons are pressed - done
Flash - Callbacks - done

Version 2.9X : ( Several unofficial releases )

First version ever where we've changed some things making this version non backward-compatible. We have added a section to the docs to step you through how to upgrade your apps to use this version, click here for details. Changes outlined below.
- Several local / global variables are now no longer used - moved to properties.
- The "Path Variable" option on the Viewer Control templates is now disabled / obsolete.
- The "Use old classes" option on the Global Extension template is now disabled / obsolete.
- Changed the way we load initial documents for each Viewer control, code moved to a procedure called "feLoadInitialDocument_ObjectName", embed points added so you can customize this. ( Also: Some objects were loading the initial document from ThisWindow::Init, other from the Window Open event, now all objects use the window open event. )
- Moved the code that triggers an event:accepted on the File Explorer entry control (Viewer template) from ThisWindow::TakeFieldEvent, to a new procedure called "feWindowTakeFieldEvent_fePathControl_EventAlertKey_ObjectName", which is called from TakeFieldEvent. Embed points provided.
- Moved code out of ThisWindow::TakeEvent into a new virtual method called TakeEvent.
- Moved code from the TakeEvent logic into a routine called "feWatchingParentPropHideStatus_ObjectName". Embed points preserved.
Various improvements, fixes etc, including:
- Fixed a problem with the feMedia (Video) control's event:alertkey code.
- FAQ's
- Docs (including Summary of callback events)
- Examples ( including in feabc.app: new Frames examples; new callback example for feMedia and feHtmlEditor, new example showing how to load from a listbox )
- Loading initial documents for feMedia objects (template settings) redone.
- Changed the equates for the feBrowser events (old ones still supported but no longer documented)
- Added equates for the feMedia callback events
- Added equates for the feHtmlEditor callback events
The feBrowser::Load method now takes additional parameters, the only (additional) one working at this stage is one to specify a TargetFrameName.
Removed several options from the template settings.
New method: FeMedia::TranslateEventID (similar to FeBrowser::TranslateEventID)
New function called "fe_StartIE". Replaces the feBrowser::StartIE method which is no longer documented.
Added some code to the Advanced_feBrowser_DOM example, courtesy of Carl Barnes.
New procedure in the feabc.app example, called "Advanced_feFlash_HelpAbout".
Eliminating variable size restrictions. So far have done the feBrowser Navigate method. More to come.

Version 2.5e : ( Released 20 Dec 2002 )

The FeBrowser::EventCallback method now takes 7 omit-able parameters, also improved the methods functionality.
Updated the "Advanced_feBrowser_SimpleCallbacks" procedure in feabc.app to demonstrate FeBrowser::EventCallback's new functionality.
Worked on documentation / example applications.

Version 2.5d : ( Released 12 Dec 2002 )

The self.Debugging property which was being set by the global extension template is now set by passing a parameter to the exe, in the form of "/debug0", "/debug1" or "/debug2".
Tidied up the documentation and examples. Concentrated mainly on FeBrowser and FeHtmlEditor.
Added three new buttons to the Html Editing buttons controls, to "Select All", "Undo" and "Redo".
The ClassVersion method has been replaced by a new function called fe_ClassVersion. The old method still works but is now undocumented.
The OnlineStatus method has been replaced by a new function called fe_OnlineStatus. The old method still works but is now undocumented.
New concept ( thanks to Charles Edmonds <g> ); there is now a subfolder in your C55\3rdParty\Docs\FileExplorer folder called "misc". I'll be adding useful pages to that folder from now on. Any suggestions welcome.
Renamed most of the properties in the FeBrowser and FeHtmlEditor classes. Have left the old properties in tact, still support them etc. so your code won't break. Busy changing all docs and examples to use the new, correct property names.
Templates no longer call the feInit function.
The feBrowser::Kill method now takes a parameter: Kill(byte level=0)
The FeHtmlEditor::Edit method now supports the following (additional) equates:
- fe:HtmlEditor_SelectAll
- fe:HtmlEditor_Undo
- fe:HtmlEditor_Redo
Improved the CallFe_EditMethod template
Added equates for the feBrowser::Edit method, changed templates accordingly
The following (additional) feBrowser events are now supported in the library:
- NavigateError
- PrintTemplateInstantiation
- PrintTemplateTearDown
- UpdatePageStatus
- PrivacyImpactedStateChange
The following feBrowser events are now documented and use these equates:
- fe:WINDOWSETRESIZABLE
- fe:WINDOWSETLEFT
- fe:WINDOWSETTOP
- fe:WINDOWSETWIDTH
- fe:WINDOWSETHEIGHT
- fe:WINDOWCLOSING
- fe:CLIENTTOHOSTWINDOW
- fe:SETSECURELOCKICON
- fe:FILEDOWNLOAD
- fe:NAVIGATEERROR
- fe:PRINTTEMPLATEINSTANTIATION
- fe:PRINTTEMPLATETEARDOWN
- fe:UPDATEPAGESTATUS
- fe:PRIVACYIMPACTEDSTATECHANGE
The FeBrowser::EventCallback method now takes more parameters (omit-able). This method is being worked on and should be more useful in the next release.
Expanded the (undocumented / internal) Debugging method

Version 2.5c : ( 8 Nov 2002 ) ( 43rd official release of File Explorer, exactly 2 years since beta 1 )

Fixed a problem / incompatibility between FE and IE6. The problem would have resulted in an error message to the effect of "There was a version error trying to launch the PDF control, version error: 6.0.2600.0000" when trying to load PDF files. The problem only exists when you set the templates to "Use the latest version" of Adobe Acrobat. If you have set the templates to specifically load Adobe 4 or Adobe 5 you would not experience this problem.
Improved / enhanced various methods, including:
- Improved the FeMaster::GetRegValue method - Now supports DWORD data type
- Improved FeMaster::OcxVersion method ( enhanced PDF version info support)
- Improved FePDF::Load method - more robust
- Several improvements to the FePDF class, and updated the documentation
Changed the position of the feDispose() call (template change).
The feBrowser::GetHtmlGraphicsInfo and feHtmlEditor::GetHtmlGraphicsInfo methods now (alternatively) accept a string as the passed parameter.
The fePDF::Load method now optionally returns a byte, indicating whether the method passed / failed. Will expand this concept and change the other objects and document this in the next release.
Updated the fenet.app (File Explorer / NetTalk) example.
Updated the Advanced_fePDF_VariousControls procedure in the fe_abc.app(demo).
Added a section to these docs with the URLs to download the latest components.

CapeSoft File Explorer Documentation

Start Here!

What's new in FileExplorer 5

License& Copyright

Introduction

Product History

Features

Support

Microsoft Windows Vista and Windows Server 2008 Compatibility

System Requirements

Installing File Explorer

Adding a File Explorer Control to your Application

What you need to ship

When using the feEditor class

Complimentary Products

Acknowledgements

The Templates

Dll Functions

fe_ClassVersion

fe_DebugString

fe_GetHtmlGraphicsInfo

fe_GetIEVersionInfo

fe_GetOSVersionInfo

fe_GetRegValue

fe_MCIPlay

fe_MCIStop

fe_OnlineStatus

fe_OnlineStatusConnectionName

fe_ShellExecute

fe_StartIE

feDispose

Support for Adobe Reader 11.0.7

Useful References

Tips & FAQ

General / Product FAQ's

FeBrowser FAQ's

FeEditor FAQ's

FePDF FAQ's

FeMedia FAQ's

NetTalk / FileExplorer FAQ's

The undocumented feStorage Class FAQ's

General / Product FAQ's

FeBrowser FAQ's

FeEditor FAQ's

FePDF FAQ's

FeMedia FAQ's

NetTalk / FileExplorer FAQ's

The undocumented feStorage Class FAQ's

Examples

Upgrading from FileExplorer 4 to FileExplorer 5

What must I do to upgrade?

My saf password does not work on the latest File Explorer install. Where do I get a new password?

Considerations if upgrading from a version earlier than 3.70 Gold

What you need to do to your existing apps that use a version of FE earlier than 2.9 Beta

Compile Errors and how to fix them:

Other changes you need to know about:

Internet Explorer Version Info

Header / Footer Strings for IE Page Setup

Using DebugView

File Explorer and The Future (The "ToDo" List)

File Explorer Version Numbers

Version History

FeEditor

Other

CapeSoft File Explorer
Documentation