Michael Wiencek 24c80a4246 Try to solve UI freezes
Calling setCurrentIndex from currentChanged causes an infinite loop, breaking
the UI. But without that line, there are other very strange effects: see
PICARD-248. The only thing that currentChanged was added for was to make sure
the next item is selected after something is removed, so that keyboard
navigation is easier. This implements a new workaround for that without using
currentChanged.
2012-09-03 19:09:23 -05:00
2012-05-29 18:45:49 +02:00
2012-09-03 19:09:23 -05:00
2012-01-30 00:48:01 -06:00
2012-08-17 02:48:09 -05:00
2011-09-15 23:00:59 +02:00
2009-09-22 20:15:35 +02:00
2006-10-19 22:00:30 +02:00
2012-09-03 14:02:15 -05:00
2012-05-29 02:24:11 -05:00
Description
No description provided
82 MiB
Languages
Python 99.4%
Shell 0.3%
PowerShell 0.2%
C 0.1%