I can replicate this as well. Definitely starting to look like a bug was accidentally introduced in the cycle gadget.
The 3.1 version just printed that the directory was in component #n of the path, which was not very useful at all. (How do you count that and why is this useful information?)
It's not useful on its own, but in conjunction with the path listed in the textfield gadget just above I think it makes sense.
3.1.4 prints the full font path.
Not necessary, in my opinion, as per above.
I now added a code to check for paths that are too long. In that case, the name is now abbreviated.
Thanks, that'll help, but I still think the cycle gadget is displaying redundant information.
Perhaps some screenshots will make it easier to explain.
Here's 3.1:
3.1_1.png: A just-started Intellifont under 3.1. Workbench:Fonts (path gadget) is recognized as the first component of Fonts: (cycle gadget).
3.1_2.png: I've clicked the cycle gadget. Path gadget changes to Work:PageStream/SoftLogik/Fonts and the cycle gadget changes to acknowledge it's the second component of my Fonts: path.
3.1_3.png: I've typed Work: into the path gadget, and the cycle gadget helpfully informs me that it's not part of the Fonts: path.
3.1_4.png: I've typed a nonsense path into the path gadget and the cycle gadget informs me it's not valid.
And here's 3.1.4:
3.1.4_1.png: A just-started Intellifont under 3.1.4. Workbench:Fonts (path gadget) is repeated in the cycle gadget.
3.1.4_2.png: I've clicked the cycle gadget. Path gadget changes to Work:PageStream/SoftLogik/Fonts and so does the cycle gadget. I don't see a reason to print this information twice.
3.1.4_3.png: I've typed Work: into the path gadget but the cycle gadget changes to Work:PageStream/SoftLogik/Fonts again. I have no way of knowing whether I've selected my intended Fonts: component (e.g., if I mistyped the path or selected the wrong directory from the ASL requester).
3.1.4_4.png: I've typed a nonsense path into the path gadget. Same behavior as 3.1.4_3.png.
Meanwhile, I can confirm my_pc_is_my_amiga's account that something is different in the startup scanning behavior. I think Intellifont always scanned DF0: (and root directories of other volumes?), but now it's scanning root and first-level directories across my whole hard drive as well. Is that the intended behavior or is that a bug?