From ac10db95ef2faa162b228cf89b30341778b7d301 Mon Sep 17 00:00:00 2001 From: Fiona Ebner Date: Tue, 26 Nov 2024 17:29:15 +0100 Subject: [PATCH] display-edit field: add emptyText getter and setter to support data-bind To access the underlying fields a reference to them is now explicitly saved after component initialisation. First user is intended to be the path field for datastores where the emptyText should dynamically be for a relative or absolute path. Signed-off-by: Fiona Ebner [ TL: switch over from saving the xtype to query in the getter or setter to directly savign a reference to the underlying fields. ] Signed-off-by: Thomas Lamprecht --- src/form/DisplayEdit.js | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/src/form/DisplayEdit.js b/src/form/DisplayEdit.js index fe1b83b..049737a 100644 --- a/src/form/DisplayEdit.js +++ b/src/form/DisplayEdit.js @@ -41,6 +41,15 @@ Ext.define('Proxmox.form.field.DisplayEdit', { vm.get('value'); }, + setEmptyText: function(emptyText) { + let me = this; + me.editField.setEmptyText(emptyText); + }, + getEmptyText: function() { + let me = this; + return me.editField.getEmptyText(); + }, + layout: 'fit', defaults: { hideLabel: true, @@ -99,6 +108,11 @@ Ext.define('Proxmox.form.field.DisplayEdit', { me.callParent(); + // save a reference to make it easier when one needs to operate on the underlying fields, + // like when creating a passthrough getter/setter to allow easy data-binding. + me.editField = me.down(editConfig.xtype); + me.displayField = me.down(displayConfig.xtype); + me.getViewModel().set('editable', me.editable); },