-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Split Layout From VBA should be grayed out if Sanitize is off #554
Comments
I am starting to wonder if we should even allow In concept it's nice to be able to export natively without any modification to the file, but it seems like new users tend to get led astray on the purpose of this option. I am just questioning whether it is worth the effort of building compatibility for an option that isn't really useful in the intended purpose of the add-in. If If someone wants to test the manual export and import of an object, they can do it from the immediate window with a single line of code. SaveAsText acForm, "frmMain", "frmMain.bas"
LoadFromText acForm, "frmMain", "frmMain.bas" |
Ya know...I think you're right. I was actually playing with Sanitization regarding #551 also, and with it set to off, I cannot build, either. I do think we need to allow the Color Sanitize to be off (it doesn't affect buildability as far as I can tell). Proposed fix options
For the options upgrade path, I'd propose we upgrade Personally, I think option 5 is the most UX friendly. It lets low-code devs still get a "raw" export, and we nudge users to use |
If
Sanitize Level
is set toNone (Off)
, we should gray outSplit layout from VBA
, because it doesn't do anything.We should also update the Wiki with this info.
The text was updated successfully, but these errors were encountered: