Why do Dolphin 5.1.4 menus seem to "roll-out" in a stilted, two-step way?
There is a brief pause after part of the menu is drawn; then the rest is suddenly drawn. I don't see this in my other apps. I'm running WinXP Pro/SP2. Regards, Shaping |
Shaping wrote:
> Why do Dolphin 5.1.4 menus seem to "roll-out" in a stilted, two-step way? > There is a brief pause after part of the menu is drawn; then the rest is > suddenly drawn. I don't see this in my other apps. I'm running WinXP > Pro/SP2. Maybe some unpleasant interaction with XP's "marvellous" slow menus ? I'm running XP Pro with all the respond-to-user-input-as-slowly-as-possible options turned off, and I see no such problem. I'm pretty sensitive to slow responses (I get bothered by slowness that I know some people can't detect), but Dolphin's menu's are all OK for me. The are /marginally/ slower than they could be, but nowhere near as slow as, say, the menus in Mozilla Firebird (which I find only /just/ bearable). Can you give a specific example of a "stuttering" menu from the system tools ? -- chris |
Chris,
>>Why do Dolphin 5.1.4 menus seem to "roll-out" in a stilted, two-step way? >>There is a brief pause after part of the menu is drawn; then the rest is >>suddenly drawn. I don't see this in my other apps. I'm running WinXP >>Pro/SP2. > > > Maybe some unpleasant interaction with XP's "marvellous" slow menus ? It would not surprise me. I've seen screen scarring with IE, Exlorer, etc., (nothing Dolphin-based executed during the Windows session), with those things active (never on machines that I control) on win2k and XP. > I'm running XP Pro with all the respond-to-user-input-as-slowly-as-possible > options turned off, and I see no such problem. Same here, unless I have a lot of stuff running, and doing so not as intended. It's difficult to find machines slow enough to cause problems, but what hardware is involved? Any errant IDE extensions? It might be interesting to look at the process monitor in the offending image. Unless other processes have been explicitly forked, a healthy image will typically have five processes running: main, undertaker, finalizer, timing, idler. With a dialog open, there might be a second main here or there. If there are lots of processes that do not look familiar, that could be the problem. There also could be some zombie views causing trouble; a panic button press (on the system shell) might be in order. Have a good one, Bill -- Wilhelm K. Schwab, Ph.D. [hidden email] |
In reply to this post by Chris Uppal-3
> Maybe some unpleasant interaction with XP's "marvellous" slow menus ?
No, I have everything related to speed and resolution almost maxed out--the highest or next to highest setting in all cases. I might have missed something, but this doesn't look like the smoother aesthetic menus. It's a quick jump to a partially drawn menu (like the first one or two items), a pause of maybe 0.1 second, and then a quick jump to a fully drawn menu (the greater part of menu now appears). Goes to User Preferences and pop a context menu. > > I'm running XP Pro with all the > respond-to-user-input-as-slowly-as-possible > options turned off, and I see no such problem. > > I'm pretty sensitive to slow responses (I get bothered by slowness that I > know > some people can't detect) [...] Likewise, I slowly go numb if I must wait a few milliseconds more than I expect. Shaping |
In reply to this post by Schwab,Wilhelm K
Bill/Chris,
Indeed, I had the menu sliding enabled. I reinstalled XP recently, and never turned off this lovely /default/ feature. Thanks. Shaping "Bill Schwab" <[hidden email]> wrote in message news:ctbfp9$uo6$[hidden email]... > Chris, > >>>Why do Dolphin 5.1.4 menus seem to "roll-out" in a stilted, two-step way? >>>There is a brief pause after part of the menu is drawn; then the rest is >>>suddenly drawn. I don't see this in my other apps. I'm running WinXP >>>Pro/SP2. >> >> >> Maybe some unpleasant interaction with XP's "marvellous" slow menus ? > > It would not surprise me. I've seen screen scarring with IE, Exlorer, > etc., (nothing Dolphin-based executed during the Windows session), with > those things active (never on machines that I control) on win2k and XP. > > >> I'm running XP Pro with all the >> respond-to-user-input-as-slowly-as-possible >> options turned off, and I see no such problem. > > Same here, unless I have a lot of stuff running, and doing so not as > intended. It's difficult to find machines slow enough to cause problems, > but what hardware is involved? Any errant IDE extensions? > > It might be interesting to look at the process monitor in the offending > image. Unless other processes have been explicitly forked, a healthy > image will typically have five processes running: main, undertaker, > finalizer, timing, idler. With a dialog open, there might be a second > main here or there. If there are lots of processes that do not look > familiar, that could be the problem. There also could be some zombie > views causing trouble; a panic button press (on the system shell) might be > in order. > > Have a good one, > > Bill > > -- > Wilhelm K. Schwab, Ph.D. > [hidden email] |
Free forum by Nabble | Edit this page |