Mercurial > dwindows
view readme @ 839:ccfa5173659f
Initial implementation of scrollboxes on Windows.
Windows does not have a scrolledview/area widget like on other platforms, so I have created one.
Implemented the layout system like I did on MacOS and discovered what likely is the issue on the Mac.
There seems to be a bug in the layout system which is avoided by packing into a single expandable box.
When used and padding are exactly the same, the layout engine drops out to prevent a divide by zero.
Will look into fixing this in the layout engine, but for now using the container box workaround.
The scrolled view widget is not finished, will need to implement the scrollbars but internally.
author | bsmith@81767d24-ef19-dc11-ae90-00e081727c95 |
---|---|
date | Tue, 29 Mar 2011 17:21:50 +0000 |
parents | 230686a7eba9 |
children | ea15fee48da8 |
line wrap: on
line source
This is an beta release of dynamic windows version 1.0.0. The current Dynamic Windows source base is relatively stable on OS/2, Windows, Linux, FreeBSD and Solaris. When the beta feature set is stable I will release a final. Known problems: Boxes don't adhere to ratios on Unix. Known limitations: It is not safe on all platforms to operate on widgets before they are packed. For portablity pack widgets before operating on them. On Windows a slider control will only work properly if it is the only slider in a box. If there is more than one slider control in a box then signals may get misdirected to the wrong control. On OS/2 and Windows MLE controls scrolled position may get corrupted when resizing. On Unix the window manager border is not a constant value so environment variables DW_BORDER_WIDTH and DW_BORDER_HEIGHT are used for proper positioning. Future features: Implementing a full set of controls. Most controls common to OS/2, Windows and GTK have been implemented. Although not all the functionality of the native controls have been integrated into Dynamic Windows. Documentation, I have all the functions relatively well documented in the source code but a developer's manual and online API reference will need to be written. If you have any questions or suggestions feel free to email me at dbsoft@technologist.com Thanks! Brian Smith