Category: WX

NumToString

Since WX treats screen controls as strings (including columns of a table) Trace(NumToString(COL_HstInvHdrSysId,"012d")) does not work. You don't get an error, it just doesn't do anything because it's not a number. So if COL_HstInvHdrSysId contains 123456 the result will be 123456. instead you have to do: nHstInvHdrSysId is int = COL_HstInvHdrSysId Trace(NumToString(nHstInvHdrSysId,"012d")) Now you will … Continue reading NumToString

Issues with Storing Window Position With Multiple Monitors

Photo by SOYBEANTOWN While working on the Document Viewer Component I ran into a few issues with the standard WinDev window position restore logic with dual monitors, so I created a couple global procedure to work around the issues. WinDev will save the size and position of each window in your application. This allows end users … Continue reading Issues with Storing Window Position With Multiple Monitors

A Document Viewer Component using Native WinDev Functions

Early in my career I created a custom document storage solution as part of several of my applications. This led to the Clarion Imaging Templates and later the Imageman Templates, both using third party OCX's. Recently one of those customers wanted some enhancements to their application, and I decided I would rather spend a couple of days converting the application into WinDev, than adding features in C6 that are built into WinDev. My first step was to explore the possibilities of using WinDev native functions to create a document viewer instead of using a third party library. I was pleasantly surprised at how easy it was and how much functionality was supported directly by WinDev.  The resulting Document Viewer is very light weight and handles most of the normal requirements, its not as powerful as I would like, put it will do for this project until I create a Document Viewer using a third party .net library at some point in the future. At the end of the article you will find a download link for the Component and the source code.

Enhancements to a Clarion Application when converting to WinDev

Many of my clients are asking for updated applications and modern features, that they have seen in some of my latest WinDev Applications. As I began making proposals for several of these conversion projects, I realized that I need a standard general comparison of some of the look and feel, and features that would be include in any application that I convert from Clarion to WinDev. The article that follows is the basis of that comparison.

A WinDev Approach to Clarion Queues

In Clarion, I use queues quite a bit as a great way to deal with multiple instances of structured data in memory instead of storing in a table or file. WinDev has several advanced data types that can be used, but none of them are the exact same as a Clarion Queue. This includes: Simple Arrays, Associative Arrays, Dynamic Arrays, Fixed Arrays, Composite Variables, Structures, Dynamic Structures, Queue, List, Stack, and then there are memory tables which are not technically a variable type.