1. I'm using opera 11.01 and the tray icon is not swallowed, it is in the top left corner of the desktop, (should be bottom right, next to the time!).. this *occasionally* happened with older JWMs (shinobars builds and others before it...)..

freememapplet, deadbeef, pmusic and puptray work fine in the tray, as normal.. maybe opera is at fault.. anyone tested opera 12? other large tray apps?

2. also, if i maximise opera, then drag or double click the title bar to unmaximise (but it remains full size of screen), then do `jwm -restart`, the title bar of the opera window moves above the screen ... it happens often after, until you manually move the window away from the top of the screen...

this same 'maximise and top of screen' problem also happens with geany.. not tested with other programs..

3. sometimes i still have to click the 'show desktop' button twice for it to work ... cannot find the cause or reproduce it reliably...

4. `jwm -restart ` causes retrovol to disappear from the tray, other apps in tray unaffected... prob retrovol at fault..

5. `jwm -restart ` causes some windows to lose their settings: whether they're folded or not, thier position, minimised or not, etc... but I think i do see improvements in keeping the minimised windows still minimised, after `jwm -restart`

i'm using 1024x768x32, tested with dual screen setup and without, which made no difference to the above stuff..

BTW, I love the fact I can drag a window from 1 desktop to another in JWM... Use it often..

I'm testing V691 After running fixmenus and jwm-restart at the terminal following the installation, I thought I lost the tray for a moment, then realized it was on "autohide" so I reset it to "off". I'm guessing that you compiled jwm with this particular configuration? Other than that, I had to re-select my theme, and also re-edit _root_.jwmrc to get my custom category for Science back on the main menu. This was expected. Further, I was pleased to see that my custom keyboard settings were retained in jwmrc-personal and so for example: my "Prt Scr" key (Print Screen) still works.

All in all, it's looking great! I am not seeing any more partially hidden windows or dialog boxes in ROX. In some cases, the windows do meet the edge of the screen, and, it is over the tray, (layer change) but again, nothing is hidden. In other cases, the windows only meet the top edge of the tray. I am not sure why there is inconsistent behavior here... maybe just some fine-tuning is needed still. My thoughts are that any window or dialog box should meet the top edge of the tray rather than go over it --otherwise, it might be more difficult to access minimized applications from the tray if those apps are indeed obscured by other windows on the desktop.

Usually, I just delete the offending lines in jwmrc-theme and save my changes. It's my understanding that these tags are no longer used, and if that's the case, maybe this can be removed from the source-code.

Again, I like the fine sharp edges of the main menu and submenu. Maybe it's my imagination, but some of the menu icons seem to be clearer; detail is more visible In all, this version is such a noticeable improvement, I will be keeping it on my desktop for the time being.

Monsie_________________My username is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

Usability--opaque window dragging, menu navigation--is faster than ever; according to Top, every JWM restart increases memory footprint by about 1mb.

I have put a issue into jwm for joe to deal with on the memory leak as I could duplicate it.

Could you please explain "Useability--opaque window dragging" and if it's a problem or just a comment as I don't understand it?

@monsie
Thanks, it looks like I have used some of the old config files by error, I shall have to check it out and fix what's in the buildset again.

You want to see how clear the menu icons are when the screen matrix is 2048x1536 on a 20" screen if the iconset is goodenough, it's one of the changes joe did a few versions ago.

@OscarTalks, I have an almost full set of mageia 1 packages,when I need to I cheat, I add them on a frugal wary development partition until something works and I can test it, then just blow the savefile away and i'm good again to test on a clean partition.

@ ALL
I have a new version to build and test before release when I am off-shift next tuesday pm. You will need to be patient I'm afraid although by then he may have a further upgrade for me.
I have also a couple if puppy jwm scripts to look at and fix again at the same time, somehow I built with earlier ones when I did a 'step-back' because of problems found with jwm, my apologies.

[s]I think I may build two test versions for you to test with, one for upgrading puppy's that have not been 'played with' and to use with woof when building, and one that contains the minimum of changes for testing only, but when I release the version I think there should only be one again to avoid confusion.[/s]

EDIT no, after thinking and some discussions, there will only be one, and built with wary. I shall build and internally test tomorrow, if ok, it should appear for you to test the next day and if no serious problems arrive by the weekend I shall build a release copy.

thanksLast edited by scsijon on Tue 26 Feb 2013, 02:29; edited 2 times in total

Just a short note that version 692 will not appear as it has a few esoteric screen problems that needs to be sorted out that will cause joe I think some headaches.

Consider the existing 691 as safe to use and a RC quality build. I shall most likely put a release pet of this version out there by early next week when I have checked and fixed the scripts.

Also of general note is that after running fixmenus we should be using jwm -reload and not jwm -restart._________________Puppy T290 - BarryK's Racy but with T2 Version 9.0 is suspended since barry is back. I'm going back to designing and building myzt2 a Puppy Wayland-X.

I have built a final release version of jwm2-691 and removed the previous versions.

jwm is now in two pets (found in the first post on page1).

The first pet, jwm2-691-w5c.pet contains only the core jwm component and docs and for someone upgrading should be enough for those upgrading from Version 679 or later.

The second pet, jwm2-config-691.pet contains only the configuration components and will be needed for anyone either upgrading from a version pre jwm2-679 or working from woof.

Alternately to using the second pet, you can instead use 01micko's jwmconfig2-130213.pet mentioned with a link in the post above which works as well and has some additional functions which I do like.

When we go forward again, will depend on joe having time to sort out further problems. I do not recomend anyone building jwm-692 as it has problems with windows and scroll bars across a number of applications and puppy versions. In some cases it even cuts sections of the window off in the manner of taking a pair of scissors to a page, or only allows reductions to full screen size. I will of course continue to work with him to test and build against puppy until the next step is ready in which case this thread will again be used.

EDIT: 6 Mar - Joe has just notified me of a new jwm-697 fix for the screen oversizing. I'll build and test this afternoon.
EDIT2: 8 Mar - the last didn't work but about to build jwm-700.

There is also a couple of enhancement requests I have put in to joe for addition to jwm.

a) when only one virtual window, limit the app window to the virtual window so it doesn't totally dissapear off screen, with alternatives being, that no-part of the app window can be off screen, or only part of it can slide off.

b) when multiple virtual windows, you can slide a app window across so part of it goes into the adjacent virtual window and it is actually visable there rather than only having an app window appearing in one virtual window.

Does anyone have any other 'sensible' enhancement requests while we have his attention?

Does anyone have any other 'sensible' enhancement requests while we have his attention?

Please, get rid of this new, rectangular "crosshair" mouse pointer. I can't tell you, how amateurishly out of place and ultimately superflous it looks on the desktop! What was wrong with the simple, old cursor, that dictated acceptance of this novelty?

Does anyone have any other 'sensible' enhancement requests while we have his attention?

Please, get rid of this new, rectangular "crosshair" mouse pointer. I can't tell you, how amateurishly out of place and ultimately superflous it looks on the desktop! What was wrong with the simple, old cursor, that dictated acceptance of this novelty?

Sorry, but I'm not getting that, mine is an arrowhead.

If I remember correctly it's part of Pcur (under desktop) that sets that, not jwm._________________Puppy T290 - BarryK's Racy but with T2 Version 9.0 is suspended since barry is back. I'm going back to designing and building myzt2 a Puppy Wayland-X.

Why are those three symbols needed at all? What purpose do they serve, except adding anxiety and confusion to a user's experience? The upper right area of a window has already the needed symbols: minimize, maximize and close window. The good, old arrowhead pointer can pretty much do it's job without having to morph into something else. Scsijon, please ask Joe to ditch the symbols and revert to the old way.

Taking this opportunity, I'd like to ask a technical question. Perhaps, you or anyone else who knows, has an answer. JWM can be compiled "icon-less", as mentioned on their site. I'm curious to know what will happen to the tray in such a case. Will it be able to display tray icons, or not.

I'd imagine the 'no-icon' option would only apply to jwm elements (titlebars, menus, traybuttons, tasklist buttons), much like 'box wms - there'd still be text and popups. A possible 'exception' would be items that load in the systray/dock and perhaps swallowed apps (see .jwmrc-tray for if that applies or not)

Likely it would run a bit leaner (like fluxbox w/o imlib2 support)

By the way, personally I kind of like the change-of-pointer when the titlebar buttons are hovered. It lets me know a) the button is indeed active & a click will result in an action and b) that other functions can be invoked, like a r-click on the minimize button will toggle shade in these newer versions (I like multifunction titlebar buttons, m2 for max vertical and m3 for max horizontal on the max button would be nice)

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