Bug 154551

The issues are much broader than problems with the analog clock. Indeed, these problems affect all applets.

resize and rotate both work fine.

Jason, maybe you use newer version, but when you rotate it, it moves a bit after you release LMB. And the border after rotation is bigger than the clock (much more). And the border is not rotated at all even it was shown as rotating (well, I think it is sane that it is not rotated, but it should not be shown as rotating).

I guess by "border" that you are referring to the applet handle. It being much bigger is just a symptom of it not being rotated with the applet.

The final position is where it should be with current subversion.

> It being much bigger is just a symptom of it not being rotated with the
> applet. 

Do you see it is bigger with your version?
 

Yes, I see it here too. If you imagine the clock is enclosed in a square, the size of the applet handle matches the size that the square would be when rotated.

the handle is not meant to be rotated with the applet.

Aaron, that's good, but then do not show it rotated. The bug exists because of UI -- either while rotating or after widget is rotated (reopening).

There is nothing to fix here. If the user drags, i.e. rotates the frame is rotated as well to show the difference between starting degree and current degree. Thus if you release the mouse-button the frame is reset to "not rotating" and starts at 0 if the user starts rotating again.

? It looks like the basic principles of design changed with KDE4 :-)
a) principle of the least surprise -- do not show user something you are not willing to do
b) WYSIWYG

The applet border is not supposed to be rotated so please do not rotate it. 

> to show the difference between starting degree and current degree

The final effect is what is count and currently KDE shows something that won't happen. So how the user can judge if she/he likes it or not if she/he cannot see it? Do you really think that user estimates degrees and says "oh, this is approximately 40 degrees so I stop here" or maybe user rather thinks "I like it THAT way".

Since the content (applet) only will be rotated please show only applet rotated. This way user will get what she/he sees -- WYSIWYG.

Applet and handles are two different things. The applet is shown rotated and is displayed rotated. The handles are not rotated and hence do not stay rotated, they are just an indicator _while_ rotating.

The handles are not showing all the time, so WYSIWYG does not apply at all anyway. If you use a manual screwdriver to rotate a screw, the screw stays rotated, yet your hand is reset to the original position before you rotate again. Unless you can twist your hand by more than 180°, which is rather unhealthy.

You want the handles to not be rotated, that's a wontfix, so please leave it at that. You want the handles to rotate and stay rotated, that's a misinterpretation of their use and purpose and hence a wontfix too.

> The handles are not rotated and hence do not stay rotated, they are just an
> indicator _while_ rotating. 

Indicator of...? (just in case: it is actually that hard to tell the applet is being rotated by looking at it?)

> You want the handles to not be rotated, 

Yes, handles + border. It serves no purpose and misinforms the users (compare it to for example Gimp, only what is rotated is being rotated, quite natural).

> If you use a manual screwdriver to rotate a screw, the screw stays rotated,
> yet your hand is reset to the original position before you rotate again.
> Unless you can twist your hand by more than 180°, which is rather unhealthy. 

Bad analogy. I can rotate applet, or image in gimp, several times around without realeasing the grip. And screwdriver is that much rotated as the screw (all the time), so you are comparing two completely different models.
 

PS. Border should be resized during resize/rotate of course. In other words:

Please show the applet with handles+border while resizing/rotating exactly like it will look after user stop rotating/resizing.

> Yes, handles + border. It serves no purpose and misinforms the users
> (compare it to for example Gimp, only what is rotated is being rotated,
> quite natural).


I did not know that the window around an image in Gimp disappears if one 
leaves it with the mouse-cursor, as the handles do -- I guess that handles 
and whatever sourrounds an image in gimp are not the same then, as stated 
before.

> > If you use a manual screwdriver to rotate a screw, the screw stays
> > rotated, yet your hand is reset to the original position before you
> > rotate again. Unless you can twist your hand by more than 180°, which is
> > rather unhealthy.
>
> Bad analogy. I can rotate applet, or image in gimp, several times around
> without realeasing the grip. And screwdriver is that much rotated as the
> screw (all the time), so you are comparing two completely different models.


Not at all, if you put the screwdriver back into the toolbox, i.e. release it 
from your hand as you do with the mouse-button and then take it out again for 
another rotation, its rotation has no relation the the rotation of the screw 
or how it was placed before putting it back into the toolbox -- as the 
handles.

> I guess that handles  and whatever sourrounds an image in gimp are not the
> same then, as stated  before. 

Nobody said that -- I just asked you to _compare_ it, i.e. the design. WYSIWYG. Plasma violates that principle.

>  Not at all, if you put the screwdriver back into the toolbox,

There is no analogy of it to applet handles. 

this is getting ridiculous. the whole thing isn't WYSIWYG anyways - the widget is rotated and scaled until the user lets go, and then it's properly resized, which often results in a rather different appearance.

Maciej, if you want the handle to not rotate as the widget is being rotated, write a patch. 
sven, you're not going to gain anything by arguing with him. go out and enjoy the snow or something :)

Try rectangular applets -- current behaviour is very untuitive since the border will be resized very differently to what the user sees.

Anyway, I am just a tester, not a user, so I close this -- no point of spending our time on this issue.