[ark] [Bug 391697] Ark does not invoke cursor status

2018-04-08 Thread Zakhar
https://bugs.kde.org/show_bug.cgi?id=391697 Zakhar changed: What|Removed |Added Resolution|--- |INVALID

[ark] [Bug 391697] Ark does not invoke cursor status

2018-03-18 Thread Zakhar
https://bugs.kde.org/show_bug.cgi?id=391697 --- Comment #6 from Zakhar --- Filed 391361 -- You are receiving this mail because: You are watching all bug changes.

[ark] [Bug 391697] Ark does not invoke cursor status

2018-03-18 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=391697 --- Comment #5 from Elvis Angelaccio --- (In reply to Zakhar from comment #4) > I would still insist for progress bar dialog > because it is the natural and most common implementation for such an > operation. Then please open

[ark] [Bug 391697] Ark does not invoke cursor status

2018-03-16 Thread Zakhar
https://bugs.kde.org/show_bug.cgi?id=391697 --- Comment #4 from Zakhar --- Task bar has a "highlighted" progress bar in which a cover is overlaid at some transparency level never the less it is a broken feature. Should task manager indicator be working, I would still

[ark] [Bug 391697] Ark does not invoke cursor status

2018-03-15 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=391697 --- Comment #3 from Elvis Angelaccio --- (In reply to Zakhar from comment #2) > Would be nice to have some sort of progess bar in its own dialog window, > currently only notifications area has progress bar available Hmm,

[ark] [Bug 391697] Ark does not invoke cursor status

2018-03-14 Thread Zakhar
https://bugs.kde.org/show_bug.cgi?id=391697 --- Comment #2 from Zakhar --- Would be nice to have some sort of progess bar in its own dialog window, currently only notifications area has progress bar available -- You are receiving this mail because: You are watching

[ark] [Bug 391697] Ark does not invoke cursor status

2018-03-11 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=391697 --- Comment #1 from Elvis Angelaccio --- When you extract from dolphin, the cursor is handled by dolphin. I think the current behavior is correct: the extraction is being performed by an external ark process, not by dolphin.