Re: setting the focus with keyboard property on a field
Posted: Sun Feb 16, 2020 12:40 pm
Hi
I do agree with the IDE bug issue.
It 'feels' that the structure is likely to come tumbling down at any moment. The software 'feels' almost amateurish and unsupported as there are so many niggles that just don't quite work. I have had several bugs open for years. Examples.
1. Multiple monitor support. The mouse alignment frequently fail if you have different size monitors and often you lose the top of the window and the tool bars. (Two years or longer now) - Completely repeatable. This is where the mouse action (where you click) does not line up with the actual mouse cursor. I don't know many developers who lives on a single screen. I like many screens as it makes working on code easier (but I could be alone here)
2. Constant crashing with breakpoints. Completely repeatable. (Open Two or more years). There is a sequence where if you press the step over button after a breakpoint is triggered the IDE crashes out. (Can't remember the exact recipe but it is documented)
Many others.
I would vote. 'Please stop with new features for 3 months and stabilize what we have PLEASE.' PLEASE PLEASE PLEASE PLEASE
The instability and bugs make me wonder if the platform is going to be supported as we go forward. It is hard to promote a platform to other developers when it is unstable.
If the software was not so DAMN AWESOME (cross-platform and ability to do everything we can) I would have abandoned it years ago because it feels like it is falling apart.
My vote is to fix what we have and clean up the bug list and methods for reporting bugs. It is difficult to actually help the development when the bug reporting mechanism is clunky and the level of response is so slow. I have largely stopped reporting things because generally they are already known (however it is hard to match them). Kinda sad really. I expect others have done the same. Why bother reporting when nothing happens!
Grrrr
M@
I do agree with the IDE bug issue.
It 'feels' that the structure is likely to come tumbling down at any moment. The software 'feels' almost amateurish and unsupported as there are so many niggles that just don't quite work. I have had several bugs open for years. Examples.
1. Multiple monitor support. The mouse alignment frequently fail if you have different size monitors and often you lose the top of the window and the tool bars. (Two years or longer now) - Completely repeatable. This is where the mouse action (where you click) does not line up with the actual mouse cursor. I don't know many developers who lives on a single screen. I like many screens as it makes working on code easier (but I could be alone here)
2. Constant crashing with breakpoints. Completely repeatable. (Open Two or more years). There is a sequence where if you press the step over button after a breakpoint is triggered the IDE crashes out. (Can't remember the exact recipe but it is documented)
Many others.
I would vote. 'Please stop with new features for 3 months and stabilize what we have PLEASE.' PLEASE PLEASE PLEASE PLEASE
The instability and bugs make me wonder if the platform is going to be supported as we go forward. It is hard to promote a platform to other developers when it is unstable.
If the software was not so DAMN AWESOME (cross-platform and ability to do everything we can) I would have abandoned it years ago because it feels like it is falling apart.
My vote is to fix what we have and clean up the bug list and methods for reporting bugs. It is difficult to actually help the development when the bug reporting mechanism is clunky and the level of response is so slow. I have largely stopped reporting things because generally they are already known (however it is hard to match them). Kinda sad really. I expect others have done the same. Why bother reporting when nothing happens!
Grrrr
M@