From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve_flutter_frontend] fix: ui: overflow error when `pending` chip comes to view
Date: Thu, 12 Jun 2025 11:53:31 +0200 [thread overview]
Message-ID: <20250612095331.26328-1-s.shaji@proxmox.com> (raw)
When the pending chip appears after enabling an option from the options
page, Flutter throws an overflow error, causing the chip to render
on top of the Switch widget due to insufficient space between
the title and the switch toggle.
To resolve this, modify the layout so that the pending chip widget
is rendered in a column instead of a row.
Steps to reproduce the issue:
- Navigate to the options tab of any VM.
- Enable the "KVM hardware virtualization" option.
- You will encounter a render flex error.
Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
---
lib/widgets/pve_config_switch_list_tile.dart | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/widgets/pve_config_switch_list_tile.dart b/lib/widgets/pve_config_switch_list_tile.dart
index af02ee6..c209fbe 100644
--- a/lib/widgets/pve_config_switch_list_tile.dart
+++ b/lib/widgets/pve_config_switch_list_tile.dart
@@ -32,8 +32,8 @@ class PveConfigSwitchListTile extends StatelessWidget {
Widget? _getTitle() {
if (pending != null) {
- return Row(
- mainAxisAlignment: MainAxisAlignment.spaceBetween,
+ return Column(
+ crossAxisAlignment: CrossAxisAlignment.start,
children: [
title!,
Chip(
--
2.39.5 (Apple Git-154)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-06-12 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 9:53 Shan Shaji [this message]
2025-06-13 11:19 ` Michael Köppl
2025-06-16 12:04 ` Shan Shaji
2025-06-16 14:12 ` Shan Shaji
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=20250612095331.26328-1-s.shaji@proxmox.com \
--to=s.shaji@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox