Fixed starting in taskbar under Win 7 when set to minimise to notification area.

[ribbons]

Original report from phil.tooley@gmail.com at 23:29:27 on 2011-04-21

Being able to start radio downloader when I start my computer is an extremely useful thing, thank you.

However it would be even better if it were possible to start minimised to the system tray (the bit by the clock - I am never certain of the correct name), to save having to do it manually upon every boot.

---

Imported from Bug 464 in the NerdoftheHerd.com Bugzilla.

[ribbons]

Original comment from Matt Robinson at 13:03:12 on 2011-04-22

So, just to check I've filled in the blanks correctly:

You are using Windows 7 and "Minimise to notification area instead of taskbar button on close" in the main options is checked?

Radio Downloader starts minimised to the taskbar on system startup instead of minimised to the "Notification area" (system tray)?

[ribbons]

Original comment from charlesrogersmk+bugzilla@gmail.com at 18:46:44 on 2011-04-23

This bug is also observed by me. (Ver0.20 of the Downloader, on Windows 7 Home Edition 64-bit). The "Minimise to notification area instead of taskbar button on close" in the main options is checked and Radio Downloader starts minimised to the taskbar on system startup instead of minimised to the system tray. When the application is restored, and then closed - it minimises to the system tray as required.

[ribbons]

Original comment from david.bugzilla@roru.co.uk at 12:10:18 on 2011-07-28

I have just upgraded from XP to Windows 7, and would point out that the behaviour under XP was that on startup RD minimised only to the system tray.

The behaviour under 7 is different, and is as described in this chain.

I love RD, have used it for years - thanks Matt - but am frustrated that I have to close it down on start up each time now that I am running W7.

Is there any chance of escalating this bug, so that "normal behaviour" (at least for me and the two others here) can be resumed as soon as possible?

[ribbons]

Original comment from Matt Robinson at 14:40:35 on 2011-07-29

Is there any chance of escalating this bug, so that "normal behaviour" (at least for me and the two others here) can be resumed as soon as possible?

Although it may be hard to believe, this bug is basically 'escalated', in that it has the next release set as the target milestone, and it is a bug rather than an enhancement. All being well, it will be fixed as part of the next release.

[ribbons]

Original comment from Matt Robinson at 20:03:22 on 2011-07-30

Fixed in 74c5af3 (one line code change ;-). This will be released as part of future version 0.22, which does not currently have a planned release date.