[MiNT] SV: WCOWORK vs WINDOM for components

[Jo Even Skarstein <joska@online.no>]

> From: evan@coolrunningconcepts.com
> Sent: 2005-07-23 10:42:40 CEST
> To: Jo Even Skarstein [joska@online.no]
>
> Module X uses WCOWORK, Module Y does not.  Module Y calls wind_create()
> expecting that wind_create() uses the FULL area of the window, but WCOWORK
> being in effect means that all calls require the WORK area instead.  The API
> changes!
> 
> Suddenly, how one module behaves DOES depend on what another module does!

But then WCOWORK is a part of the interface! I still don't see the problem here.

> So what breaks if we have seperate calls instead?

What happens if the same application use both the old way and WCOWORK to deal with windows? What's the point in WCOWORK at all then?

Jo Even