E. Gladyshev [EMAIL PROTECTED] wrote:
I don't know much about other GUI systems but win32
and MFC. I think we can try to define the low-level
layer using win32 and/or MFC as the starting point.
Please, do NOT use MFC. Just native Win32 API as a starting point. MFC
is 1) not available on mingw
E. Gladyshev [EMAIL PROTECTED] wrote:
** Option 1 (compile-time structure)
typedef std::list boost::entrylineEdit,
std::string listbox;
I like it. More compile time information better type safety, and more
space for user plugins (ie. template parameters) or future standard
library
E. Gladyshev [EMAIL PROTECTED] wrote:
GUI objects generate events. What is the best design
for it? Should the events handlers be executed
I do not know what is best design, but here's what I think about it:
- each window (or almost each - may it be widget, edit box, dialog,
data view, or main
Philippe A. Bouchard [EMAIL PROTECTED] wrote:
// ScrollViews, ButtonGroups, ListBox, ...:
typedef listwidget container;
struct container : listwidget { ... };
Uh. I would not recommend inheriting from STL. I think that template
policies would be rather more appropriate solution:
typedef
David Abrahams [EMAIL PROTECTED] wrote:
but the installer I used puts it in
C:\Program Files\Microsoft VisualStudio .NET
I think you missed yet another space
C:\Program Files\Microsoft Visual Studio .NET
^
B.
William E. Kempf wrote:
Could this not have been implemented with a critical section and use
TryEnterCriticalSection? Why was the mutex approach used for one and
not the other?
TryEnterCriticalSection is not portable. Specifically, it's not
available in the Win9x line.
Critical sections
