Re: [MiNT] WCOWORK vs WINDOM for components

["Joakim Högberg" <gokmase@gmail.com>]

======= At 2005-07-23, 10:42:40 Evan wrote: =======

>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!

Shouldn't these modules be able to receive and pass information on what mode the main
program is running in? 

>From where I stand, this should not be too complex really:

1) XaAES would use the WCOWORK On/Off setting for any window that belongs to
an application id.  

2a) Hence, it would have to be the responsibility of the application (if it aims to support the new mode)
 to tell its modules which mode is the one currently in use.

2b) If one Module X is calling another Module Y, then it would have to be responsibility of Module X to supply any information
that Module Y would be in need of. In this example, Module Y would most certainly need to be told whether the main
application has enabled WCOWORK or not.


Or am I getting this the wrong way..?


Regards,

/Joakim