eluengo

Thanks MikeTO Sure this anchor duplication does occur, but the anchors dereferenced was not those from the TOC, they was the other not related to the TOC but to the cross-referencing. Either there is a hidden link between all references (this should not occur or be never so programmed) or a confusion between with multiple references to an unique anchor. In either case appear to be a programming confusion. For my case it has no much transcendence because I know how to do the same thing thru different procedures. It was only because this way is quicker than other. But is not really a problem. Hopefully this can alert the programmers to search for this unstability (and other ones that those, otherwise very good, apps have, specially with the text styles). Thanks for trying to help Emilio

p 2024-11-17 a las 16.44.26.mov Hello MikeTO This is the sequence -- A pair of new inserted blank pages -- I select a pair of text frames containing the text of a TOC in the previous pages -- Duplicate (by selecting-option.dragging) and positioning onto the new fresh pages -- After it entering text by double.clicking, selecting all text thru command.A -- Then erasing all this text (no affecting the original Index, indeed) with the keyboard (⌫) -- With the erasing of this text, all the cross-references are dereferenced (as you can see: the little dark circles with the checkmark inside transform all to hollow circles with a little interrogation mark inside), not before I think the video shows it OK Sure, If I create new text frames instead of duplicating previous TOC-containing, the page numbers from the cross-references mantain themselves correctly. It's an annoying behaviour only because duplicating a previous existing text frame is speedier than recreating new ones and applicating all the quirks and whistles that these should have to maintain homogeneous styles throughout the book. Thanks for your attention Emilio

After inserting some pages at the beginning of a book, all the cross-references went dereferenced, preflight showed error in all of them. But buttons for updating one or all cross-references doesn't update them to the correct target. They should be manually corrected reference by reference. Is this a normal behaviour or not? I send a short video.... Emilio p 2024-11-17 a las 12.06.32.mov

I don't know if it's useful but I use this external edit in ApplePhotos (to AFP 2) sometimes, and instead of "saving" or "saving as" I simply close directly the app letting it to ask me if I save the changes, in this way I have never had a problem

Ich weiss, es ist zu einfach, und du hast es sicher probiert, aber manchmal das Komputer aus- und einschalten funktioniert. Auch wenn du die Komputercachés wischst: Mac ausschalten, dann nochmal einschalten mit Hochbuchstabentaste gepresst (wenn in Intel Mac) oder in M1-2-3 Mac auschalten und wieder einschalten aber kontinuierlich Starttaste pressend, und nachher vom schwarzen Schirm aus: deiner Festplatte das System MIT der Hochbuchstabentaste gepresst starten. In beide Fälle: einige minuten mit dem Komputer spielen, dafür dass die Cachédateien gewischt werden, un immer danach wieder aus- und einschalten, un vielleicht funktioniert wenn das problem mit den using-Bit vom OS zu tun hat. Eine app kann alles das machen ohne so viele Arbeit: ONYX, ist gratis, und normlerweise funkzioniert prima. Hoffe nicht zu fehleraft auf Deutsch geschrieben zu haben

I think is's not really a problem of the 3 AFF apps, but since the actualization to the last Sonoma version (14.3) in my M1 Mac, the ultraslow first launch that we used to have before M1 has returned: frequently more than 30 seconds after dock-click lasts to appear the AFF window. Its probably an OS problem, but it's annoying. It happens only on the first launch after computer (re)start, next launches are near instantaneous, as we used to.

No

I don't know if this a bug or a misbehaviour.... and is not especially annoying, but if it can be corrected...? Some flaps on the Studio Tools inspector doesn't open when clicked. They need that another flap in the same level is already open bug.mp4 to open adequately. In my case this occur with "Glyph Browser" and "Stroke" flaps. In previous AFPub versions the same happened to de "Find&Replace" flap. I include a video, if my explanation is not completely clear. (in the video the double-click that closes the flap cannot be correctly seen, but after double click the corresponding flap is deselected)

🤷‍♂️ I only wanted to give u a solution Life is tough

Sure I think objects on a white backgrount should be cut out, silhouetted, before pasting. White is never white, it depends on what you paste and the sftw it uses into screen.

Since introduction M1 and latest version of AFFsuite the sluggish first start of any of the three apps was forgotten.... But NOW with either last 2.2.1 apps or last Sonoma 14.1 OS the snail-first-starts have returned ... like McArthur.... Something wrong? (M1 MacBookAir, 16GB RAM, 1TB SSD filled only 52%, OS fresh installed, AFF apps fresh from AFFStore). Should I try different render methods: Metal, OpenGL, hardware etc.... Not sure if recently some other users have reported the same issue...?

Sorry, NO, Walt, in standard interface guidelines ellipsis after a menuitem is *always* leading to an ampliation of information the app needs to execute the adequate command. In MacOS this has been so since 1984. There is no exception neither option. Otherwise, the absence of ellipsis should (originally) lead to the inmediate execution of the command. This second rule has been broken so frequently that today no one is surprised if after such a no-ellipsis-menuitem comes a info-extension dialog. Is another error, but so frequent that isn’t really of interest. But both are errors. A different thing is that a such minimal question needs to be corrected or is really not necessary, I think it’s not. BUT this interface discipline is law (like other rules), and good practice, in the Mac universe (this is not necessarily so in other OSs, could every interface method or interface manager have its own rules and directives). A good interface design and interface rules are the best way to quick and errorless work. Regards Emilio

Certainly, I said, is known from version 1.x.x. And I know the solution. But years have passed and it's not bad to remember such little things!

This is not really a bug. Appears as an interface error, perhaps. Both [Rasterise...] and [Rasterise&Trim...] menuitems under [Layer] menu have (as seen in the video I send) an ellipsis or three points after the text of the menuitem. Traditionally in MacOs this ellipsis/3points is reserved for menuitems that invoke an additional dialog to select or modify any behavior. But neither [Rasterise...] nor [Rasterise&Trim...] have this. Both actuate immediately. Could this be an interface design glitch? Emilio littlemovie.mov

This is a little error (not especially annoying) that comes from version 1, and continues in version 2. When using dialog for new or edit Text Style, under Paragraph>Tab Stops new tab markers can de defined. In doing that a new line creates in tab list, and in every marker a different option of "Tab stop leader character" can be chosen. To edit this leading character a little button with an ellipsis [...] should be pressed and a small popup dialog appears with the different tab options to be defined (see image 1). There is not possible neither change the leading character nor adding a character sequence (like point-space, to put less dot density in the tab leader). This perverse behavior doesn't happen when invoking the same (or similar) popup dialog directly in the Tab Stop definition in the Paragraph Inspector, where it's possible to type anything as tab stop leader char (see image 2). The straightaway solution is to not define tab stops in text style, then modify it in the inspector, and update the text style endly. So is not severe, but it would be welcome to correct it. Emilio

I think the same... in "Auffüllen" the problem is probably the "ff" signature, that is considered an unique character. You can make a try introducing a soft-hyphen between both "f".... but for automating it... I don't know. Hyphenation in languages-not-english (german, spanish, french, czech or polish, usw.) can be a complex thing....

but... this was not the way version 1.x.x showed the preview for exporting.... well, I've to live with it

Is there a way not to have the "checkerboard" background (transparent?) when exporting a document? having the document's background shown as it is in the edition window (more wysiwyg) Or should be so? Is a bit annoying....

Thanx Both advices were correct. I need to remember when opening older dox

Anyway, thank you! Reconstructing the doc in a new doc created with 204 all works correctly (I have this already done). For one only book is no problem.... but if I need to edit older files, this problem will be a nightmare. Emilio

Old documents prepared with AFPub 2.0.3 when opened in 2.0.4 have lost the capability to alter paragraph leading. When done ex novo in a 2.0.4 doc all goes OK. I send two clips to demonstrate the problem. And also an AFPub doc with this problem present. Need to be corrected? Emilio 203 doc open in 204.mov new 204 doc.mov 20230131 Presentacion Curso ECO.afpub

Oh no, my dear friends Is neither elegant nor adequate to go for extra-app solutions. AFPublisher is a so good piece of software that a extraneous solution is completely out of bounds. (very good piece of sw, despite some/lot of small/no-so-small problems... 🤷‍♂️) AFF should correct its own problems.

Hi There's another problem with interface when using big font size in preferences. I send a video... it explains problem by itself. 👍 captura 2023-01-07 a las 11.28.43.mov

Light interface… less rethinked ergonomically is better a light than a dark interface.... but the dark interfaces are trendy 🤷‍♂️

Answering to @rafa-cerezo in his question about Spanish hyphenation in AFPub v1 forum... "Hi, everyone. Does anyone know if this issue has been addressed in V2 of affinity publisher? Thank you." My answer, regarding version 2 was... "Sorry but the Spanish hyphenation continues to be DRASTICALLY CATASTROPHIC in version 2 Is really unusable, and leads to a complete control and correction of the complete text. Is really, again, ununderstandable because Spanish rules are clear, published, definite, with near no exceptions, and the amount of rules is small. My personal solution is hours after hours of manual correction if the text is long. I won't give examples because those have been given before, also because the errors are excessively evident, and because it appears to be a chronic disease in a good piece of software. So like a chronic patient, is better a good medical control than other drastic or imaginative solutions. Resuming: version 2 is exactly so error-prone in Spanish hyphenation than version 1. Regards. Emilio"