From: Matthias Heiserer <m.heiserer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH widget-toolkit 2/2] use the width-helper from utils
Date: Thu, 24 Mar 2022 12:33:30 +0100 [thread overview]
Message-ID: <20220324113331.681971-2-m.heiserer@proxmox.com> (raw)
In-Reply-To: <20220324113331.681971-1-m.heiserer@proxmox.com>
Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
---
src/node/APTRepositories.js | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/src/node/APTRepositories.js b/src/node/APTRepositories.js
index 09ed0be..d63a569 100644
--- a/src/node/APTRepositories.js
+++ b/src/node/APTRepositories.js
@@ -230,16 +230,7 @@ Ext.define('Proxmox.node.APTRepositoriesGrid', {
});
},
listeners: {
- render: function(btn) {
- // HACK: calculate the max button width on first render to avoid toolbar glitches
- let defSize = btn.getSize().width;
-
- btn.setText(btn.altText);
- let altSize = btn.getSize().width;
-
- btn.setText(btn.defaultText);
- btn.setSize({ width: altSize > defSize ? altSize : defSize });
- },
+ render: Proxmox.Utils.calculateWidth,
},
},
],
--
2.30.2
next prev parent reply other threads:[~2022-03-24 11:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 11:33 [pve-devel] [PATCH widget-toolkit 1/2] Utils: add calculate max button width hack Matthias Heiserer
2022-03-24 11:33 ` Matthias Heiserer [this message]
2022-03-25 8:37 ` [pve-devel] [PATCH widget-toolkit 2/2] use the width-helper from utils Thomas Lamprecht
2022-03-24 11:33 ` [pve-devel] [PATCH manager] " Matthias Heiserer
2022-03-25 8:47 ` Thomas Lamprecht
2022-03-25 8:35 ` [pve-devel] [PATCH widget-toolkit 1/2] Utils: add calculate max button width hack Thomas Lamprecht
2022-03-25 8:47 ` Thomas Lamprecht
2022-03-28 9:43 ` Matthias Heiserer
2022-03-28 9:44 ` Thomas Lamprecht
2022-03-28 10:17 ` Matthias Heiserer
2022-03-28 10:27 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220324113331.681971-2-m.heiserer@proxmox.com \
--to=m.heiserer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.