Prevent model init with unset bounding box and persist flag

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Bounding box defaults could trigger huge model extents; prevent initialization until the user explicitly sets an extent and persist that state.

• Data Manager
  • Track a bounding_box_set flag, persist it in project save/load, and mark it when users change the box.
• UI/Validation
  • Block “Initialize Model” when the bounding box isn’t set and show a clear error.
  • Visually flag unset bounding boxes by outlining extent spin boxes in red until set.

Example:

# Persisted flagdata_manager.set_bounding_box(xmin=10, xmax=100, ymin=20, ymax=120, mark_set=True)
data_manager.is_bounding_box_set() # True# UI guardifnotdata_manager.is_bounding_box_set():
QMessageBox.critical(self, "Bounding box required", "Please set the bounding box before initializing the model.")

Original prompt

Update the bounding box logic to include a flag that keeps track of whether the bounding box has been set, this flag should be stored in the data manager and should be saved in the project. Currently the default bounding box is min 0 max 1000 in x and y. But the model will use this bounding box and then expand to keep all of the data points. This can cause a massive model support and crash the plugin. What we need to do is have a flag that the bounding box has not been set and in this case it should not allow the user to initialise their model. It should give and error and tell them to update the bounding box. IT would also be good to visually show the bounding box has not been changed by adding a red box to the extent spin boxes.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.