~profzoom/wmaker/master : changes

~profzoom/wmaker/master » Changes from revision 3946

From Revision 3945 to 3926

Rev	Summary	Authors	Date
3945	Edit leftover automake files and READMEs for Serbian localiz... Edit leftover automake files and READMEs for Serbian localization This patch adds sr.po files to Makefile.am files throughout the repository where needed. It also adds credits for Serbian localization in README files as needed. Signed-off-by: Страхиња Радић <contact@strahinja.org>	Страхиња Радић	1 year ago
3944	Add Serbian localization Add Serbian localization This patch adds Serbian localization to Window Maker. Signed-off-by: Страхиња Радић <contact@strahinja.org>	Strahinya	1 year ago
3943	util/wmgenmenu.c(main): Close parentheses around vgradient util/wmgenmenu.c(main): Close parentheses around vgradient Currently, menu definitions created by wmgenmenu don't include the closing parenthesis in vgradient constructs. This patch adds the missing closing parentheses. Signed-off-by: Страхиња Радић <contact@strahinja.org>	Страхиња Радић	1 year ago
3942	Revert "WUtil: Be more strict about base directory for wmkdi... Revert "WUtil: Be more strict about base directory for wmkdirhier()" This reverts commit a0b283a60f734c38faa8e7cd594ace1657ce74b0, as it breaks saving the history in ~GNUstep/.AppInfo/WindowMaker/History by restricting modifications to either ~GNUstep/Defaults or ~GNUstep/Library. Thanks to Paul Selig for reporting this issue.	Carlos R. Mafra	1 year ago
3941	Update .gitignore Update .gitignore Since fc63d72032 (WINGs: Fix incorrect use of macro USE_PANGO in installed header) and 0e274dc979 (WRaster: Fix incorrect use of macro USE_XSHM in installed header) the files wrlib/wraster.h and WINGs/WINGs/WINGsP.h are generated by the compilation, so add them to .gitignore	Carlos R. Mafra	1 year ago
3940	Fix calculation of version number in the library mapfiles Fix calculation of version number in the library mapfiles As reported by Andreas Metzler, the latest API change in lib WRaster caused a compatibility issue because the internal version number was increased. To correctly handle this situation, this patch does 2 things: - do not discard the 2 last number in the "c:r:a" version, because we need them; - when calculating the version for the mapfile, use the formula that is suggested in libtool's documentation. The purpose of the formula is that when API is changed, if a new function is added then the version is not incremented to reflect that we are still compatible with current binaries, it will be incremented only when there is a break in compatibility.	Christophe CURIS	1 year ago
3939	Window Maker 0.96.0 Window Maker 0.96.0	Carlos R. Mafra	1 year ago
3938	Fix autoconf obsolete macros Fix autoconf obsolete macros autogen.sh is reporting some warnings as below ./autogen.sh 2>&1 \|grep "obsolete" libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:115: warning: The macro `AC_LANG_C' is obsolete. configure.ac:115: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.ac:134: warning: The macro `AC_LANG_C' is obsolete. configure.ac:134: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.ac:135: warning: The macro `AC_LANG_C' is obsolete. configure.ac:135: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.ac:146: warning: The macro `AC_LANG_C' is obsolete. configure.ac:146: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.ac:146: warning: The macro `AC_LANG_C' is obsolete. configure.ac:146: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.ac:373: warning: The macro `AC_LANG_C' is obsolete. configure.ac:373: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.ac:458: warning: The macro `AC_HEADER_TIME' is obsolete. configure.ac:681: warning: The macro `AC_TRY_LINK' is obsolete. configure.ac:807: warning: The macro `AC_TRY_LINK' is obsolete. As the minimum autoconf version required is v2.69, we need to make sure to update obsolete macros as described at https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Obsolete-Macros.html	David Maciejak	2 years ago
3937	Set proper motif wm hints name Set proper motif wm hints name Just a cosmetic change as the variable is currently not in use. According to the Motif Toolkit API and MwmUtil.h, the last long variable from the Motif WM Hints struct is currenlty used for the status.	David Maciejak	2 years ago
3936	Add central position feature for active window Add central position feature for active window This patch adds a new Central feature under the window menu "Other maximization" entry. Shortcut can be configured via WPrefs "Center active window" action. When called the active window is centered on the screen head. If the window height or width are bigger than the head size, the window is resized to fit. There are some transitions defined as below: from fullscreen to center from any corner to center from top half to center top half from bottom half to center bottom half from left half to center left half from right half to center right half Undoing the action is done via the window menu "Unmaximize" entry or the shortcut.	David Maciejak	2 years ago
3935	NEWS: Hot corners feature description NEWS: Hot corners feature description Add an entry in the NEWS to describe the Hot Corners feature.	David Maciejak	2 years ago
3934	WPrefs: Hot corner preferences WPrefs: Hot corner preferences Add a new "Hot Corner Shortcut Preferences" section to WPrefs to configure the Hot Corners feature.	David Maciejak	2 years ago
3933	Hot corners feature core Hot corners feature core Add mouse pointer position detection to trigger the corner actions. Screen corners can be assigned an external command to be executed when the mouse pointer is entering those areas. In WPrefs, "Hot Corner Shortcut Preferences" can be used for configuration or by manually adding a "HotCorners" key and value to "YES" in the ~/GNUstep/Defaults/WindowMaker file. Actions are specified by the "HotCornerActions" and are defined as a four entries list ("top left action", "top right action", "bottom left action", "bottom right action"). A screen corner area is a cube shape defined by the "HotCornerEdge" which is a number of pixels from 2 (by default) to 10. To lower the risk of triggering that feature accidentally a "HotCornerDelay" key can be used which is the time before the action is triggered while the pointer is in one of the screen corner. Default value is 250 ms. Hot Corners feature is disabled by default.	David Maciejak	2 years ago
3932	Fix internal function name typo Fix internal function name typo The patch is to fix a typo in the fct name movePionterToWindowCenter	David Maciejak	2 years ago
3931	WPrefs: fix keyboard shortcut sorting order WPrefs: fix keyboard shortcut sorting order That patch is fixing some Actions entries that are not sorted properly. One is using some upper/lower cases. And the other one, is displaying numbers while alphabetic sorting is not working properly on numbers. For example: Shortcut for window 1 Shortcut for window 10 Shortcut for window 2 ...	David Maciejak	2 years ago
3930	Add some more cases to handle window unusual size request Add some more cases to handle window unusual size request As discussed on the ML, the test to check for CARD16 limit is probably innacurate. Check instead for maxH and maxW which are set by default to twice the size of the screen or to the max values passed by the window normal hints property.	David Maciejak	2 years ago
3929	Fix ICCM ConfigureNotify request Fix ICCM ConfigureNotify request According to ICCM specs at [1] Not changing the size, location, border width, or stacking order of the window at all. A client will receive a synthetic ConfigureNotify event that describes the (unchanged) geometry of the window. The (x,y) coordinates will be in the root coordinate system, adjusted for the border width the client requested, irrespective of any reparenting that has taken place. The border_width will be the border width the client requested. The client will not receive a real ConfigureNotify event because no change has actually taken place. Moving or restacking the window without resizing it or changing its border width. A client will receive a synthetic ConfigureNotify event following the change that describes the new geometry of the window. The event's (x,y) coordinates will be in the root coordinate system adjusted for the border width the client requested. The border_width will be the border width the client requested. The client may not receive a real ConfigureNotify event that describes this change because the window manager may have reparented the top-level window. If the client does receive a real event, the synthetic event will follow the real one. *Resizing the window or changing its border width (regardless of whether the window was also moved or restacked). A client that has selected for StructureNotify events will receive a real ConfigureNotify event. Note that the coordinates in this event are relative to the parent, which may not be the root if the window has been reparented. The coordinates will reflect the actual border width of the window (which the window manager may have changed). The TranslateCoordinates request can be used to convert the coordinates if required. In Window Maker, the first case is not implemented: doing a synthetic ConfigureNotify to notify no changes were done. That's creating some issues with app like Citrix icaclient when sometime windows are blank and need to be moved to be refreshed. [1]https://x.org/releases/X11R7.6/doc/xorg-docs/specs/ICCCM/icccm.html#configuring_the_window	David Maciejak	2 years ago
3928	Update window.c copyright Update window.c copyright Just updating the copyright line in the file header.	David Maciejak	2 years ago
3927	WPrefs: update maximization feature descriptions WPrefs: update maximization feature descriptions Align the old maximization descriptions to the new visual indicator names. The internal shortcut names had also been updated, meaning a reconfiguration of the shortcuts in WPrefs is required.	David Maciejak	2 years ago
3926	Window menu: add maximization visual indicators Window menu: add maximization visual indicators Add visual indicators for the maximization options in the window menu.	David Maciejak	2 years ago

Older »