Bug 293920

Summary: kturtle can't be docked
Product: [Applications] kturtle Reporter: Sang <sangtx00007>
Component: generalAssignee: KDE-Windows <kde-windows>
Status: CONFIRMED ---    
Severity: normal CC: cies
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sang 2012-02-12 18:15:16 UTC 
Version:           unspecified (using KDE 4.8.0) 
OS:                MS Windows

I can't dock kturlte's code editor again after undock it

Reproducible: Always

Steps to Reproduce:
I can't dock kturlte's code editor again after undock it


Expected Results:  
I can't dock kturlte's code editor again after undock it
Comment 1 Patrick Spendrin 2012-02-20 23:41:44 UTC 
Happens for all docks. This might be system independent. Very likely this is a junior job.
Comment 2 Sang 2012-02-21 15:04:45 UTC 
Yes, I it worked
Thanks for your reply
I want to use Kstep but I don't find it in installation package, I use Win7
Can you please help me ?
Thank you very much !

Sang

2012/2/21 Patrick Spendrin <ps_ml@gmx.de>

> https://bugs.kde.org/show_bug.cgi?id=293920
>
>
> Patrick Spendrin <ps_ml@gmx.de> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEW
>                 CC|                            |cies@kde.nl
>         AssignedTo|cies@kde.nl                 |kde-windows@kde.org
>     Ever Confirmed|0                           |1
>
>
>
>
> --- Comment #1 from Patrick Spendrin <ps_ml gmx de>  2012-02-20 23:41:44
> ---
> Happens for all docks. This might be system independent. Very likely this
> is a
> junior job.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 3 Justin Zobel 2021-03-10 00:32:46 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.