Bug 115171 - advanced button separate window
Summary: advanced button separate window
Status: RESOLVED NOT A BUG
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-27 03:49 UTC by Cassio
Modified: 2005-10-27 19:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cassio 2005-10-27 03:49:41 UTC
Version:           v0.8.3 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.6 (Debian 1:3.3.6-5)
OS:                Linux (i686) release 2.6.11.8

When opening separate download windows the window is
opened showing advanced features but the advanced
button is not pressed.
To close the advanced features is necessary to click 2
times the advanced button, one to really press it and
another to release it.
I personally sugest that the window do not show the
advanced options by default.

Thanks,

Cassio
Comment 1 Urs Wolfer 2005-10-27 19:14:24 UTC
I'm not sure what you exactly mean. Do you mean with advanced features timer and log? If yes, I cannot reproduce this behavior with the current version.
Comment 2 Cassio 2005-10-27 19:28:31 UTC
I mean...

In the kget main window, in that window I have 3 downloads running.
When I double-click one of the running downloads it opens a separate download window. In this window, there is an "advanced" button, wich opens and closes the "advanced panel" (the window is resized and TIMER and LOG apears).

The problem is: When this separate window opens it opens showing the advanced panel, but the advanced button is not pressed. So, if I want to close the panel, I have to click once in the button, to keep it pressed and click once more to in fact close the panel.
Once it's closed, its behavior turns back to normal.
Comment 3 Urs Wolfer 2005-10-27 19:37:40 UTC
Ok, thanks. But I cannot reproduce this behavior with the current version. You could try to update KGet.