mailstarinc

Recently, FusionPro 13.1.8 dropped, with the only patch note being that it added official support for Acrobat 2024. While the preview display functions properly on MacOS Sonoma, the previous visual issue that was present in 13.1.4 is still there in Ventura. It looks like Ventura is still officially supported, so I wanted to report this. Happy to answer any additional questions/provide more examples.

My FusionPro license renews on April 3rd. I occasionally get a pop-up letting me know this. This is the icon that appears when this pop-up appears on my sidebar. Since about March 4th (give or take), every time I try to do anything in FusionPro, this icon will briefly appear in my application bar before closing and allowing me to complete the task. From previewing a new record to moving a textbox, there's a noticeable pause that wasn't present previously. Composition also takes a moment to start up, and I get this message prior to anything starting. Is this intended behavior? If so, is there any way for me to stop it? It's slowed down the speed at which I'm able to work on my projects. Let me know if I should provide any more information. And my apologies for not posting about it sooner ... needed to get the screenshots to hopefully be as clear as possible.

Attaching a simplified version of the job file & associated data for reference, but essentially – I'm declaring a certain variable globally because it needs to be declared quite a few times throughout this job. However, the variable is not recognized properly when composing or previewing, and only works properly in the rules editor when I open up Javascript Globals first and then preview the rule. Is it not possible to declare a variable based upon a record in the Javascript globals? global variable not functioning as expected.pdf sample data.csv

This is exactly what I was looking for – thanks, Thomas! Having frame groups that are hidden/shown definitely speeds up the composition process. It's not as fast as I would like for it to be, but it did take the time to compose 633 records from 01:13.21 to 00:47.68, so this definitely feels like a good basepoint for me to start at.

Built in to FusionPro is the SetBodyPageUsage(name, usage) function(?) which returns a boolean that says if the page will be composed. I was wondering if it would be possible to create an equivalent that determines whether a text box is composed. I looked through the Rules System Guide, but didn't immediately see anything that existed...so I figured it'd be best to ask here. I have a job that has certain text boxes that should only be composed based upon which version of a letter the client wants to produced. My previous way of handling this had a lot of redundant code that significantly slowed the project – this feels like a way to potentially ease up that issue.

Elaborating on the bullet points – Right now, there's nothing like <ul> <li> in the FusionPro markup, like what you'd find in HTML to create a list automatically. Of course, you can just use tabs or &nbsp; to brute force something, but I was a bit surprised initially to see it not natively built in. If I encounter any other issues or bugs in the future, I'll be sure to report them here. As well as perhaps digging up some of my jobs that haven't run as smoothly and seeing if there's any rule optimization or the such that could be done to make things run faster...

More than happy to share the PDF template – it's attached to this post. And alas – I realized the screenshots had been downsized after making my initial post. Good to know for the future that I should aim for smaller images so they hopefully don't get as compressed. noto sans symbols.pdf

When using the font(s) Noto Sans Symbols (& Noto Sans Symbols 2) (which is a free font that can be downloaded from Google), any underlined text that is returned from a rule with mark-up also appears to be crossed out. Regular Noto Sans does not do this, and changing the base font used for the text doesn't make the underlining go away either. When the font is changed entirely to Noto Sans Symbols, underlining breaks entirely. This is the only font where I've ever encountered something like this. Having Noto Sans Symbols appear anywhere in the returned text causes underlines to break, but ONLY within the returned text. Other underlines that may be present (either directly in the textbox, or from other rules) are unaffected. Two screenshots are attached to this post – one of how the text appears when previewing in FusionPro, and one of how it composes. The top textbox has the rule text in Calibri & the bottom two segments in Noto Sans Symbols & Calibri, while the bottom has the rule text in Noto Sans Symbols and the bottom two segments in NSS & Calibri again. I'm running Creator 13.1.4 on MacOS 13.6.4, but I had this issue originally back in August of 2023 (so on an earlier version of Ventura & FP). Happy to clarify anything further if I've missed anything.

Thanks so much for your reply! I really appreciate all of the insight you've given with your post – everything you've gone over makes sense, especially how complicated it becomes when you're dealing with multiple other organizations, both for the actual development itself and for making sure you're staying up to certain standards. I suppose I can break down my wants for a roadmap into two different categories: Performance enhancements – though as I am operating off of Rosetta at the moment, I'm not sure how valid some of my concerns may be (as an example: when composing a document with many text/graphic frames, the speed at which it is composed significantly slows than when there's only one or two frames. Happy to provide more details there if they're wanted). As I'm not personally familiar with how developing plug-ins for Adobe software works, there may be some things that simply aren't possible (an example myself and my boss have discussed is how potentially multi-threading could help increase speed issues...but, it may be impossible for the FusionPro plugin for Acrobat to ever be multi-threaded, since Acrobat itself is single threaded and likely will be for the foreseeable future. And, of course, multi-threading isn't just a band-aid you can slap on something that'll magically help performance...etc, etc). But – if architecture improvements could lead to speed increases – I'm certain everyone would be happy about that 😀 Feature updates – as an example, it was very exciting when FP13 introduced the updated CopyFit GUI & the ability to return "empty" in the drag & drop GUI. The other new features – while not things that are as necessary for my workflow – are fun to see, in case I do ever need to utilize them. And – knowing if something like bullet points (which as far as I know, aren't present in Creator's markup tags) are on the horizon helps me to plan out changes I may need to make for future repeating jobs. It may also be good to have some sort of hub for known issues – hopefully, it'd help mitigate people all reporting in with the exact same issue (though of course, when dealing with problems, getting MORE sample data is always useful). Perhaps some sort of "here are known issues, if you're experiencing them submit info specifically related to the issue to the support email to help our team fix the problem" post? As someone who only uses Creator and is with a small physical-only shop, there'd likely be many things that don't apply to me, but I'd hope that others would also find the information helpful. Knowing that what people report on the forums helps impact development is wonderful; I'll definitely be sure to speak up if anything comes to mind that I feel would be an improvement in the future. (In fact, there's a potential bug I think I may make a post on soon if I can replicate it with the most recent version of the software...)

If this thread should be in a different section of the forum, I apologize. I've been thinking over where to put it for a while now. I was curious if there were any plans for a public roadmap to be visible for FusionPro. Aside from the M1/M2 support, which I have eagerly been waiting for, I'm also curious to see if there's anywhere where someone can look at planned upcoming features/planned bug fixes/etc ... even just a centralized forum post would be neat.

Because this thread was pinned, I figured it'd be a good place to ask the question...even though it is quite old at this point. If I encounter any fonts that don't cooperate with FusionPro, I'll send them along to support – but yes, most of the time when they don't cooperate it's usually because the font itself was poorly created. Will be looking forward to the Silicon plug-in's release...though I know it's likely still a long ways away. And – good to know that the display issue I've encountered is related to Adobe, rather than Rosetta. Text will often overlap/not fit into the boxes/etc unless I zoom out significantly...but Adobe's been releasing a lot of feature-breaking updates with Acrobat lately, so that doesn't surprise me too much.

That option worked – even on a version of Acrobat where "Use Local Fonts" is gone. So – hopefully this will also help others in the future. Luckily, none of my fonts are corrupted at the moment, but if I encounter issues, I'll be sure to clean out the cache. (I have had fonts break FusionPro before, but luckily the info files from when you load fonts in are always help for identifying that).

Having this issue now – originally, the copy of Acrobat I was running didn't even have "Use local fonts" as an option, but I downgraded to a version that restored the option. Selecting it & loading fonts did not fix the issue. The downgrade to Acrobat was done as a fresh install, and I did a fresh install of FusionPro as well. The version of Acrobat I was downgraded to by Adobe's tech support is 2023.006.20380, but this behavior was occurring on the most recent release as well. I am wondering if this is potentially an issue that's being caused because of Rosetta emulation – I have an M2 Pro, so I'm running Acrobat through it. (I've also had some general display issues which I believe are being caused by the Rosetta emulation, but the font issue is more pressing right now – may make a forum post later showing some examples to see if others are having the same issue.)