The menu highlight scrolling no longer works except with a strict plastik theme/widgets.
Affected are all TDE app menus and the TDE menu.
The build set is from two days ago but today I pulled the latest for tqt3, tqtinterface, and tdelibs and rebuilt. No change. I don't know what other changes have taken place because the commit page has updated in two days.
Darrell
The menu highlight scrolling no longer works except with a strict plastik theme/widgets.
What do you mean by menu highlight scrolling?
Scrolling /moving the mouse pointer up and down a menu results in the menu item being highlighted. The item highlighting only works with an all-plastik configuration.
Darrell
The menu highlight scrolling no longer works except with a strict
plastik
theme/widgets.
What do you mean by menu highlight scrolling?
Scrolling /moving the mouse pointer up and down a menu results in the menu item being highlighted. The item highlighting only works with an all-plastik configuration.
Darrell
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.
Tim
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.
Trinity must be modeled after Windows. Reformat, rebuild, reinstall.
What is the purpose of all of this style stuff other than to break things every few days?
Darrell
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.
Trinity must be modeled after Windows. Reformat, rebuild, reinstall.
What is the purpose of all of this style stuff other than to break things every few days?
Darrell
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.
Tim
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.
Expected? Sure. Yet you never post forewarnings or guidance of what to expect. You don't tell us what the changes affect so we can be watchful for specific changes or bugs. We just kind of stumble along the way.
Darrell
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.
Expected? Sure. Yet you never post forewarnings or guidance of what to expect. You don't tell us what the changes affect so we can be watchful for specific changes or bugs. We just kind of stumble along the way.
Darrell
My apologies. For the next week or so you might want to hold off on doing anything while I work through these problems.
Tim
My apologies. For the next week or so you might want to hold off on doing anything while I work through these problems.
That's fine. Just know that lately many bug resolution patches are being pushed. GIT users would like to take advantage of the fixes. :)
Darrell
What do you mean by menu highlight scrolling?
Scrolling /moving the mouse pointer up and down a menu results in the menu item being highlighted. The item highlighting only works with an all-plastik configuration.
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.
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.
Darrell
What do you mean by menu highlight scrolling?
Scrolling /moving the mouse pointer up and down a menu results in the
menu
item being highlighted. The item highlighting only works with an all-plastik configuration.
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.
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.
Very strange, as it works just fine here. What style(s) are you seeing this problem with?
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.
That sounds suspiciously like a system issue, not a TDE one, unless you are referring to TQt3 based applications?
Tim
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.
Very strange, as it works just fine here. What style(s) are you seeing this problem with?
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.
That sounds suspiciously like a system issue, not a TDE one, unless you are referring to TQt3 based applications?
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
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.
Very strange, as it works just fine here. What style(s) are you seeing this problem with?
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.
That sounds suspiciously like a system issue, not a TDE one, unless you are referring to TQt3 based applications?
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
I can definitely understand that! Why don't you stick with the Oct. 29 build until I figure out what happened. :-)
Tim
I can definitely understand that! Why don't you stick with the Oct. 29 build until I figure out what happened. :-)
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
I can definitely understand that! Why don't you stick with the Oct. 29 build until I figure out what happened. :-)
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
Understood. :-) I'll take a look at the commits page tomorrow; it should be updating at least twice a day.
The style overhaul grew out of a little project that turned out to be much larger than I had thought. I have actually been working on the style engine for months now, and while it is very close to being usable with other toolkits there are still some problems remaining.
Tim
On 3 Nov 2012, Timothy Pearson uttered the following:
The style overhaul grew out of a little project that turned out to be much larger than I had thought.
When you find these things, you might want to drop a tag in history immediately before you started on the overhaul, perhaps an occasionally- moved 'latest-believed-working' tag or something, so that people tracking trunk know that this is the most recent version known to build for you at least.
(Chromium has something similar with their Last Known Good Revision webpage, which tracks the most recent version that their autobuilders managed to build and test successfully.)
-
Darrell Anderson -
Nix -
Timothy Pearson