Enabling the Expert Level in Processor Expert
Join the DZone community and get the full member experience.
Join For Freeprocessor expert in eclipse and codewarrior is cool thing, and acts as the ‘expert’ for anything around the microcontroller used. but by default, it is acting in the ‘basic’ level only.
but there are ways to get it to the expert level
.
the ‘basic’, ‘advanced’ or ‘expert’ level is used to filter the amount and level of properties shown in the component inspector: so the idea is that with basic only the most important properties are shown, with advanced you get more, and with expert you get everything. while this sounds like a good idea (and actually it probably is), i always end up to switch to the expert level as i always think i need to see ‘the full monty’
.
and maybe it is really hard to distinguish what should be in the basic, advanced or expert level?
basic, advanced and expert
to switch the different levels, the component inspector view offers 3 buttons:
basic
below is the i2c_ldd component in ‘basic’ view:
advanced
switching to ‘advanced’ shows more properties:
expert
and finally with expert mode i get the full stuff:
fixing the mode
for myself, i feel the expert mode is the right thing
. for this, i always switch to expert mode in the inspector view. the only problem: processor expert does not remember my settings: when i load the workspace again, its defaulting again back to basic
.
it might be debatable if this setting reversal is a bug or not?
but there is a trick to fix the mode
. there is a setting in the menu
window > preferences > processor expert > general
:
now i would expect that ‘apply’ would change the inspector view settings? nope. the setting is used at the time opening a workspace. not a big deal, but worth to mention.
happy experting
Published at DZone with permission of Erich Styger, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Trending
-
What Is JHipster?
-
Power BI Report by Pulling Data From SQL Tables
-
Breaking Down the Monolith
-
What to Pay Attention to as Automation Upends the Developer Experience
Comments