What do you mean by menu highlight scrolling?

Have you done a full recompile/reinstall of tdelibs and friends after a full recompile/reinstall of TQt3? There may have been some minor style engine ABI breakage recently, and there will be some more coming shortly as I resolve other style-related deficiencies and issues.

You are tracking the development branch; such things are to be expected! ;-) Did you see my message last night regarding the GTK3 theme engine? Essentially I am modernising the TQt3 style engine so that it can be used natively with other toolkits such as Qt4 and GTK3.

My apologies. For the next week or so you might want to hold off on doing anything while I work through these problems.

I updated GIT a couple of hours ago, short version 8488. As always, a clean build from scratch. I rebuilt all core modules. Menu item highlighting remains broken.

The Alt key is broken. That is, sequentially pressing Alt, F, O no longer functions. I have to concurrently press Alt-F to open the app File menu. The Alt breakage affects non Trinity apps too.

The only non Trinity app I tested the Alt key was Firefox. but sequential usage of the Alt failed there and in all Trinity apps. The problem is the recent commits. I reverted to GIT short version 8443 from Oct. 29 and both the menu item highlighting and the Alt key function normally again. I use the KDE 2 window decoration, KDE Classic widget style, and crystalsvg icon set. I don't use themes. With the GIT 8462 build set from yesterday I tested other window decorations and widget styles. Only a combined plastik window decoration and widget style allowed menu item highlighting to work. I did not test the Alt key problem when I was testing the menu item highlighting. I discovered that problem about an hour after, at which point I reverted to my Oct. 29 8443 build because both problems were creating serious usability dysfunction with my habits. Darrell

Sure. My desktop is again stable with the Oct. 29 package set. I save my package sets for this exact purpose. :) Somebody has to test GIT on a continual basis or these bugs would remain undiscovered for long periods. You know me --- I can break, er test, things as fast as you patch them. :) Some breakage is expected but sometimes the breakage impairs usability. I was almost tolerating the menu item highlighting breakage but the loss of the sequential Alt key killed me. I only get frustrated when we are not informed of these major overhauls and the commit page doesn't update for several days at a time. We then have no forewarning of potential breakage or what to test (people using the GIT branch accept that they test every day). When the commit page is current I can figure out what to reverse to help debug. When the commit page isn't updated there is no way not to know there are subsequent commits. At that point trying to reverse anything becomes classic spaghetti. Well, there probably is a way with a fancy script of some sort to parse each module's commits, but I don't have anything like that. I guess the whole point is with a lack of communication the proverbial left hand does not know what the right hand is doing. :) Darrell