Quickwin 40 child window limit

[parker9]

according to the Help w/ IVF, Quickwin applications are limited to 40 child windows.

1) is there a way to increase this limit?
2) to go beyond 40 windows, would i have to do a Windows application?

if i have to do a Windows application, do i also have to rewrite my graphics routines (which uses Quickwin routines) to use win api instead? basically, in general, would one expect a significant amount of work/coding going from Quickwin to Window application?

thanks in advance

[Jugoslav_Dujic]

As a middle ground, you could try Xeffort (see my signature). It is a thin wrapper library around Windows applications, (source code available), and it's much more powerful than QuickWin. When something is not directly supported by Xeffort wrappers, it's easy to directly use Win32 APIs.

However, even with Xeffort, you will have to rewrite and restructure your application. Xeffort graphic routines (XFTGDI) do resemble QuickWin ones and are simpler to use than Win32, but still are not the same as QuickWin. Also, the code structure can be quite different -- most of the code is stored in handlers (callbacks).

[parker9]

Jugoslav- thanks, I had looked at xeffort.com... i wanted a quick fix since this is contract work and can't afford to do any major rewrite on this part of the code. short term answer is to tell them this is outside of my control and they simply can not have more than 40 windows. longer term would be to offer to code a windows application or use some graphics library where the number of windows is not limited, but on a different PO. i just wanted to make sure it wasn't some parameter that could be changed. thanks for your reply!