Mercurial > dwindows
view readme.txt @ 2447:8723c01fb87e
iOS: Fix bug in dw_pixmap_new_from_file(). Resources go into the app
directory on iOS it seems. Remove a couple debug messages in dwtest from
that last commit.
author | bsmith@81767d24-ef19-dc11-ae90-00e081727c95 |
---|---|
date | Fri, 09 Apr 2021 22:17:42 +0000 |
parents | 9ae60d8f4ea3 |
children | e747f03699e7 |
line wrap: on
line source
This is a stable release of Dynamic Windows version 3.2. The current Dynamic Windows source base is considered stable on: OS/2, Mac, Windows, Linux, FreeBSD and OpenSolaris. Build Recommendations: MacOS: 11.0: configure --with-arch=modern --with-minver=10.14 64bit Intel and Apple Silicon (ARM64) with Dark Mode. 10.13-10.15: configure --with-minver=10.8 64bit Intel with Notifications, Dark Mode for 10.14-15. 10.8-10.12: configure --with-arch=intel --with-minver=10.8 64 and 32bit Intel with Notifications but no Dark Mode. 10.5-10.6: configure --with-arch=classic --with-minver=10.5 32bit PowerPC, 64bit and 32bit Intel classic support. No Notifications, Dark Mode nor NSView container/trees. Windows: 7-10: Visual Studio 2017-2019, WebView2 and WinToast. Should run on Vista and later, supports domain sockets on Windows 10, oldsockpipe() on older versions. XP: Visual Studio 2010. Should run on XP and later, with Aero on Vista and 7. No Notifications nor WebView2 and oldsockpipe() on all. 2000: Visual Studio 2005. Remove -DAEROGLASS from CFLAGS. Should run on 2000 and later, no Aero, Notifications, WebView2 and oldsockpipe() on all versions. Known problems: Boxes with no expandable items will have their contents centered on GTK2 instead of top or left justified on the other platforms. GTK3 due to changes in the core architecture does not support widgets that are smaller than what is contained within them, unless they use scrolled windows. GTK2 and other platforms do. Therefore windows or other elements may expand their size to fit the contents, overriding requested size settings. In Unicode mode on OS/2 there are some bugs in the input controls, minor bugs in entryfield based controls and major bugs in the MLE. The text displays properly but the cursor and selection jumps around oddly when passing over multibyte characters. Known limitations: It is not safe on all platforms to operate on widgets before they are packed. For portability pack widgets before operating on them. Future features: OS/2 is currently missing the HTML widget because the system does not support it by default. Looking into importing functionality from available libraries (Firefox, Webkit, Qt, etc). OS/2 is also missing a notification system, so the new notification APIs are not yet supported on OS/2. May implement our own system if a popular notification system is not already in existance. Ports to iOS and Android are underway. Changes from version 3.1: Added initial support for GTK4. --with-gtk4 is now available. GTK4 support is less complete than GTK3, a number of features of the GTK3 version are no longer possible in GTK4 like: Taskbar icon support, MDI, gravity and non-callback drawing. Added initial support for Wayland on GTK3 and GTK4. Wayland is not in my opinion ready for prime time, many features, possibly a half a dozen functions, dealing with coordinates, mouse pointer grabbing and such are unable to function. I recommend sticking with X11 for now, but built with GTK3 or GTK4 Dynamic Windows applications will run on Wayland now. Added dw_render_redraw() function to trigger a DW_SIGNAL_EXPOSE event on render widgets allowing drawing to happen in the callback. GTK4 and GTK3 with Wayland require drawing to be done in the callback, necessitating a dw_render_redraw() or dw_flush() call. dw_flush() may cause multiple draw passes. Added support for dw_window_set_font() with a NULL font paramaeter. This resets the font used on the widget to the default font. Fixed GTK warnings on GTK3 caused by using Pango style font syntax. Fixed GTK3 leaks when setting fonts or colors on a widget repeatedly. Fixed incorrect reporting of word wrap support on Windows. Fixed a number of misbehaviors with dw_window_set_font() and dw_window_set_color() on various platforms. Added missing DW_CLR_DEFAULT support on OS/2, it previously only worked to avoid setting a color, not resetting them to default. Added oldsockpipe() macro which will be used as a fallback. This allows us to use domain socket sockpipe() when available... and fall back to the old version when not, letting us have Windows 10 domain socket builds that work on earlier versions. Fixed building and several issues related to MacOS 10.5 now that I have a PowerMac G5 running 10.5.8 to test on. Dynamic Windows Documentation is available at: http://dbsoft.org/dw_help.php If you have any questions or suggestions feel free to email me at: brian@dbsoft.org Thanks! Brian Smith