WMNewApp.1 (1737B)
1 .\" This program is licensed under the terms of GNU GPL v3 or (at your option) 2 .\" any later version. Copyright (C) 2020-2024 Yourname Here. 3 .\" See the file LICENSE for exact copyright and license details. 4 .Dd January 1, 2024 5 .Dt WMNEWAPP 1 6 .Os 7 .Sh NAME 8 .Nm WMNewApp 9 .Nd Describe your newly generated application 10 .Sh SYNOPSIS 11 .Nm 12 .Op Fl dh 13 .Sh DESCRIPTION 14 .Nm 15 is an example app generated with 16 .Sy wmgen . 17 . 18 .Ss Command line options 19 .Bl -tag -width ".Nm Fl h" -offset indent 20 . 21 .It Nm Fl d 22 Turns on debug mode. 23 . 24 .It Nm Fl h 25 Prints usage information. 26 . 27 .El 28 .Sh SEE ALSO 29 .Xr wmaker 1 30 .Sh AUTHORS 31 .An "Yourname Here" Aq address@example.com , 32 2020-2024 33 .Sh BUGS 34 .Bl -dash -width "-" -offset indent 35 .It 36 WINGs bug: when 37 .Dq Shared application icon 38 is selected for an application generated with 39 .Sy wmgen , 40 one of the two things happen, depending on whether 41 .Fn WMMapSubwidgets 42 and 43 .Fn WMMapWidget 44 for the main window is called before (A) or after (B) creating the main menu: 45 .Bl -tag -width "A)" -offset indent 46 .It A) 47 Every instance of that application will generate a 48 .Dq phantom copy 49 of the application menu, which persists after closing the application, can't be 50 closed with 51 .Sy xkill , 52 apparently isn't associated with any process, and for which 53 .Sy xprop 54 doesn't detect any properties. 55 Interestingly, when the main application is closed, and relaunched, the extra 56 copies of menus work in the new instance. 57 .It B) 58 The menu is not shown at all. 59 This is the same behavior/known bug as in 60 .Sy FSViewer . 61 .El 62 .Pp 63 I chose to follow option (B), same behavior as in 64 .Sy FSViewer . 65 I believe that having no menu at all, and behaving consistently with known 66 application is better than having leftover uncloseable copies of menus around. 67 [SR] 68 .El