Of course then you just get a 'standard' pointer for the hovers. Some cursor sets like Neutral_Plus_Inverted (aka npi) actually look really good for the hovers - the appearance is fairly intuitive, anyhow .. even a few surprises in that set (a proper right_ptr for one)

On the testing side, did a quick-o compile of 707 in p431 - it crunked out on src/fonts with default options enabled, but fine with my usual disables .. glad scsijon does do his with fribidi and so on for the wider base of users. For a lark, I tried that binary in racy 5.4.91 .. seems fine on all the major functions.

Minor - tried the new tasklist attribute border="0" (or "false") in tray file, border/outline persists on buttons (windowbuttons in tasklist and traybuttons as well) It's a cosmetic preference to be sure, full windows or shaded titlebars take a border/outline well but it can look a bit overdone in the confines of a tray (with some themes it's more noticeable than others). Maybe something odd on my side (disables or using the p431 binary in racy), will test again when scsijon does a 707..

___721 compiled on p431___addenda 130404___
.. really seems to be getting a handle on the compmgr-max-toggling thing ..
puppy 4.3.1 - still has remnants (max-* toggled from titlebar buttons)
racy 5.4.91 - no remnants at all, very stable with all control methods
wary 5.1.4 - if toggled from winmenu, all is fine .. toggling from titlebar buttons gives a variety of repeatable results (differing dependent on if k or xcompmgr used)

thank you 'f00,
yes, the systemconf line is misleeding as we don't use it, but it has to be there in the build, it won't build without it. I remove the file before I pet it up to both save space and make sure the jwm default one isn't used as it's nothing like puppy's (it's really an example). JWM looks for a $HOME/.jwmrc first anyway, which for us is /root/.jwmrc.

I shall report the remnants problem. Personally I haven't seen it in testing, but I shall re-check and see what I find.

EDIT: a quickcheck and it's not happening with rox-filer, thunderbird, firefox or a console screen. However I have reported it anyway, maybe it's a quick find and fix. Maybe it's worth adding a link for kcompmgr in your message above in case he wants to download it to test with.

Round windows are madness anyway (pixels and screens aren't round). I still find it surprising that people want that feature in JWM..._________________If you have or know of a good gtkdialog application, please post a link here

joe has created a new 'head' snapshot with version 726, these are master base versions.
I shall build this afternoon when back home and upload this evening._________________Puppy T290 - BarryK's Racy but with T2 Version 9.0. First Beta planned out end of August 2017.

joe's been at it already, we now have a 729, I shall build and upload tonight. It's mainly cleanup of unused functions, and make configure find the right XPM library on IRIX so doesn't concern us directly.

I'm going back to mage2 for a few days of pre-'last' beta release fixes before a general and Final 'Last Beta Release early next week so don't expect anything much till then._________________Puppy T290 - BarryK's Racy but with T2 Version 9.0. First Beta planned out end of August 2017.

The easiest explained is the close 'X' button will bring up a kill message window if the true function of the button is to kill the window instead of just closing. In this case you will usually find an onscreen 'quit' button available, which you should really be using.

Also problems with XML parsing issues with entities have been attended to.

And the compiled options listed in help has been updated to the current status.

I plan on leaving the Version 731 as release level for a while now.

The test version will update as they ocurr as has been for the last few months.

Observations on v722 :
* In Puppy 43 when X is killed, freememapplet and inotifywait aren't killed . v456 does it fine .
* When i have geany open, and navigate in another virtual window to a textfile in rox and click open as text, all virtual windows show a geany with a non-working window-top-frame except the source virtual window .

___

v456 is fine enough for me, cannot reproduce all the problems ie shinobar and patriot were working on in pre-500 times.

I about refusing to test further and am not expecting any improvements in jwm in the next future .

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum