Skip to content
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

Alternate parts #236

Closed
volafh opened this issue Apr 16, 2018 · 2 comments
Closed

Alternate parts #236

volafh opened this issue Apr 16, 2018 · 2 comments
Labels
feature-request New features resquested. wont fix Features that will be not implemented or that diverges from KiCost context.

Comments

@volafh
Copy link

volafh commented Apr 16, 2018

With a similar goal in mind like issue #17 I'd like to suggest the possibility of entering alternatives to parts. Especially when looking at generic passive components you might have tested several alternatives for your design and want to use the component with best availability.

There is something similar with Subparts. You can of course use subparts in order to automatically get storage and price of alternate parts and then manually delete the non-stocked or more expensive.

@hildogjr hildogjr added the feature-request New features resquested. label Apr 16, 2018
@hildogjr
Copy link
Owner

hildogjr commented Apr 16, 2018

Something in this line could be:

  1. Use more than one manf#cone in the design (e.g. manf# = PART1; PART5; PART4);
  2. Set ALIAS variable (e.g. alias = 1; 3, in this example PART1 and PART4 are alias);
  3. Create the spreadsheet as usual;
  4. Create other spreadsheet page as 'minimum values of PART1 and PART4' or other rule or even some kind of 'combo select'/option select.

This is just a idea.
For now, I am trying to use time on the base feature as multiple currency #65 and bugs.

@hildogjr hildogjr added the wont fix Features that will be not implemented or that diverges from KiCost context. label Aug 6, 2018
@hildogjr hildogjr closed this as completed Aug 6, 2018
@hildogjr
Copy link
Owner

hildogjr commented Nov 17, 2018

@mobilinkd, about the discussion in #17. This topic was closed by inactivity (the author never answer me with some discussion/guideline for implementation).

The propose of use | as "or" is interesting, but we have to keep in mind that the different distributors could have best price in different manf# part that compose your selection. Therefore the spreadsheet have to deal with the best price (not the internal KiCost code), this will ask for a new spreadsheet format.

The work around is using the multipart options and select by your self.

I am re-opening this issue for new propose about, if you have some. But, for now, we have without people to fix the main recent issues of KiCost (https://forum.kicad.info/t/kicost-call-of-developers/13271), so I have to focus me time in keep KiCost operational (not working in #236, #17).

@hildogjr hildogjr reopened this Nov 17, 2018
@hildogjr hildogjr removed the wont fix Features that will be not implemented or that diverges from KiCost context. label Nov 17, 2018
@hildogjr hildogjr added the wont fix Features that will be not implemented or that diverges from KiCost context. label Mar 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New features resquested. wont fix Features that will be not implemented or that diverges from KiCost context.
Projects
None yet
Development

No branches or pull requests

2 participants