Report button is grayed out when exception happened to 3rd party plugin's code. We wouldn't like to receive errors from there since we can't fix them anyway. -
Why this design change : all the actions, but one - this one - are at the dialog bottom, in plain text? I'm sure others will miss it like I did.
I think it's becoming a space issue, adding more and more buttons on a new page. There is another windows which does this now as well, the functionality grouping is consistent. A little annoying to get used to, but I don't think it's bad.
Those buttons at the dialog bottom usually close one terminating modal session. That's why 'blame' and 'open request in browser' buttons moved from the dialog buttom. Making those buttons look like regular JButtons might be worth thinking about though.
Yes, until you clear them with 'clear and close'. I mean fatal error icon will flash anyway if the exception happens again but you won't be presented an option to submit this issue again.
Those buttons at the dialog bottom usually close one terminating modal session.
Well, the Apply button (in a Apply-Close or OK-Apply-Cancel dialog), for example, does not close the dialog.
It would be useful, to make clear, that the Blame button operators on the selected exception (which is what I believe should be the case). These buttons usually are right beside the table/list (like Add, Remove, Move Up, Move Down, ... buttons).
I understand that JetBrains would like not to receive plugin errors. In that case, please do not show flashing icon with "fatal errors". User cannot do anything about it either. It is plain irritating to see that icon flashing and then being clueless when "report to jetbrains" is disabled.
A better idea might be for JetBrains to establish a platform where you accept plugin errors and plugin author receives them. This will make life easy for users, plugin authors as well as you JB!
Report button is grayed out when exception happened to 3rd party plugin's
code. We wouldn't like to receive errors from there since we can't fix them
anyway.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
Maxim
We can't send you "Blame IDEA core" errors either, as the "Send.."
button is hidden when they happen.
Alain
That probably means nothing is typed in into user description area. Type
in xxx or something if you unsure about what might be causing this.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
>> .. 3rd party plugin's code. We wouldn't like to receive errors from
>> there since we can't fix them anyway.
>>
Maxim
>
(see attached image)
There is no /Send report to JetBrains/ button, so I can't type anything
anywhere.
Alain
Attachment(s):
blameIdeaCore.png
Alain the send button is the little bug icon
R
Which can be normally activated by pressing Enter.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
Maxim
>> Alain the send button is the little bug icon
>
Why this design change : all the actions, but one - this one - are at
the dialog bottom, in plain text?
I'm sure others will miss it like I did.
Alain
Robert
>Alain the send button is the little bug icon
>
>
Thanks.
Alain
I think it's becoming a space issue, adding more and more buttons on a
new page. There is another windows which does this now as well, the
functionality grouping is consistent. A little annoying to get used to,
but I don't think it's bad.
R
+1 from me. Making the default button (see Maxim's answer about hitting
Enter) not a visually distinguishable button is not a professional choice.
Just curious, will the same exception now be suppressed for the current
session, when it was reported?
Tom
Those buttons at the dialog bottom usually close one terminating modal session.
That's why 'blame' and 'open request in browser' buttons moved from the dialog
buttom. Making those buttons look like regular JButtons might be worth
thinking about though.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
>>> Alain the send button is the little bug icon
>>>
See my reply to Alain.
Yes, until you clear them with 'clear and close'. I mean fatal error icon
will flash anyway if the exception happens again but you won't be presented
an option to submit this issue again.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
Well, the Apply button (in a Apply-Close or OK-Apply-Cancel dialog), for
example, does not close the dialog.
It would be useful, to make clear, that the Blame button operators on the
selected exception (which is what I believe should be the case). These
buttons usually are right beside the table/list (like Add, Remove, Move Up,
Move Down, ... buttons).
Tom
I understand that JetBrains would like not to receive plugin errors. In that case, please do not show flashing icon with "fatal errors". User cannot do anything about it either. It is plain irritating to see that icon flashing and then being clueless when "report to jetbrains" is disabled.
A better idea might be for JetBrains to establish a platform where you accept plugin errors and plugin author receives them. This will make life easy for users, plugin authors as well as you JB!