No Components Listed

  • Thread starter Thread starter skylark
  • Start date Start date
S

skylark

I have just installed a XP Embedded Development Tools SP1, applied SP2 and
the FP2007.

When I open Target Designer and use the default visible components (1000) I
can see the components in the component list. However, if I change the number
of visible components to anything else, ie. 10000 no components are then
visible. This is apparent even after restart Target Designer.

Appreciate any help with getting all the components listed with 10000 visible.

Thanks
 
Hi skylark,
the behaviour you find is correct, 10000 is the highest visibility value,
but no real component has more than 2000.
If you set the level to 2000 only macros are shown, if set to 2100 nothing
is shown.
I have the level always set to 100 to have better control.
Regards Raffaele
 
Raffaele

Thanks for your reply. I am sure I previously had '10,000' components set
and these listed OK in the Target Designer. Apart from that, are you saying
that it is actually better to develop with less components visible? Would
this not rely more on TD to auto resolve any dependencies, and what about
additional features. I remeber setting this to 10,000 so that I had access to
some additional features/functions.

It has been some time since I have touched a XPe development system, from
what I can remember things were more striaght forward than it is now.

Thanks again for your help.

Jason
 
No, Jason
I set visibility level to 100 to see as much components possible.
Level 100 means you see a lot, 1000 you see main, 2000 only macros.
Take this way: Level 100 shows 10.000 components, level 10.000 shows 0
components!
I always have Autoresolve disabled be aware of what is added, so level shoul
be kept low.
Regards Raffaele
 
No, Jason
setting 100 means you see 10.000 components, setting 10.000 means 0
components.
I develop with all components available and auto resolve disabled, to better
control what's happening.
Raffaele
 
Raffaele

You are star, thanks for clearing that up for me. All components are now
visible! :-)

As for not using auto-resolve disbaled, how do you ensure you have all the
components included in your build? I guess you are VERY familiar with what is
required in your builds!

Have a good weekend, and thanks again for clearing things up for me.

Jason
 
Jason,
this is the way I do for a new build, provided I already have hdw drivers:
1) start with your hardware template and add macro components ( those seen
at level 2000) as :
TCPIP networking
Winlogon sample macro
Win xp explorer user interface
Internet explore
Kernel audio
and all
then auto resolve until a basic working device is ready. Set this .SLX as
read-only keeping it as the base for new designs.
If you need to improve your design, add components with auto resolve
disabled, so you are in control of what is added.
If autoresolve is disabled, at the end of the check TD shows you the list of
what's missing, and you have the choice to add or not each one.
Good weekend to you also Raffaele
 
Back
Top