[FIXED] Protect "Set as startup form" during renaming

Bug Reports
#1

I noticed that if you rename a Form that you’ve previously Set as startup form, you get the following error when you run your app:

image

The error message is somewhat misleading, but if you’re lucky you’ll realise that you need to manually do Set as startup form again on your newly renamed Form.

The error could be avoided entirely if the Rename… function itself checked for Set as startup form and reapplied that status to the renamed Form automatically, rather than creating an ‘orphan’.

#2

It should already do that! This makes this behaviour a bug - I’m moving to Bug Reports.

And your screenshot has helped us reproduce it, too! Normally, my startup form is a top-level form, and in that case the rename is tracked perfectly. But if you have a form a few layers deep, and set that as your startup form, and then rename that…boom.

Edit: Aaaaand fixed.

1 Like