Significant IDE Code Editor Bug

General
1

Hey guys,

I’ve finally figured out how to duplicate an IDE bug that has occasionally happened to me but I’ve never been able to duplicate it at will until now.

1.) Go into an event for a control.
2.) Make sure there is more than one line of code in the event. Place the cursor insertion point on any line other than the first line.
3.) Move the mouse cursor into the header area at the top of the editor (where the name and parameters of the event are shown). The mouse cursor will be an arrow.
4.) Now slowly move the mouse cursor downwards until the mouse cursor changes to the insertion cursor (the one that looks like the cross section of a steel i beam).
5.) Now click the mouse
6.) Start typing. You will now change the text in the header line. You will also NOT get the insertion cursor in the code editor.

I can repeat this 100% in the IDE in OS X.

Here is the bug report:

<https://xojo.com/issue/33673>

I have photos and a movie of this behavior attached to the report.

The only way to get the proper name of the event back is to delete the event and re-add it.

Jon

2

Confirmed on OSX. Weird (and annoying if it were to happen)!

3

Trust me - it is annoying. This now becomes a new event in the control as well!

4

Props for holding a camera and using your computer at the same time.

5

With the undo function the the correct event name comes back.

6

Not necessarily. I’ve not had luck getting undo to work.

Anyhow, I think that this was the fastest bug that has been fixed. Norman looked at the bug yesterday, fixed it and closed it. It was less than 24 hours from when I reported the bug until it being fixed. I think that’s a record!

7

Looks like you got attention and it’s fixed.

8

Yeah, I figured this would be one they’d want to fix right away. And I can’t imagine why it was ever editable in the first place. If that text is a label (why wouldn’t it be), then you simply never allow the text to be edited. So I bet the fix for this was really easy and quick.

As it would bit me every so often, I’m really glad I was finally able to figure out how to make it happen.

9

[quote=92305:@Jon Ogden]Not necessarily. I’ve not had luck getting undo to work.

Anyhow, I think that this was the fastest bug that has been fixed. Norman looked at the bug yesterday, fixed it and closed it. It was less than 24 hours from when I reported the bug until it being fixed. I think that’s a record![/quote]

Not even close to the fastest report to fix
We’ve had several that are minutes

10

Thanks for finding a way to duplicate the bug, Jon! I stumbled a few times over it and wondered what I did to make it happen. And thanks for fixing it that fast, Norman!