Gianni Becattini
Members-
Posts
348 -
Joined
-
Last visited
Everything posted by Gianni Becattini
-
The printer is asking me for a problem. He says that "The backgrounds are in 0-0-0 RGB (black). This will be 100% black in CMYK, but certain "black" pages also have images with a black background. This then becomes a build-up color black (not 100% K but also some other C, M or Y values) resulting in tint differences clearly visible in the final product." I believe I understand that: I have a black page, obtained with black rectangle over i I placed a photo (see an example below). But which could be an alternative to that? Maybe that the problem was that I have two black rectangles superimposed? Thanks
-
Black is black?
Gianni Becattini replied to Gianni Becattini's topic in Affinity on Desktop Questions (macOS and Windows)
Thanks, very useful, and thanks for the suggestions. I never could have got there by myself... -
Black is black?
Gianni Becattini replied to Gianni Becattini's topic in Affinity on Desktop Questions (macOS and Windows)
Thank you, I understand mainly that there are many things that I cannot understand. For what I know, I never changed Color format. I will be very grateful if you can give me an answer on these point: my document is going to be printed, so the CMYK sounds good to my untrained ears; when I want the most possible black printed, have I to select 0,0,0 (so the black from Apple palette) or what I get with the second little square (231F20)? Forgive my ignorance -
Black is black?
Gianni Becattini replied to Gianni Becattini's topic in Affinity on Desktop Questions (macOS and Windows)
The second little square out of the four on the right, produces 231F20 not black. Thanks for the link, but the problem is not in printing text. -
Black is black?
Gianni Becattini posted a topic in Affinity on Desktop Questions (macOS and Windows)
In the palette small window, there are four small squares: nothing, grey, black and white. There is a reason why the black is not exactly black? Thanks -
I am the one who started this topic, so I cannot be suspected of ...connivance with the enemy 😁 I had a long experience with FrameMaker and some with Indesign and Photoshop and had some endless fights with Adobe. Their products also are not flawless and their support is simply a joke. In addition, I have several paid licenses that I cannot any longer use. I had no serious answers from them... simply they don't register anymore and eventually I gave up. All that to say that Affinity has its (many) problems, first of all APub stability. Recently things are getting better and I no longer regret having used it instead of the Adobe suite (which I still pay). IMHO, however, the best part of Affinity is this forum. Used to the Adobe support ("Did you remember switching on your computer? Many people forget its... Oh yes, it's on, but you must ask Apple, not us..."), here I can find competent people, very quick answering and trying to find real solutions together, without any politically correct attitude. In the end, beside reasonably good products and a fair pricing policy, for me this forum is the best reason to continue using the Affinity suite. Don't underevaluate it, it's a true difference.
-
I hope that the following notes can be useful for somebody. I don't pretend to teach anybody, they are just some notes on my experiences. I have three Macs: A MacBook Pro M2 An iMac i9 An old MacPro 3.2, used only as backup. Each day, at 12 o’clock, it switches on, synchronises with iCloud and execute Time Machine on an internal but logically external drive, then switches off. In this way, also in case of some strange iCloud behaviour, I can go back in Time Machine and restore a lost file. All that has one day resolution, so it does not work inside the last 24 hours. iCloud has always used to be a wonderful thing and a terrible thing. Wonderful, because it allows me to use the two computers indifferently, terrible because from time to time it does something wrong with terrible consequences and I have a very little control over it. In addition it has some un-understandable attitude. For example, after the Sonoma update, on the MacBook downloaded more times all the iCloud content without any reason. Typical problem are instead: Missing sync - this is the more dangerous, because you start editing a non-updated file and then a conflict arises. Sometimes iCloud understands this condition and warns you, sometimes updates the old file with the new, destroying your work. So, always close your work before changing Mac and wait to be sure that iCloud is synced before switching it off. Going on the other Mac, check the file timestamp to be sure that you are working on the right version. Forcing sync - Not always iCloud syncs with the cloud and Apple does not provide a way to force it, but you can “entice” iCloud. Here some tricks: Just duplicate a file on your desktop; Go in Photo and check that photos are syncing. If it says that sync is paused, reactivate it by clicking the reactivate message; Double click the icon on the iCloud line on any Finder window sidebar. Unlock upload - this is one of the worst problems and is very common. iCloud sticks saying, e.g., “Uploading 2 files 0 bytes of 2.1M) This can help: The problem is the dashed cloud (Waiting to Upload). When it happens that locks, it is possible that the problem stays there for days. The only solution I found is to identify the offending files (with the dashed cloud) and then moving them to a folder outside iCloud. It asks you permission and when no other locked file is present, it should say sync OK (clicking on the iCloud Pie Chart icon on a Finder window). At this point you can move back your files to their place and normally they are synced correctly. Another good suggestion is to check the iCloud situation on the web, so that you can understand if the source Mac didn’t sync or the cloud is synced and the problem is in the destination Mac. From the Affinity point of view, it happens that sometime a file is not yet synced and it syncs when Affinity tries to use it. That could trigger some strange situation and Affinity hangs, so that you are forced to kill it, and that, by its side, sometimes leaves something in an intermediate state that will affect future executions (the best in this case is to reboot). The best solution is to work on non-iCloud folders or to be sure that every file is synced before Affinity uses it. Until now, for me, the iCloud benefits are greater than drawbacks. What I cannot understand is why Apple is not interested in iCloud improvements. Few changes could give the user a better information about iCloud Drive activity or, even better, some few control possibilities. But it seems like new backgrounds or emoticons are more requested by the users….
-
Table cell margins
Gianni Becattini replied to Gianni Becattini's topic in Affinity on Desktop Questions (macOS and Windows)
It works, thanks! -
Table cell margins
Gianni Becattini replied to Gianni Becattini's topic in Affinity on Desktop Questions (macOS and Windows)
-
Congratulations, Walt, you won! Almost every chapter developed a second section with "start from page" option. Don't ask me why, certainly I didn't create them. But having removed them, things seem again in the right direction. By the way, I believe I find often chapters which changed from "continue numbering" to "start from". But the important is that I am again in the race... thanks!
-
This is the window of Apub. Note the page numbers: 427, 428 (not shown), 429, 430: This is the produced pdf file. Note that we jump to 437 without any visible reason. This seems to happen without a logic. Page numbers seem to jump backward and forward, even from an export to another. Is it my fault or a bug?
-
In addition: if you clear the target style and then apply it again nothing changes (KO) if you just delete not the text frame but just the text and then you type it in again, it often works OK the CR naming behavior is very strange; see the attachment. Sometimes it include the text after the dash, other times it doesn't - the naming seems to be connected with the problem. If you get a wrong name, it is a sign that something will go wrong. In my cases, it got often the name of another CR. I tried also to delete the pointed text AND the CR. Often, when you try to re-create a new one, the old name is retained even if you change completely the text. In other words, it seems that when you create the CR, some hidden info is retained in the pointed text frame, where probably the problem is. another bad sign is when you get no chapter number in the table in conclusion, to be safe, when you have problems like these, it is better to delete the destination text frame and create it again. In this way I never had problems again (until now 😁). I have verified more times what I said.
-
I believe I found something... I created a new file with just my TOC: same problem I added a true TOC: it worked OK Eventually I discovered that the wrong information is in the referenced paragraph (Main Section Title in my case). Deleting them and creating new ones, the cross-references return to work. But why have they got damaged? And why the "true-TOC" can see them correctly? A reference should be a reference....
-
Some information, don't know how useful. I created a brand new book (by the way: it is very annoying that as default APub sets "start from page number" for each chapter instead of "continue numbering". I could not find a way to set them all, you must go along with each of them). I did not add the "500-Series" chapter, but... even destroying all the references and creating new ones, again appears always the "500-Series" cross reference. So the wrong information must be stored in the other chapters. Perhaps the first one with my pseudo-TOC?
