From: Jared <lis...@le...> - 2010-03-30 07:08:00
|
On 03/30/2010 01:36 AM, D. Michael McIntyre wrote: > This is KDE, not Qt. The only way Rosegarden will have similar functionality > is if someone writes it all from scratch, in-house. If this were simple to > do, the sheer demand for this feature would have been plenty of incentive to > take a bit of time out to sit down and code it. > > Unfortunately, it's not simple at all. It's going to be a pretty big > undertaking, and this is the kind of thing that is pretty much just going to > sit on the back burner until somebody gets around to it. I couldn't possibly > guess at a timeframe. My bad. I looked through the Rosegarden dependencies on Gentoo and didn't see KDE explicitly listed, so I just assumed (and, obviously, assumed incorrectly). I never meant to imply that this was simple. After all, as you said, if it was simple it'd probably already be done. I am, however, curious as to why it would be such a major undertaking. As I mentioned before, KDE apps seem to have a pretty standard way of handling hotkey configuration - they pretty much all have a Settings, Configure Shortcuts option that pulls up a standard configuration dialogue that lists available actions and matching shortcuts. Just superficially it seems like most of the backend code is shared/provided by KDE itself, with the application primarily mapping actions and shortcuts on top of that. I'm sure none of this is new to you, but for curiosity's sake could you explain why Rosegarden couldn't take a similar approach as other KDE apps? or maybe I'm just way off on what's involved. Thanks, and I appreciate the information. -- Jared |