This commit is contained in:
@@ -60,11 +60,6 @@ todo: v8 migrate additions
|
||||
..........................................................................................................
|
||||
* todo JC misc list:
|
||||
|
||||
percent control hide insignificant trailing zeros?
|
||||
Tag extension should have tag picker instead of empty field in cases where you are picking from existing tags
|
||||
Tag extension to report results of operation? i.e. how many tags deleted etc
|
||||
Tag extension or any extension refresh main data table it was run from after operation (so can see results) automatically
|
||||
Default warehouse try to enter a tag bombs with error likely due to read only nature of default or missing the empty array maybe in it's record? (though tags is supposed to handle that now?!?)
|
||||
PartInventory data table errors out when click on column selector (see if others have same issue once figure out what the issue is)
|
||||
PO form Hide serial field until an ID is set (i.e. don't show 0)
|
||||
PO FOrm serial field read only unless superuser??
|
||||
@@ -960,4 +955,15 @@ build 105
|
||||
memo to dropdown list shows all users for selection then after selecting one shows only that selected when you next drop down, should show all users still like first time.
|
||||
memo click on reply or forward should put cursor into top of edit message control (notes)
|
||||
memo read now flags correctly
|
||||
taxcode form has default of .05 in taxa, change to zero
|
||||
taxcode form has default of .05 in taxa, change to zero
|
||||
Default warehouse try to enter a tag bombs with error
|
||||
|
||||
- not changed
|
||||
Tag extension should have tag picker instead of empty field in cases where you are picking from existing tags
|
||||
** Not doing this, went in to look and it would not work with the system in place. Tag picker control is designed for multiple tags,
|
||||
tags extension system is designed to replace / remove a single tag at a time by design, so wouldn't save any typing by user anyway as would be restricted to one tag
|
||||
and would need extensive changes to working code to implement
|
||||
Tag extension to report results of operation? i.e. how many tags deleted etc
|
||||
** Not practical at this time / have made a case to look into down the road, would require extensive changes to working code at both server and client
|
||||
Tag extension or any extension refresh main data table it was run from after operation (so can see results) automatically
|
||||
** looked into and realized could cause issues forcing a refresh when the user doesn't want it necessarily if they are picking and choosing records to work with in extension more than once
|
||||
|
||||
Reference in New Issue
Block a user