Menu
▾
▴
[Rosegarden-bugs] SF.net SVN: rosegarden:[10246] website/wiki/data
|
From: <ca...@us...> - 2009-05-04 09:44:38
|
Revision: 10246
http://rosegarden.svn.sourceforge.net/rosegarden/?rev=10246&view=rev
Author: cannam
Date: 2009-05-04 09:44:28 +0000 (Mon, 04 May 2009)
Log Message:
-----------
* Update SVN from live wiki
Modified Paths:
--------------
website/wiki/data/pages/dev/9.x.txt
website/wiki/data/pages/dev/coding_style.txt
website/wiki/data/pages/dev/contributing.txt
website/wiki/data/pages/dev/making_strings_translatable.txt
website/wiki/data/pages/dev/qt4_bug_tracker.txt
website/wiki/data/pages/dev/slog_endgame.txt
website/wiki/data/pages/dev/style_bugs.txt
website/wiki/data/pages/low-latency_kernels.txt
website/wiki/data/pages/start.txt
Added Paths:
-----------
website/wiki/data/media/
website/wiki/data/media/dev/
website/wiki/data/media/dev/regression-10127-a.jpg
website/wiki/data/media/dev/regression-10127.jpg
website/wiki/data/media/dev/regression-filedlg-dropdown.png
website/wiki/data/media/dev/regression10211-1.jpg
website/wiki/data/media/dev/regression10211-2.jpg
website/wiki/data/media/dev/regression2.png
website/wiki/data/media/dev/regression_prevention_snapshot_1.png
website/wiki/data/media/dev/tooltip.png
website/wiki/data/media/managemididevices1.png
website/wiki/data/media/managemididevices2.png
website/wiki/data/media/matrix1.png
website/wiki/data/media/matrix2.png
website/wiki/data/media/matrix3.png
website/wiki/data/media/matrix4.png
website/wiki/data/media/matrix5.png
website/wiki/data/media/matrix6.png
website/wiki/data/media/matrix7.png
website/wiki/data/media/matrix9.png
website/wiki/data/media/rambling-800.jpg
website/wiki/data/media/whiteboard.jpg
website/wiki/data/media/wiki/
website/wiki/data/media/wiki/dokuwiki-128.png
Added: website/wiki/data/media/dev/regression-10127-a.jpg
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/regression-10127-a.jpg
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/dev/regression-10127.jpg
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/regression-10127.jpg
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/dev/regression-filedlg-dropdown.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/regression-filedlg-dropdown.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/dev/regression10211-1.jpg
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/regression10211-1.jpg
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/dev/regression10211-2.jpg
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/regression10211-2.jpg
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/dev/regression2.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/regression2.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/dev/regression_prevention_snapshot_1.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/regression_prevention_snapshot_1.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/dev/tooltip.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/dev/tooltip.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/managemididevices1.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/managemididevices1.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/managemididevices2.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/managemididevices2.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix1.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix1.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix2.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix2.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix3.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix3.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix4.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix4.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix5.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix5.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix6.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix6.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix7.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix7.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/matrix9.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/matrix9.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/rambling-800.jpg
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/rambling-800.jpg
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/whiteboard.jpg
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/whiteboard.jpg
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: website/wiki/data/media/wiki/dokuwiki-128.png
===================================================================
(Binary files differ)
Property changes on: website/wiki/data/media/wiki/dokuwiki-128.png
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Modified: website/wiki/data/pages/dev/9.x.txt
===================================================================
--- website/wiki/data/pages/dev/9.x.txt 2009-05-04 02:45:03 UTC (rev 10245)
+++ website/wiki/data/pages/dev/9.x.txt 2009-05-04 09:44:28 UTC (rev 10246)
@@ -1,11 +1,11 @@
-====== ROSEGARDEN 09.X (to be) RELEASED ======
+====== ROSEGARDEN 09.10, codename "Abraham Darby" (to be) RELEASED ======
**IMPORTANT: THIS HAS NOT HAPPENED YET**
-**This page is only a working area for making notes about what is being done for the 09.x release, so that we don't forget anything when the code is finally ready to be released -- which will not be for some time yet.**
+**This page is only a working area for making notes about what is being done for the 09.10 release, so that we don't forget anything when the code is finally ready to be released -- which will not be for some time yet.**
-The Rosegarden team is proud to announce the release of version 09.x of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. This is version 9x of the modern 21st century Rosegarden (formerly known as Rosegarden-4) and should not be confused with the old, obsolete X11 Rosegarden (formerly known as Rosegarden).
+The Rosegarden team is proud to announce the release of version 09.x of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux.
http://www.rosegardenmusic.com/
@@ -22,6 +22,7 @@
* Yves Guillemot
* Chris "CJ" Fryer
* Heikki Junes
+ * Shelagh Manton
===== Thanks To =====
* Luis Garrido
@@ -32,20 +33,30 @@
* Removed all ties to KDE for a lower dependency footprint
* Stunning new look that is equally at home on KDE, GNOME, or any other Linux desktop
* Most application resources are now bundled inside the application itself, reducing its installation footprint, and allowing you to run different versions (eg. a stable production version and a release candidate) in parallel without data file version conflicts
- * You can finally run more than one copy of Rosegarden at the same time
+ * You can finally run more than one copy of Rosegarden at the same time!
* Completely new icons for the notation editor, and anywhere else we could benefit from true antialiasing as opposed to simple transparency
- * New MIDI device manager
+ * All new MIDI device manager
+ * New "Save As Template" option saves files with a special new .rgt extension, which discourages you from overwriting your template for a string quartet with your newest composition for string quartet. (As time goes on, we will be putting together a collection of useful templates in much the same way as we have been accumulating MIDI device library files over the years.)
+
+(this is minor stuff)
* Improved flashing metronome mode and more realistic looking LEDs for the transport
* Markers now have a "Comment" instead of a "Description" to make it more clear which bit of text is going to show up on the marker ruler, and be exported to LilyPond
+ * The simple event editor now handles notation-quantized notes more intelligently
+ * Improved controller manager dialog now opens the editor automatically after creating a new controller
-
====Significant Bug Fixes====
* Exporting project files to paths that have spaces no longer fails
* Faders can now be moved in both directions with the mouse scroll wheel
* Corrected LilyPond export of double octave clefs
+ * Corrected rendering problem when moving expanded-height tracks
+====Minor Bug Fixes====
+ * Controller editor dialog now keeps track of the color index properly
+ * Newly created knobs of color "default" now display the correct color, rather than black
+
+
====Thanks to====
===Active translators for this release:===
* Heikki Junes
@@ -58,3 +69,4 @@
* Greg Lyons
* Georg Balzer
* Theo Smit
+ * ADR
Modified: website/wiki/data/pages/dev/coding_style.txt
===================================================================
--- website/wiki/data/pages/dev/coding_style.txt 2009-05-04 02:45:03 UTC (rev 10245)
+++ website/wiki/data/pages/dev/coding_style.txt 2009-05-04 09:44:28 UTC (rev 10246)
@@ -18,7 +18,7 @@
// 2
class SomeUsefulClass
{
- // code
+ //code
};
// 1
// 2
@@ -26,6 +26,7 @@
</code>
* Braces are what you might call Java-style, which means:
+
<code c++>
int
SomeClass::someMethod(int f)
@@ -67,6 +68,7 @@
connect( detailsButton, SIGNAL( clicked(bool) ), this, SLOT( slotDetails() ) );
</code>
+ * Pointers are ''MyObject *ptr;'' not ''MyObject* ptr;''
* If you have more arguments than will fit on a reasonable length line (80 characters is a good figure, but this is not a hard rule), align the extra arguments below and just after the opening ( rather than at a new level of indentation:
<code c++>
Modified: website/wiki/data/pages/dev/contributing.txt
===================================================================
--- website/wiki/data/pages/dev/contributing.txt 2009-05-04 02:45:03 UTC (rev 10245)
+++ website/wiki/data/pages/dev/contributing.txt 2009-05-04 09:44:28 UTC (rev 10246)
@@ -1,25 +1,24 @@
+(still needs more editing, but I'm leaving it alone for now)
======HOWTO contribute bug fixes and feature enhancements to Rosegarden project======
+There are numerous ways to contribute to Rosegarden. You may
-
-There are numerous ways to contribute into Rosegarden. You may
-
* Create a patch (described in this page)
* [[http://rosegarden.sourceforge.net/tutorial/bug-guidelines.html|Report a bug]]
- * [[http://sourceforge.net/tracker/?group_id=4932&atid=354932|Create a feature request]]
+ * [[http://sourceforge.net/tracker/?group_id=4932&atid=354932|Create a feature request]] (Please understand that it typically takes two years or longer for a feature request to be implemented, and many of them will never be implemented.)
* [[Add or update translation]]
* [[http://sourceforge.net/mail/?group_id=4932|Discuss in Rosegarden's mailing lists]]
- * Update documentation
+ * Update documentation (needs a page, but first we actually need to establish a new documentation structure)
-Let's proceed on and follow steps on howto prepare a patch for Rosegarden...
+Let's proceed on and follow steps on how to prepare a patch for Rosegarden...
@@ -27,21 +26,21 @@
===1.A) As an anonymous user===
-svn co [[https://rosegarden.svn.sourceforge.net/svnroot/rosegarden/trunk|https://rosegarden.svn.sourceforge.net/svnroot/rosegarden/trunk/rosegarden]]
+<code bash>svn co https://rosegarden.svn.sourceforge.net/svnroot/rosegarden/trunk/rosegarden</code>
===1.B) As a sourceforge user===
-svn co [[https://us...@ro.../svnroot/rosegarden/trunk|https://<user>@rosegarden.svn.sourceforge.net/svnroot/rosegarden/trunk/rosegarden]]
+<code bash>svn co https://<user>@rosegarden.svn.sourceforge.net/svnroot/rosegarden/trunk/rosegarden</code>
====2. Compile source (be prepared to install missing dependencies in first compile)====
-$ cmake .
+<del>$ cmake .
$ make all
$ sudo make install
-As an alternative to the first step, you can run "ccmake ." (note the extra "c") for a curses-based interactive way of adjusting the build parameters (installation prefix, build options etc).
+As an alternative to the first step, you can run "ccmake ." (note the extra "c") for a curses-based interactive way of adjusting the build parameters (installation prefix, build options etc).</del>
====3. Make changes and recompile====
Modified: website/wiki/data/pages/dev/making_strings_translatable.txt
===================================================================
--- website/wiki/data/pages/dev/making_strings_translatable.txt 2009-05-04 02:45:03 UTC (rev 10245)
+++ website/wiki/data/pages/dev/making_strings_translatable.txt 2009-05-04 09:44:28 UTC (rev 10246)
@@ -1,5 +1,6 @@
+THIS DOCUMENT IS OBSOLETE AND NEEDS TO BE EDITED HEAVILY OR REPLACED
-======Making strings translatable======
+<del>======Making strings translatable======
@@ -90,3 +91,4 @@
=====Overview of KDE translation system=====
At runtime, the system looks in the $KDEDIR/share/locale/$KDE_LANG/LC_MESSAGES/rosegarden.mo file for strings that match the arguments to i18n and replaces them with the translated versions if available. See the developer.kde.org link above for repercussions with respect to translating #defines, etc.
+</del>
\ No newline at end of file
Modified: website/wiki/data/pages/dev/qt4_bug_tracker.txt
===================================================================
--- website/wiki/data/pages/dev/qt4_bug_tracker.txt 2009-05-04 02:45:03 UTC (rev 10245)
+++ website/wiki/data/pages/dev/qt4_bug_tracker.txt 2009-05-04 09:44:28 UTC (rev 10246)
@@ -1,143 +1,84 @@
-=====Rosegarden 09.04 (ha ha) Fake Bug Tracker=====
-We're going to try just using this wiki page as a tracker for now. To report a bug, just jot something down. To claim a bug, tack your initials after it in brackets, like [dmm] or [cc] or [jjjs]
-
+=====Rosegarden 09 Fake Bug Tracker=====
+We're just using this wiki page as a tracker for now. To report a bug, just jot something down, preferably at the top of the stack, using docuwiki numbered list syntax (like the existing examples.) To claim a bug, tack your initials after it in brackets, like [dmm] or [cc]
[[style_bugs|Style Bugs]] [dmm]
====Bugs====
- * TrackVUMeter has all the right bits to be showing the track number texts, but they never appear, stylesheet or no. I think it's due to the broken VUMeter class painting over them or something. I can't quite work this out. We could probably release without VU meters the way KDE 4.0 and 4.1 released without a working taskbar if we really had to, and replace them with plain QLabels, but I figure this whole project looks like a nice bit of work for one of you looking for something small but important to do.
-
- * VU meters are broken because they're of a highly Qt3-dependent design. VUMeter <= QLabel <= QFrame, and QFrame used to have drawContents() and drawFrame(). We are apparently getting a working drawFrame() in here from having Qt3-compatibility mode on, but drawContents() is gone.
-
-Porting guide says:
-<code>QFrame used to have drawFrame(QPainter *) and drawContents(QPainter *) virtual functions. These are now gone. In Qt 4, the frame is drawn by the QFrame::paintEvent() function. If you want to change the way QFrame paints itself, reimplement this function. To draw the contents of the frame, reimplement QFrame:paintEvent() and call the base class implementation of the function before you use the contentsRect() function inherited from QWidget, to retrieve the rectangle to paint on.</code>
-
-I tried a quick go at something like that, didn't get anywhere, and set it aside. I'm thinking this whole thing could probably use a total rethink if someone would like to play with it. Do a new implementation, make it look cool, and fix it in the process.
-
- * right click assignment menus were QPopupMenu. Emanuel got this tweaked implementation off the ground, then dropped the ball. [er]
-
- * if two copies of RG are started, the second one is unable to connect to JACK. Chris says we can sort this out and what needs fixing in an email I've misplaced.
-
- * crash after successful looking audio recording
-<code>
-#0 0xb742d4aa in QWidgetPrivate::clipRect () from /usr/lib/libQtGui.so.4
-#1 0xb742d7c2 in QWidget::repaint () from /usr/lib/libQtGui.so.4
-#2 0x0814403f in Rosegarden::RosegardenGUIDoc::slotUpdateAllViews (this=0x8c3a4c0, sender=0x0) at src/document/RosegardenGUIDoc.cpp:235
-#3 0x0814484d in Rosegarden::RosegardenGUIDoc::finalizeAudioFile (this=0x8c3a4c0, iid=1000) at src/document/RosegardenGUIDoc.cpp:2773
-#4 0x084aa633 in Rosegarden::SequenceManager::processAsynchronousMidi (this=0x8dffb68, mC=@0xbfcd6ec8, audioManagerDialog=0x0)
- at src/gui/seqmanager/SequenceManager.cpp:934
-#5 0x082d0c39 in Rosegarden::RosegardenGUIApp::slotCheckTransportStatus (this=0x8b4c300) at src/gui/application/RosegardenGUIApp.cpp:3954
-#6 0x082f3ee9 in Rosegarden::RosegardenGUIApp::qt_metacall (this=0x8b4c300, _c=QMetaObject::InvokeMetaMethod, _id=216, _a=0xbfcd7008)
- at src/gui/application/RosegardenGUIApp.moc:697
-#7 0xb7073f79 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
-#8 0xb7074642 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
-#9 0xb70b1817 in QTimer::timeout () from /usr/lib/libQtCore.so.4
-#10 0xb707b0fe in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
-#11 0xb706e9fa in QObject::event () from /usr/lib/libQtCore.so.4
-#12 0xb73dff9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
-#13 0xb73e4bf9 in QApplication::notify () from /usr/lib/libQtGui.so.4
-#14 0xb705f0b9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
-#15 0xb708cc01 in ?? () from /usr/lib/libQtCore.so.4
-#16 0xb708a4a0 in ?? () from /usr/lib/libQtCore.so.4
-#17 0xb681bcc6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
-#18 0xb681f083 in ?? () from /usr/lib/libglib-2.0.so.0
-#19 0xb681f63e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
-#20 0xb708a9f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
-#21 0xb7473a25 in ?? () from /usr/lib/libQtGui.so.4
-#22 0xb705e33d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
-#23 0xb705e4cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
-#24 0xb706074d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
-#25 0xb73df897 in QApplication::exec () from /usr/lib/libQtGui.so.4
-#26 0x082bc3ef in main (argc=1, argv=0xbfcd7b44) at src/gui/application/main.cpp:760
-</code>
-
- * changing the grid size in the matrix randomly results in some insane number being written out to Rosegarden.conf. Subsequent matrix starts crash on this insane number. (Uninitialized variable maybe? Some problem with QVariant? I looked at the static_cast<unsigned long long> for Rosegarden::timeT, but this doesn't seem in of itself to be the culprit) [dmm]
-
- * The notation editor core dumps on an empty segment [rev 9704] [[notation_crash_discussion]]
-
- * Undo/redo buttons don't appear properly on toolbar [cc]
-
- * Notation garbled, and generally all sorts of problems there beyond the scope of this page [cc]
-
- * Configure dialog contains tab widget inside a tab widget, which is a definite no. It needs to look more like the old one. [NOTE: Michael has working sample code for creating a similar widget and everything, but is still waiting on someone to [[help_with_config_page|help]] him understand how to solve one underlying problem that's throwing a spanner in the entire works]
- * Configure dialog buttons (across the bottom) have no labels and don't work
-
- * Progress dialogs generally don't work (I have yet to see a working progress bar inside one, although I did get a working progress bar _outside_ the dialog on audio file import)
-
- * Lilypond export progress dialog never disappears, RG seems to think it has never completed -- I suspect this means we aren't getting feedback from the lilypond export process properly? Pity, because we took a bit of care over that one I think (dmm - when I try "preview with LilyPond" Rosegarden just becomes totally unresponsive, and has to be killed, though it never stops repainting itself, and doesn't look hung. No LilyPond anything ever takes place, or takes place too fast to catch with ps.) (Lilypond preview does actually work for me --cc)
-
- * File dialogs generally need a bit of care and attention to make sure previous paths per file type are used, etc. [hjj]
-
- * File dialog doesn't know where to find example files (and neither do I, actually) (unlike many resources, examples will probably want to be installed -- and they will be installed at /usr/share/rosegarden/examples I think -- but you're right that the dialog doesn't know that --cc) [cc]
-
- * File -> Close from e.g. notation window crashes the application
-
- * In Manage Metronome dialog, the pitch chooser doesn't show a note on a little staff. (may be related to general notation view brokenness --cc) (staff and clef are visible again, but no note yet [rev. 9758] --yg)
-
- * Main composition view doesn't scroll correctly -- if I use Select tool to drag "off the top", the whole widget containing the composition view moves down! It's very weird. (yes, very, very weird -dmm) [cjf]
-
- * Rosegarden rotary widgets drawn with incorrect colors or something. They look off. [dmm -- the backgrounds are fixed with the new styling work, and the rest of this will fall under the umbrella of changes I'm making in that process. I'm probably going to tweak the colors users can pick from for the knobs, so they coordinate better, and along the way I'm going to try to address this drawing problem, which seems to have something to do with drawing on white instead of on the expected background color.]
-
-====Bugs that were listed above, now fixed====
- * save after previous successful save fails with [hjj]
-
- * after saving file "test" then modifying it, the main window title is "test*.rg" Should probably be "test.rg*" I imagine. Oh, nevermind, I thought that was the "document is modified" renaming I seem to remember, but in fact it's just "*.rg" added to the end of the file, and it's actually trying to write "test*.rg" to disk, so it fails. [dmm]
-
- * File dialog doesn't seem to know about .rgd or .rgp files, and defaults to * instead of *.rg [hjj]
-
- * No File -> New on main window File menu [hjj]
-
- * File -> Save As, save to eg. /tmp/foo.rg leads to dialog "This is not a local file." [dmm]
- * the other error about "not local filesystem" or whatever [dmm] (Commented out code poorly adapted from KURL::isLocalFile() that was originally supposed to determine that the file was free of any protocols etc. I'm not sure if this matters, and I'm sure it matters less than just being able to save a damn file at all, so this will certainly do for now.)
- * all saving fails with either the "failed to rename temporary output file" error or the, um, [dmm]
-
- * Parameter area in main view lacks scrollbar (just disappears off the bottom) (and needs a horizontal scrollbar or an enforced minimum size too (I vote scrollbar) (I vote no horiz scrollbar, but more work to make it less stupidly wide --cc) (looking much better now though!) (the current behavior seems great now... it's minimum sized by default, and you can't stupidly make it wider than it needs to be, but you **do** have the option to make it less wide if you want to, and you get a horizontal scrollbar then, and only then. Best of all possible words, I think. Calling it fixed -dmm)
-
- * Ticks on ruler don't have dark gray background [fixed by CJ I guess; rulers top and bottom look normal now]
-
- * Currently selected track has white foreground, but background does not become dark blue [dmm] [fixed with caveats; this solution really isn't stylesheet compatible, and I'm uncertain how to make it so]
-
- * The transport dialog disappears when the mouse goes outside of the main window. [[dev:transport_focus]] [dmm]
- * the transport dialog disappears when the matrix is open, [[dev:transport_focus]] [dmm]
-
- * Main window zoom slider is completely trashed, garbled, and apparently dysfunctional [not sure who fixed this, but the default toolbar layout is also fixed now -dmm]
+ - The backend export/print to LilyPond stuff generates J*.ly or T*.ly in . instead of /tmp/somewhere. This used to be /tmp/kde/my_user or something like that, probably from KDE. We should probably do something similar, like /tmp/my_user or something, and ensure that this gets passed into, eg. LilyPondProcessor with the full path intact. Noting for later but not endeavoring to do anything about this just now. Oh, also these temp files need cleaned up when we're done!
+ - Currently no playback devices exist out of the box. If I create one and connect it to something, Rosegarden never receives any MIDI from this device. We didn't expose record devices to QJackCtl's MIDI connection manager in 1.7.3, and still don't now, so it makes it hard to diagnose exactly where the breakdown is occurring here. The key debug traces seem to be: "Creating device 3 in Record mode -- no connection available Default device name for this device is Anonymous MIDI device 2 [seqman] CreateDeviceCommand::execute - added device 3" and then after I have connected the new device explicitly "ReconnectDeviceCommand::execute - reconnected device 3 to "20:1 UM-2 MIDI 2 (duplex)" but I never receive anything, and haven't been able to figure out where the breakdown is. This one is a pretty serious showstopper, with MIDI recording being something somewhat important and all.
+ - When tracking playback, the new matrix panner zoom box thingie sticks to the bottom of the panner. If you move it up to where the music you want to follow resides, it always jumps back down to the bottom almost instantly. This is true with Qt 4.5 as well.
+ - Transport toolbar buttons in the matrix aren't connected to anything (and this is quite a little project, actually)
+ - Hovering over or doing anything with the segment canvas or track buttons causes thousands of Qt painter errors. These don't actually seem to hurt anything, but they're seriously getting on my nerves whenever I forget to run with 2>&1|grep -v paint to filter all this garbage out.
+ - Matrix, draw an event, double click to open the simple event editor. Change something, and hit OK. Boom! I looked into this one, but what's going on in here is too subtle for a quick glance, and somebody needs to spend some time tracing around and working this out. It's crashing in Rosegarden::ViewElement::event (this=0x0) at src/base/ViewElement.h:43 from Rosegarden::MatrixSelector::handleMouseRelease (this=0x9589fe0, e=0xbfcba580)
+ - tricky to sort and get this one right, a ton of things aren't setting the document to modified, so it is possible to close with no protest after making extensive edits and accidentally clicking the wrong window button... hopefully/maybe they all have some simple common root
+ - segment previews are at least a pixel too thick (and this seems to echo other drawing problems I've already dealt with where the correct maximum size for such and such was ''theOldQt3Value - 1'')
+ - adding an audio file from the audio file manager causes some kind of paint event feedback loop, and ultimately leaves the GUI hung and unusable and/or crashes (this one is rather tricky... slotInsert() or whatever in the audio file manager dialog emits the signal insertAudioSegment() which RosegardenMainWindow is supposed to catch and send to RosegardenMainViewWidget::slotAddAudioSegmentDefaultPosition() to do the actual business. That slot never fires, and it actually seems like if I grep -v out the painter errors, there is no feedback loop, and it's a simple matter of nothing ever happening at all. Don't grep out the errors, and it effectively kills the application, though it never crashes. I'm just not at all sure what any of that strangeness is about, but it doesn't look very easy to root out and fix at all. I'm hoping whatever the solution is to the 10 billion track-related painter errors will turn out to be common to this one, but there's still some underlying breakage here that's rather mysterious indeed.)
+ - the long pause between black screen and the splash image showing up is getting on my nerves... must find some way to fix this... delay showing anything until the resource is secured and ready or something
+ - if two copies of RG are started, the second one is unable to connect to JACK. Chris says we can sort this out and what needs fixing in an email I've misplaced.
+ - changing the grid size in the matrix randomly results in some insane number being written out to Rosegarden.conf. Subsequent matrix starts crash on this insane number. (Uninitialized variable maybe? Some problem with QVariant? I looked at the static_cast<unsigned long long> for Rosegarden::timeT, but this doesn't seem in of itself to be the culprit) [dmm]
+ - Notation garbled, and generally all sorts of problems there beyond the scope of this page [cc]
+ - Progress dialogs generally don't work (I have yet to see a working progress bar inside one, although I did get a working progress bar _outside_ the dialog on audio file import)
+ - Lilypond export progress dialog never disappears, RG seems to think it has never completed -- I suspect this means we aren't getting feedback from the lilypond export process properly? Pity, because we took a bit of care over that one I think (dmm - when I try "preview with LilyPond" Rosegarden just becomes totally unresponsive, and has to be killed, though it never stops repainting itself, and doesn't look hung. No LilyPond anything ever takes place, or takes place too fast to catch with ps.) (Lilypond preview does actually work for me --cc)
+ - File dialogs generally need a bit of care and attention to make sure previous paths per file type are used, etc. [hjj]
+ - File dialog doesn't know where to find example files (and neither do I, actually) (unlike many resources, examples will probably want to be installed -- and they will be installed at /usr/share/rosegarden/examples I think -- but you're right that the dialog doesn't know that --cc) [cc]
+ - File -> Close crashes the application in ''src/document/RosegardenDocument.cpp:196'' though I have not been able to determine why or write successful code to trap the bad condition and avert the crash. I seem to be able to trigger the crash by loading some file, modifying it until it finally gets the modified flag set (see bug above) and then File -> Close from the main window. It always crashes in the same place, but I don't understand what's really all coming together there at that line of code, so I can't do much else with this one. *view is not coming in null, and m_editViewList is not empty. I guess *view is pointing somewhere it shouldn't be.
+ - Vertical autoscroll in matrix is much too fast (tricky one this, because there is currently no distinction between horizontal and vertical autoscroll -- both are implemented at the same time through a delayed call to ensureVisible on the cursor position -- the reason vertical scroll is too fast is presumably just that the vertical distances involved are shorter)
+ - The select tool in the matrix does not work the first time the view is opened -- if you open a matrix view on an existing segment with notes in it already, it's supposed to have an active select tool, but I have to switch to another tool and back again before it does anything. Just at the moment I have no idea why this is the case, so all investigations welcome.
+ - I'm seeing a repaint loop on the text float over the main window's tempo ruler. The text float flickers on and off constantly while the mouse is held over the ruler widget. [I can't repeat this one Chris with either version of Qt I have installed.]
-
- * The percussion matrix editor layout is comically borked in innumerable ways; just look at it (dmm - looks more or less OK now, certainly in the ballpark; not sure who fixed this)
-
- * The regular matrix core dumps on an empty segment [rev 9704] (dmm - no longer true; not sure who fixed this)
-
- * I have yet to get the new RG to actually _play_ anything (though the pointer will move) [cc] [I get noise out of my emu10k1!! nothing else yet though]
-
- * The main window is "Untitled" instead of calling itself "Rosegarden" or something. The "Untitled" might be correct for the name of the current document, in which case the application name is simply missing from the title bar. Investigating... [dmm]
-
- * Minimum draggable height of main window exceeds 945 px., which is too tall for a 1050 px. high screen with a large KDE panel, and surely much too large for 1280x800/1024x768/etc. [fixed by cc, dmm thinks]
-
-
- * Main window load presets was failing due to legacy slotOk() from KDialogBase -> QDialog conversion. Fixed by changing to use overridden accept() instead. Changed throughout code, hopefully all cases are solved now. [dmm]
-
- * Transport dialog buttons don't work
-
- * Manage MIDI Devices crashes
-
- * Time sig dialog "big buttons" lack icons
-
- * The bit of the transport window that normally shows the current time in the format of choice is empty (it does actually show the numbers when non-zero, it's just missing the default zeroes and punctuation. I think they just need loading in Designer --cc)
-
- * Notation editor doesn't set a default tool, so crashes when you move mouse over it unless you can select a tool first [cc]
-
- * GUI is very slow altogether -- it appears to be stuck in a continuous repaint loop
-
- * The transport window "show additional controls" icon is missing.
-
- * When playing (trying to play), the transport shows junk like "D#(I18N_ARGU" instead of the octave number [fixed by hjj]
-
- * The event list editor has some weird "<numintg>1</numintg>" nonsense in its title (in fact this appears everywhere a %1-parameter argument goes into an i18n() string I think -- cc) [fixed by hjj]
-
- * Studio -> Manage Metronome crashes the application.
-
- * QDeferScrollView implementations (e.g. track buttons) do not scroll with the canvas as they are intended to
-
- * Event list editor scrolls very slowly. I wonder if this is a tree widget when it should be some sort of list widget? Was there some issue like the new tree widget was the only thing that closely matched the old list widget, or something? I can't remember and I didn't handle this conversion, but I do know that lists using e.g. QTableView in other Qt4 applications scroll much faster than this (dmm - Fixed? I tested with a fairly long segment, and it scrolls very fast here.) (yes, I think this was a side-effect of the general gui repaint loop problem --cc)
-
- * Quick marker functions absent from Composition menu
-
- * Fader widgets don't update while sliding up and down. Update only happens after letting go. Float is several hundred pixels away from the widget being manipulated, and usually way outside of the Rosegarden window space.
+====Bugs that were listed above, now fixed====
+ - doc properties setting audio path file dialog comes up with "file dialog" in the "type text here" box. That's odd. (The whole bit with how I struggled to remember how to set this makes me think we really should make the audio path more readily accessible too.)
+ - When there is too much tracks to fit vertically into the segment canvas window, rolling down then up the mouse wheel on this segment canvas hides everything on it. [This is the Qt 4.5 raster graphics "scrubbing problem." The interim solution is to pass ''-graphicssystem native'' on the command line. Chris and I are debating whether to keep this and fix it or optimize the code for better performance using the slower vector engine. The change causes other bad side effects too, but I won't enumerate them here.] [fixed by ifdeffing out the QApplication::setGraphicsSystem call, and reverting to native rendering in all cases; I took this decision after noticing that the raster graphics system caused problems drawing the LEDs as well... too many problems on top of problems, and I doubt it's worth pursuing further, though I left the code there in case it is.]
+ - Undo/redo buttons don't appear properly on toolbar [cc] **(This one is really starting to annoy the Official Project Stylemeister)**
+ - Initial "Open" file dialog (from e.g. Open button on toolbar) only shows Rosegarden files by default; it used to show both RG and MIDI files and I think it should do so. (Actually it used to show RG2.1 files as well -- I don't care about that.) [dmm -- skipped RG2.1 files]
+ - Configure dialog buttons (across the bottom) have no labels and don't work [not sure what this was about, but I guess CJ fixed it?]
+ - The "file type" dropdown in the file dialog is unreadable -- some style problem? See [[http://www.rosegardenmusic.com/wiki/_media/dev:regression-filedlg-dropdown.png|screenshot]] [dmm - this one was ugly; apparently a bug in Qt 4.5 as far as I can tell, because with a simple application stylesheet consisting **only** of a few lines of pasted sample code from the Qt website, all combo boxes in our application take scrollbars, even if there are only two items. I can't repeat this outside Rosegarden to file a bug against Qt, but whatever witch's brew of random variables is causing this to manifest is nothing we're doing wrong per se. It's most likely due to Qt3-support, I hazard, but haven't been able to prove that. Anyway, I addressed the issue by ensuring that the unwanted scrollbars would at least be small enough to function, even though they look ridiculously stupid, and I wish I could make them go away.]
+ - controller editor: add a controller, and unless you change the color by hand, it always comes out "default" even when it's hacked to actually default to something other than default; some missing plumbing there[dmm]
+ - just hack the damn rotary drawing code to work around this color map passing around default color bug, because I can't figure it out, and it's not worth more time[dmm]
+ - File Save and picking a new name saves file as "newname.rg *.RG" [dmm - fixed along with the new template bit]
+ - Controller editor dialog had a color index bug for years [dmm]
+ - Controller editor dialog did not allow editing of existing controllers due to broken signal [dmm]
+ - Controller editor dialog layout problems [dmm]
+ - **SERIOUS MATRIX SELECTION BUG**! Draw, say, four events in the matrix. Sweep select them. Now shift click on one of the events. What's supposed to happen is that if an event is already part of the selection, that event gets removed from the selection. The selection part of this seems to be working properly, but there is a **SERIOUS** glitch. Every time you shift-click an event that's already part of a selection, all the events that remain in the selection **MOVE** in time. [Chris apparently just fixed this in rev. 10143, though I'm not sure if he fixed it by design, or as a convenient side effect.]
+ - crash after successful looking audio recording [dmm]
+ - The notation editor core dumps on an empty segment [rev 9704] [[notation_crash_discussion]] [although it is light years away from becoming a notation editor again, or at least appears so from the surface]
+ - In Manage Metronome dialog, the pitch chooser doesn't show a note on a little staff. (may be related to general notation view brokenness --cc) (staff and clef are visible again, but no note yet [rev. 9758] --yg)
+ - something's off with whatever keeps various rotaries in sync. If I open the MIDI mixer and tweak the pan control, the knob in the MIDI IPB keeps in step, but this doesn't work for any other knob. [CJ]
+ - right click assignment menus were QPopupMenu. Emanuel got this tweaked implementation off the ground, then dropped the ball. [CJ]
+ - Main composition view doesn't scroll correctly -- if I use Select tool to drag "off the top", the whole widget containing the composition view moves down! It's very weird. (yes, very, very weird -dmm) [cjf]
+ - Rosegarden rotary widgets drawn with incorrect colors or something. They look off. [dmm -- the backgrounds are fixed with the new styling work, and the rest of this will fall under the umbrella of changes I'm making in that process. I'm probably going to tweak the colors users can pick from for the knobs, so they coordinate better, and along the way I'm going to try to address this drawing problem, which seems to have something to do with drawing on white instead of on the expected background color.]
+ - Trying to change tabs on the MIDI mixer crashes
+ - Configure dialog contains tab widget inside a tab widget, which is a definite no.[CJF]
+ - The AudioPluginManager dialog was catastrophically broken. Now it's greatly fixed. No more serious layout problems, and it shows all the controls for plugins. It looks OK with style too. [dmm]
+ - TrackVUMeter has all the right bits to be showing the track number texts, but they never appear, [CJF fixed the big problem, and is supposed to be working on tweaking the little problem]
+ - save after previous successful save fails with [hjj]
+ - after saving file "test" then modifying it, the main window title is "test*.rg" Should probably be "test.rg*" I imagine. Oh, nevermind, I thought that was the "document is modified" renaming I seem to remember, but in fact it's just "*.rg" added to the end of the file, and it's actually trying to write "test*.rg" to disk, so it fails. [dmm]
+ - File dialog doesn't seem to know about .rgd or .rgp files, and defaults to * instead of *.rg [hjj]
+ - No File -> New on main window File menu [hjj]
+ - File -> Save As, save to eg. /tmp/foo.rg leads to dialog "This is not a local file." [dmm]
+ - the other error about "not local filesystem" or whatever [dmm] (Commented out code poorly adapted from KURL::isLocalFile() that was originally supposed to determine that the file was free of any protocols etc. I'm not sure if this matters, and I'm sure it matters less than just being able to save a damn file at all, so this will certainly do for now.)
+ - all saving fails with either the "failed to rename temporary output file" error or the, um, [dmm]
+ - Parameter area in main view lacks scrollbar (just disappears off the bottom) (and needs a horizontal scrollbar or an enforced minimum size too (I vote scrollbar) (I vote no horiz scrollbar, but more work to make it less stupidly wide --cc) (looking much better now though!) (the current behavior seems great now... it's minimum sized by default, and you can't stupidly make it wider than it needs to be, but you **do** have the option to make it less wide if you want to, and you get a horizontal scrollbar then, and only then. Best of all possible words, I think. Calling it fixed -dmm)
+ - Ticks on ruler don't have dark gray background [fixed by CJ I guess; rulers top and bottom look normal now] [this is fixed with stylesheets now]
+ - Currently selected track has white foreground, but background does not become dark blue [dmm] [fixed with caveats; this solution really isn't stylesheet compatible, and I'm uncertain how to make it so] [it's fixed with spot stylesheets now]
+ - The transport dialog disappears when the mouse goes outside of the main window. [[dev:transport_focus]] [dmm]
+ - the transport dialog disappears when the matrix is open, [[dev:transport_focus]] [dmm]
+ - Main window zoom slider is completely trashed, garbled, and apparently dysfunctional [not sure who fixed this, but the default toolbar layout is also fixed now -dmm]
+ - The percussion matrix editor layout is comically borked in innumerable ways; just look at it (dmm - looks more or less OK now, certainly in the ballpark; not sure who fixed this)
+ - The regular matrix core dumps on an empty segment [rev 9704] (dmm - no longer true; not sure who fixed this)
+ - I have yet to get the new RG to actually _play_ anything (though the pointer will move) [cc] [I get noise out of my emu10k1!! nothing else yet though]
+ - The main window is "Untitled" instead of calling itself "Rosegarden" or something. The "Untitled" might be correct for the name of the current document, in which case the application name is simply missing from the title bar. Investigating... [dmm]
+ - Minimum draggable height of main window exceeds 945 px., which is too tall for a 1050 px. high screen with a large KDE panel, and surely much too large for 1280x800/1024x768/etc. [fixed by cc, dmm thinks]
+ - Main window load presets was failing due to legacy slotOk() from KDialogBase -> QDialog conversion. Fixed by changing to use overridden accept() instead. Changed throughout code, hopefully all cases are solved now. [dmm]
+ - Transport dialog buttons don't work
+ - Manage MIDI Devices crashes [totally rewritten by Emanuel and the new dialog tweaked somewhat by Michael]
+ - Time sig dialog "big buttons" lack icons
+ - The bit of the transport window that normally shows the current time in the format of choice is empty (it does actually show the numbers when non-zero, it's just missing the default zeroes and punctuation. I think they just need loading in Designer --cc)
+ - Notation editor doesn't set a default tool, so crashes when you move mouse over it unless you can select a tool first [cc]
+ - GUI is very slow altogether -- it appears to be stuck in a continuous repaint loop
+ - The transport window "show additional controls" icon is missing.
+ - When playing (trying to play), the transport shows junk like "D#(I18N_ARGU" instead of the octave number [fixed by hjj]
+ - The event list editor has some weird "<numintg>1</numintg>" nonsense in its title (in fact this appears everywhere a %1-parameter argument goes into an i18n() string I think -- cc) [fixed by hjj]
+ - Studio -> Manage Metronome crashes the application.
+ - QDeferScrollView implementations (e.g. track buttons) do not scroll with the canvas as they are intended to [fixed on canvas by CJ, fix pulled out into DeferScrollArea by Michael]
+ - Event list editor scrolls very slowly. I wonder if this is a tree widget when it should be some sort of list widget? Was there some issue like the new tree widget was the only thing that closely matched the old list widget, or something? I can't remember and I didn't handle this conversion, but I do know that lists using e.g. QTableView in other Qt4 applications scroll much faster than this (dmm - Fixed? I tested with a fairly long segment, and it scrolls very fast here.) (yes, I think this was a side-effect of the general gui repaint loop problem --cc)
+ - Quick marker functions absent from Composition menu
+ - Fader widgets don't update while sliding up and down. Update only happens after letting go. Float is several hundred pixels away from the widget being manipulated, and usually way outside of the Rosegarden window space.
\ No newline at end of file
Modified: website/wiki/data/pages/dev/slog_endgame.txt
===================================================================
--- website/wiki/data/pages/dev/slog_endgame.txt 2009-05-04 02:45:03 UTC (rev 10245)
+++ website/wiki/data/pages/dev/slog_endgame.txt 2009-05-04 09:44:28 UTC (rev 10246)
@@ -6,9 +6,9 @@
===== Working environment =====
-Here's how to check out, update, and test-build the "qt4" branch.
+Here's how to check out, update, and test-build the Qt4 port. Note that **this code is now in the Subversion trunk**, it is no longer a separate branch. (The old, stable code is the separate branch now.)
-First you'll need the Qt4 and KDE4 headers. On Ubuntu 8.04 this one line seems to be enough:
+First you'll need the Qt4 and KDE4 headers. On Ubuntu this one line seems to be enough:
<code>
$ sudo apt-get install kdelibs5-dev
@@ -19,14 +19,18 @@
Then,
<code>
- $ svn co https://rosegarden.svn.sourceforge.net/svnroot/rosegarden/branches/qt4
- $ cd qt4
- $ make -f qt4-makefile
+ $ svn co https://rosegarden.svn.sourceforge.net/svnroot/rosegarden/trunk/rosegarden
+ $ cd rosegarden
+ $ sh ./bootstrap.sh
+ $ ./configure
+ $ make
$ ./rosegarden
</code>
-If that fails catastrophically, you probably need to edit qt4-makefile to adjust it to your environment. Our CMake-based build system is still broken, though it will work eventually. There is no need to install anything, as it is all encapsulated in the one rosegarden binary.
+If that fails catastrophically, you probably need to edit the Makefile to adjust it to your environment. For the old KDE3 codebase we used a comprehensive CMake-based build system; this has never (yet) been converted to the new code, so we are testing a simpler autoconf configuration instead. It should work, but it's not guaranteed. If you find fixable problems, please report them to the -devel list.
+There is no need to install anything, as it is all encapsulated in the one rosegarden binary.
+
===== Bug tracker =====
We're not going to start using the SourceForge tracker to keep track of things until later in the process. Instead, we've got this handy dandy [[dev:qt4_bug_tracker|Tracker Page]]
\ No newline at end of file
Modified: website/wiki/data/pages/dev/style_bugs.txt
===================================================================
--- website/wiki/data/pages/dev/style_bugs.txt 2009-05-04 02:45:03 UTC (rev 10245)
+++ website/wiki/data/pages/dev/style_bugs.txt 2009-05-04 09:44:28 UTC (rev 10246)
@@ -1,33 +1,31 @@
+[[dev:regression_snapshots]]
====== Style Bugs ======
-It's time to start a list of things somewhere so I can keep track of everything left to do in the ongoing style work.
-
-I wouldn't mind help with certain tasks at this point, but I've established my vision for how this is going to go, and I've put the --LONG-- hours into making it happen, so I hold the veto pen, and nothing should get done without it going across my desk first.
-
===== Outstanding Issues =====
- - Rotaries are still in a grizzly state
- - Toolbar tooltips still have the wrong colors [NOTE: this is my KDE default background color, and it has proven very sticky to get rid of so far. Nothing worked.]
- I disabled the JACK warning dialog, and I need to rewrite it with a don't show button. I forget how I need to do that, but it looked somewhat complicated, which is why I skipped it at the time. Something about QSomething::addCustomButtonSomethingOrOther and then plumbing that all to some backend to make it work. I should do that, or at least remember the dialog is broken. For now, screw JACK. I've been getting a thousand xruns a day lately, and I'm tired of looking at the stupid red icon anyway.
- - Audio mixer quite miserable, but these are code bugs now. "Master" in the wrong place. The void below should be buttons for plugins, but they don't show up sans stylesheet either.
- - MIDI mixer appears superficially functional except for the faders, but very bland like a dialog suffering from QWidget underspecificity inhertiance glee overload, and probably needs TLC in the style file
- - Comp -> Start and end sizing problem. [and currently: crashing problem at doc->getEndMarker() or similar]
- - The new device manager is really very dreadful in this scheme due to style bugs on the one hand, and due to problems with things that are actually working correctly, like the groupbox backgrounds. This one needs serious attention, but it's probably pointless until it settles down. Improve it some, surely, but don't bother trying to get it perfect yet. (Not really possible. It has to be styled from the .ui file, because Designer wants to give _1 _2 _3 names to named objects of the same name, and because naming the objects didn't even work on the first one.)
+ - Progress dialogs are coming out solid black. Progress dialogs are still broken to the point where they're random and useless, so I haven't bothered to try to iron this out at all. I haven't tried to style the actual progress bars themselves yet either, but that needs to be done eventually.
+===== Fixed Issues =====
+ - checkbox and radio button disabled states
+ - IGNORED: I'm still thinking about getting rid of the metadata editor table thingie, but if we keep it, it still has one thorny style problem. We need to replace QLineEdit with the subclass (and possibly convert the subclass into a re-implementation like QInputDialog) LineEdit in this table to make the colors work out right when you edit an item. It's currently awful. Fixing it looks very possible, by changing with "delegate" QTableWidget uses for these items, but it looks like hours of reading to fix something I never use and would be happy to see deleted, so I am sticking this down way down at the bottom of my TODO list.
+ - The new device manager is really very dreadful in this scheme, but the whole thing is pretty much in need of serious attention anyway, so I'm intending to finish what Emanuel just wandered away from and left abandoned in the dirt, to turn it into something usable, with style fixes along the way)
+ - Matrix IPB no longer exists, and should stay that way
+ - Matrix piano keyboard is inverted
+ - Menu fonts look like total ass on my system. [actually, it was the default "disabled" effect]
+ - audio route menus in mixer are QWidget #404040 hack gray, but take other properties from QMenu style, so they're quite illegible. Haven't resolved that one yet
+ - on the MIDI mixer, the tab thingie has funky looking buttons that look like something out of sample code, though I don't remember styling anything like this [not sample code, un-styled, similar to the weirdly too large arrows on the header views before I figured out how to override that]
+ - Rotaries are still in a grizzly state [no longer!]
+ - rotary colors all look ridiculous in this scheme, and they need a makeover (on top of fixing the horrible white circles) [changed my mind about this one]
+ - Toolbar tooltips still have the wrong colors [NOTE: this is my KDE default background color, and it has proven very sticky to get rid of so far. Nothing worked.]
+ - Comp -> Start and end sizing problem. [and currently: crashing problem at doc->getEndMarker() or similar] [though this dialog could use a makeover to look more like other dialogs... took a quick look, and it's a bit more work than it's worth to me right now]
- VUMeters aren't working properly, and most particularly their numbers are never showing up. [CJ agreed to come to my rescue again on this one. Long live Chris Fryer. Hip hip hooray!]
- - Menu fonts look like total ass on my system. Bold fonts are not bold, but drawn twice in a "ghost" mode that looks like channel 13 when I was a kid. Which Spiderman is the real Spiderman? No other Qt4 apps seem to have this problem, and we don't have this problem, or it isn't nearly so visible, unless the background for the menu bar is black. Could be us, could be Qt. Needs research with an eye toward improving if possible, so I don't wind up taking a ton of crappy looking pixmaps for tutorials.
+ - MIDI mixer style problems are due to tab whatever that is style problems
- The spinboxes still remain to be styled at all, and need pixmaps [now they're styled, and behaving reasonably, but I haven't styled them for real yet]
- - The matrix is going to need a big makeover, but I'm afraid to touch it until after the qt4-graphicsview merge. Issues that exist now:
- - Matrix group boxes don't have the same scheme as RosegardenParameterArea and most (one might hope all, but probably not) of the dialogs. [NOTE: This is because the matrix IPB goes directly into the QDockWidget instead of a QGroupBox. Plan is to put a GroupBox into the layout, and also turn these off by default so they don't appear unless asked for, then we'll see who notices]
- - Matrix piano keyboard is inverted (probably need to fix this with painter. contemplate ripping off the look of LMMS which has an awesome looking keyboard)
- - The notation editor is probably an even bigger makeover that, again, I'm afraid to touch at this time. Issues to watch out for though:
- - I like the toolbar handle I've got better than anything else I came up with, but it's only suitable for horizontal toolbars. I can't discover any way to specify an alternate handle for vertical toolbars in the stylesheet. If this exists, it isn't documented anywhere, or it's deeply buried in googlespace. This problem will need to be solved, or else the handles have to go in favor of something more ugly and more workable. I have some kind of :top :bottom / :left :right thing in the...
[truncated message content] |
