This might not be the answer/opinion that you want to hear...I would recommend against having spaces in your Table Occurrence names. Using underscores gives you a visual delimiter and work fine. Underscore are generally safe to use in FileMaker object names.
Not a bug to me...because I do not use spaces in Table Occurrence names.
Hope that helps.
this is among common naming conventions: no spaces and no special characters for Fields, TO's, Scripts, custom-functions, whatever!
Among other potential conflicts, don't using space grants that you can select any item by Double-Clicking.
Thanks for the suggestion. I am aware that solves the problem.
Since naming-with-spaces is permitted though, and is parsed correctly on entry, it seems like FMPA should be able to replace the entire word chain. It doesn't seem like it can't be doable, does it? It knows where the last recognized operator or term is while you are typing in the new Script Space, so it should know where the term you are working on starts. Seems like it ought to be easily accomplished.
I feel semi-stuck with the naming I've got. Originally I did use some underscores or CamelCase or inchwormCase, but I got tired of fixing the field name legends on the layouts as I added them. And if you do "fix" them then they no longer alter themselves when you alter a field name. At this point much CWP (via PHP, XML) would need to be altered too, if I were to start renaming everything. I'm sure you know what I mean.
I feel semi-stuck with the naming I've got.
I'm not quite sure. I recommend to do a test with 1 Field AND TO AND Script:
change the name and figure out where the change get's applied automatically.
Even with placeholders such as
<<Adress::First Name>> being changed to <<Adress::First_Name>>
Maybe you like to set up a small database from scratch for some experiences.
Sure if you use script with hardcoded gotoLayoutName, you're screwed
Oh yes, name changes work fine, I imagine everything is referenced by ID internally. I'm just saying that I avoided camel case or underscores so that the text labels on layouts would LOOK good to the user.
If you edit a field label text chunk (next to the field on the layout, for example) it unlinks it from the field name, so that if you change the field name the label will no longer automatically change.
So, if I had used underscores, then cleaned up the automatic field label (placed when the field is added to the layout), by removing the underscores, then if I subsequently changed the field name in the Manage Database area, the label will no longer change as well. It would remain as what I had manually changed it to, to clean it up.
Regarding the CWP via XML & PHP, there is no ID or token level, it's all by name of the field. So, any field or table occurrence or list name changes also need to be done in the PHP files too, anywhere those are referred to. Not impossible, just tedious: find, make sure it's appropriate to replace, and replace. Repeat.
That's why semi-stuck. I'd rather have FMPA deal with field names with spaces very well... than go through all that just to get auto-complete to be friendly.
FileMaker supports spaces in object names, it's a feature. Type-ahead suggestions is a new feature, I love it, but it doesn't play nicely with old features. Until it does, it's buggy.
Thank you for your post.
I have sent your post and video to our Development and Testing departments for review. When I receive any feedback, I will let you know.
Thank you. Perhaps it's worth mentioning that when typing FileMaker functions or script steps in the same environment, many of which are multi-word with spaces, those are completed and replaced properly by the type-ahead feature, much as I would expect for table and field names that include spaces. So, it seems like it ought to be possible.
I have included your latest comments in the original report.
Thank you, TSGal.