You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+44Lines changed: 44 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -222,3 +222,47 @@ o Lot histories are not saved and are rebuilt each time one is desired
222
222
- Added functionality: ‘find’ can now edit a group of materials after the desired list has been generated
223
223
o Essentially allows for a ‘mass edit’ feature
224
224
- Updated menu heading
225
+
226
+
V1.8 1/7/2015
227
+
- New function! ‘usage’ or ‘monthly’ provides a powder usage history for the current month
228
+
o User enters ‘usage’ at the main menu and usage is automatically calculated and exported as a report, similar to ‘lot history’
229
+
o Currently only works for the current, cannot be done for a month in the past
230
+
- Changed the ‘recent’ function to only clear if 500 entries are made
231
+
- Added functionality: editing a group of materials in ‘find’ will now add them to ‘recent’
232
+
- Added functionality: listing results in ‘find’ also gives the total weight without having to write a report every time
233
+
- Added functionality: searching for materials in ‘find’ will automatically search for partial matches if no complete matches are found
234
+
o Partial matches are only searched for during new searches
235
+
o Refining a search will not seek partial matches
236
+
o A partial match is one where the user input is found as fragment of the actual term, or vice versa.
237
+
o Eg. Searching for ‘steel’ would return partial matches for ‘stainless_steel’ ‘maraging_steel’ and ‘chrome_steel’
238
+
o Eg. Searching for ‘nickel_iron’ would return partial matches for ‘nickel’ and ‘iron,’ but NOT ‘nickel_steel’ or ‘nickel_chrome’
239
+
o One of the terms must appear COMPLETELY in the other to return match
240
+
- Updated help menu
241
+
- Updated menu heading
242
+
- Re-enabled hidden experimental function, used for debugging only
243
+
o Accessed via command ‘beta’
244
+
- Bug fixes:
245
+
o Whenever a date is entered by the user, the program will thoroughly check to be sure it is a valid date in the proper format
246
+
o The program will not incorrectly add a material to ‘recent’ if the edit never went through
247
+
V1.8.1 2/6/2015
248
+
- ‘search’ now displays its results in a neater table format
249
+
- Fixed a bug where inventorying a new item and using it in the same month would report no usage
250
+
V1.8.2 2/17/2015
251
+
- Updated menu heading
252
+
- Added functionality: ‘monthly usage’ now prints out the report on the screen as well as writing it to the file
253
+
- Added functionality: ‘recent’ now gives a preview of the total weight, instead of having the print the report to see it
254
+
- Added functionality: ‘monthly usage’ now tallies up power gained and powder lost in the monthly report, instead of giving just net usage
255
+
- Added functionality: whenever a number is entered for a weight, the program checks to ensure it is an actual number before continuing, preventing commands or nonsensical entries accidentally being entered as weights
256
+
- Writing any report now puts the written text report in a folder called ‘reports,’ instead of putting them directly in the program’s files
257
+
V1.8.3 3/4/2015
258
+
- Added functionality: ‘search’ now also adds up the total weight of the powder containers being scanned
259
+
o Now only prompts the user to enter a barcode once at the start, instead of each time.
260
+
- Updated menu heading
261
+
262
+
V1.8.4 4/16/2015
263
+
- When a contained of powder is edited for weight (meaning the weight has changed) the program will now also automatically mark it as being opened
264
+
- Added a hidden command at the main menu “fix_all”
265
+
o Runs through the list of powder in inventory
266
+
o Any entry with more than 1 instance of history (i.e the weight has ever changed) will be set to ‘1’ or be marked as opened
0 commit comments