HuntingNut
HuntingNut
   Login or Register
HomeCommunity ForumsPhoto AlbumsRegister
     
 

User Info

Welcome Anonymous

Nickname
Password

Membership:
Latest: waidmannsheilsafaris
New Today: 2
New Yesterday: 1
Overall: 13234

People Online:
Members: 0
Visitors: 132
Bots: 1
Staff: 0
Staff Online:

No staff members are online!
 

Coppermine Stats
Photo Albums
 Albums: 315
 Pictures: 2480
  · Views: 849744
  · Votes: 1316
  · Comments: 85
 

Request - OEM/MilSurp options
Post your bug reports or feature requests here!

View previous topic :: View next topic  
Author Message
SyberShooter
Member
Member


Joined: Jul 23, 2010
Posts: 93
Location: Arizona

PostPosted: Fri Sep 23, 2011 7:21 am    Post subject: Request - OEM/MilSurp options Reply with quote

I would like to request some generic options in the standard bullet, powder, primer and case database.
Many times I might be testing a factory load and don't know the type or brand of component used. I generally type OEM in to indicate that. I also use a lot of Military Surplus which I denote as MilSurp so I know it is different from commercial OEM.

Having generic terms available in the drop downs helps save typing and increases uniformity. Other possible terms could be often used generic components such as 'Cast', 'LSWC', 'FMJ' M193, Ball etc. (These generics should be available in their category even if you havent selected some unknown data that may be required for named brands- ie: no bullet manuf. selected I can still select FMJ and then go back and select MilSurp for manuf. and have FMJ be persistant).

or are these something I should put in the user configurable files?
but don't they get wiped out with updates?

thanks
al
Back to top
View user's profile
SyberShooter
Member
Member


Joined: Jul 23, 2010
Posts: 93
Location: Arizona

PostPosted: Sat Sep 24, 2011 9:21 am    Post subject: Re: Request - OEM/MilSurp options Reply with quote

Well... after trying to add some generic terms to the user .slk file I can see where there will be some issues. The two primary problems I currently see are:
1. Every caliber and bullet weight would need a generic entry. This is a lot of data. Enough that it might justify it's own SLK file for loading at startup - which might help with problem #2, which is.
2. All the data fields need to filled in or else the line is not recognized as valid. The problem fields are BC and SD since these are probably unknown and will be different for each bullet. Also the bullet diameter is required which means an entry for every caliber and bullet weight.

That's a lot of work just to have OEM and MilSurp labels available in the drop down list - especially when it works just as well to just type it in during data entry.

Maybe this isn't such a good idea after all unless it can be easily added with a few lines of code to include it as a data selection option with exceptions to ignore the bullet dia, SD & BC during entry and ballistic calcs..
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic   Printer Friendly Page    Forum Index » Bug Reports / Feature Requests
Page 1 of 1
All times are GMT - 7 Hours



Jump to:  


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Valid CSS! Valid HTML 4.01!
Click to check if this page is realy HTML 4.01 compliant for speed :)

All logos and trademarks in this site are property of HuntingNut.com.
The comments are property of their posters, all the rest © 2011 by HuntingNut.com
Interactive software released under GNU GPL, Code Credits, Privacy Policy

.: Upgraded to DragonFly 9.2 by *Dizfunkshunal* :.