New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print Size tool/build step - small issue with Hex option #175

Closed
TM1234 opened this Issue Feb 3, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@TM1234

TM1234 commented Feb 3, 2017

I'm using the latest 3.2.1 plugins in Eclipse/CDT Luna SR2 32 bit on Windows 7 64 bit.
I've noticed a small issue with the Cross ARM GNU Print Size tool/build step configuration.
View the properties of a project.
By default Size format = Berkeley and the Hex and Show totals checkboxes are clear.
Select Size format = SysV.
The Hex option becomes greyed out because it's only relevant to Size format = Berkeley.
Click OK to apply/save the changes and close the Properties window.
View the properties of the project again.
Format size = SysV but the Hex option is not not visible at all.
Select Format size = Berkelely and the Hex option remains hidden.
Click OK to apply/save the changes and close the Properties window.
Open the properties again.
Format size = Berkeley and the Hex option is again visible.
I suppose ideally the Hex option should remain visible no matter what Size format is selected but should be disabled/greyed out when Size format = SysV?
Hope this helps.

@ilg-ul

This comment has been minimized.

Show comment
Hide comment
@ilg-ul

ilg-ul Feb 3, 2017

Contributor

thank you, time permitting, I'll try to address this.

Contributor

ilg-ul commented Feb 3, 2017

thank you, time permitting, I'll try to address this.

@ilg-ul ilg-ul self-assigned this Feb 3, 2017

@ilg-ul ilg-ul added the bug label Feb 3, 2017

@ilg-ul ilg-ul added this to the Next release milestone Feb 3, 2017

@TM1234

This comment has been minimized.

Show comment
Hide comment
@TM1234

TM1234 Feb 3, 2017

Thanks for the quick reply Liviu.
As I said it's a minor issue in the greater scheme of things especially given that there is an easy workaround.

TM1234 commented Feb 3, 2017

Thanks for the quick reply Liviu.
As I said it's a minor issue in the greater scheme of things especially given that there is an easy workaround.

@ilg-ul

This comment has been minimized.

Show comment
Hide comment
@ilg-ul

ilg-ul Feb 24, 2017

Contributor

fixed since 3.3.1-201702251311

Contributor

ilg-ul commented Feb 24, 2017

fixed since 3.3.1-201702251311

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment