This commit is contained in:
2021-02-06 00:40:39 +00:00
parent 4df81f485d
commit ad38e07629
3 changed files with 12 additions and 6 deletions

View File

@@ -21,10 +21,15 @@ LISTVIEW REPLACE CURRENT <----HERE not THERE ---v
why does it not switch when switch widths and have to reset?
custom fields dont' show unless defined??
Should user be able to select custom fields in teh column selector if they are not set to show in the first place?
I would say gray them out as inactive but leave in UI for column selector?
Or hide them if not activated so they can't be selected?
Also, maybe don't return them to the client from the server if they are inactive in the first place
Maybe: this does involve some fuckery because there isn't a direct correlation between datalists and for customization
leaning toward just saying fuck it for now It could be useful for peopel to see what is in fields that they set to not show but entered data in previously??
Custom fields
Hide visible=false ones in column selector
SERVER
Don't return or act on in any way custom fields in a datalist query if they are visible=false
todo (after)

View File

@@ -313,7 +313,7 @@ function generateMenu(vm) {
//
async function initForm(vm) {
await fetchTranslatedText(vm);
await populateSelectionLists(vm);
populateSelectionLists(vm);
await ensureTemplateIsInStore(vm);
await initDataObject(vm);
}

View File

@@ -430,6 +430,7 @@ function initWorkingView(vm) {
if (fld.isRowId) {
o.rid = true;
}
ret.push(o);
}
@@ -449,7 +450,7 @@ function initWorkingView(vm) {
o.rid = true;
o.include = true;
}
ret.push(o);
}
}