Closed Bdavy92960 closed 1 year ago
I've checked the sequence above and it falls well outside of the optimal area on several of my devices. This can be resolved easily:
f 5% +.2a+ -1% +o1+ -2% +,22c...''2.'+ (15,0) -2% ```+````````ry2.' (-2,0) 24- (-12,0) -2dh(
)....'' (9,0) -2% pn(1.)~ (6,0) ~iv6s......'~~ (-8,0) ''2rp(2)1
However, this fix creates new overlapping issue. OpenAero should fit sequences into the available size, even when not designed optimally. So I will have a look and try to have a fix for the next update. By the way, the same issue is present on the first version of OpenAero that supported IMAC forms.
A fix update is available at https://openaero.net/devel/ . Please let me know if this resolves the issues.
I played around with it and it seems to correct the issue we were seeing. Thank you for looking at it, although the primary problem was a sequence designer not checking his work.
Brad
Fixed in 2023.3.7
I don't know if this started with the new release, but I'm having more problems with it. The printed forms seem to both be offset to the left side of the page, which is causing the mini form A to cover figures on Form C, even when the layout is within the nominal boundaries. Not sure if "justifying" form C to the Right would correct this, or perhaps changing the location of the mini form A to always be on the left side.
As an example, here is a sequence string for a draft sequence that all falls within the nominal area, but when going to print with the miniform A, the figure list covers the ninth figure. f (10,0) 5%
+.2a+
(-5,0) -1%+o1+
(-9,0) -2%+,22c...''2.'+
(15,0) -2%``+````````ry2.' (-2,0) 24- (-12,0) -2dh(`)....'' (9,0) -2% pn(1.)~ (6,0) ~~iv
6s......'~~ (-8,0) ''2``rp(2)1Update: Discussion with the individual creating the sequence reports that he created the sequence on his phone, and when he uses the print process on his phone he does not have issue with the miniform A printing on top of the figures on form C, so looks like it may be a difference in the way the print process is implemented on the phone vs. a web version.
Continuing to work with him to get it better understood.
Update: Found the problem with the above sequence string. As laid out, figures 8 and 10 were trying to use the same space, forcing the print layout to stretch the figure 8-9 line, and driving figure 9 behind the list of figures. Extending figure 9 downline eliminated the overlap, and solved the print issue. So not sure if there is an update that can be made to better handle this overlap, or I just need to train my sequence authors to avoid the situation.
Brad