@toddgeist and team, I’d like to ask that you consider changing OttoDeploy to not hide the Status Toolbar at line 28 of its OnFirstWindowOpen script. Alternatively, give your users an alternative, and/or tell me what I’m missing in the following explanation.
As far as I can tell, FileMaker has a long-standing bug where any hosted solution file that f’s with my Status Toolbar, fubars it for me permanently. As revealed by the letter ‘f’ count of in the previous sentence, I find it unforgivably bad form for an app to mess with my environment behind my back. OttoDeploy is a developer tool. Developer’s shouldn’t need other developers to hide their toolbars for them. In my frustration, I’ve done a fair bit of experimenting to figure out how to get my toolbar customization to stick as I move between hosted solution files. What I’ve found is that if any file ever hides my toolbar, the next time I show it, the toolbar will have reverted to the default config.
Of course, I simply commented out that line in my copy of OttoDeploy. But, I assume the next time I do the quick-update, my modification will be lost, and I’ll have to go through the whole close file, download, fix my toolbar, upload, routine again.
I’d love to hear that I’ve missed something because this toolbar routine has been a “death by a thousand paper cuts” kind of annoyance for a very long time.
Thanks for listening,
-Mike