Jump to content
You must now use your email address to sign in [click for more info] ×

Thomahawk

Members
  • Posts

    303
  • Joined

  • Last visited

Everything posted by Thomahawk

  1. Still, the copy/paste problems make working with tables in publisher very difficult. Whatever I paste in, the text in cells in the next column get deleted. And until now, the only source to get a text list from that end up in individual rows in publisher is from tables in Word. Text lists with line breaks from any other source including publisher itself end up being put all in one single cell. Big problem.
  2. Thanks Joachim. I did try all kind of usual key combinations, somehow it did not work before, until I knew from your post that it must. Now suddenly it does. Much better. Should be the standard setting.
  3. Column Handling problem: In Publisher 1.7.1 tables are very hard to handle. Resizing single columns always affects the columns next to it. This makes it insanely difficult to get to the desired end result. Very frustrating, that all following columns have always to be resized. The handling is furthermore very tense, clicking and moving the column line does not respond fluidly but with lags in response time. Please take an example from Indesign, where the other columns are not affected by a change of one of the columns. Copy/Paste Problem 1: Copy text of all rows in one column. Park it in a text-only editor or in a publisher textframe already shows all text without line separation. When copying it back into new rows, all text lands in one cell. By general standards, copying text from tables always must include line breaks for each row. Copy/paste Problem 2: Delete content of one row (C) and replace it with rows texts copied over from Word, I paste it without formatting into C. All content of row (D) disappears.
  4. Bluring only the edges of images is an important feature I used a lot in Indesign and I really miss it in Publisher. I was looking for such a function in fx - like it is in Indesign - without sucess. Of course, there is the transparency tool, but with that, I can only blur one side. Adding an additional option to blur specific sides with transparency tool or making an fx, both would work, but probably best is having it an fx, makes more sense. Important is, one does not have to go over and do a pixel edit in Afphoto, so as to preserve the original image and being able to try around within the publisher layout. I dont see this possible with masks either, as the seems to be no function to blur edges of a vector rectangle also. Would anyway be too complicated in comparison.
  5. When copying elements from another document, the included dependencies must come with them into the new document. For example the color Swatch that was applied to that element, object or text. This is now not the case in Af Publisher 1.7.1. Despite having set a global swatch and applied to elements, the swatch is not appearing when copying the elements into another document. It seems to be working with text styles, though.
  6. When opening a Document in Designer and fonts are missing, a message pops up to inform that fonts are missing. The next (important) step would be the possibility to replace those fonts with certain other fonts. (I am surprised this was mentioned in the forum only once in 2017)
  7. Nevermind! "Protect Transparency" checkbox was hidden in my top tool bar. Found it by accident.
  8. Lets say you have something cut out and it lays on a layer. How do I now only work within the none transparent pixels (only within the cut out)? In Photoshop I just roughly make a selection around it, move the cut out and instantly the selection reduces itself to only the cut out (including pixels of different transparency levels) now I can work just inside the selection, leaving the cut and transparencies intact. How can I do that in Af Photo?
  9. Not much to say about this. OS X Mojave, Publisher 1.7.1. Left the view in Publisher is all right. Text messed up in exported PDF. Not the first time something like this happens.
  10. Very good, Lmpessoa. Thanks for posting this. I like yours even more than mine. You do really understand what GUI standards mean and how usability and intuitivity work. I dont understand affinity here on this. Not following established standards makes no sense. We have a GUI to use it, not to make it a mess. Right, I did not include the AF photo, because thats the one exception where I prefer the thumbnail. However, I still did not get to work it in OS X Mojave for desktop or symbol view, the right icons only show up in list view.
  11. On Mojave OS X, Designer 1.7.1 This happens a lot, also with other objects. Screen rendering, things disappearing when moving or texts wandering around when moving text itself or another object. See screengrab. ScreenRecorderProject4.mov
  12. This are general design rules necessary for a good GUI, ddeveloped over the past 30 years, to be logical and intuitively accessible. It has nothing to do with personal taste. To toss that aside by making document icons that look like application icons is indeed technically wrong, because it makes things unnecessary disorienting and incomprehensible.
  13. I am used to instantly identify the main layout documents in each project by its icon. That's why I do not save Publisher or Designer files with thumbnail preview. I only do that with images/photos. But as Affinity still does not get the icons right (their doc icons are identical to the app icon, which is against GUI standards) I have created correct icons for Publisher and Designer myself. Attached, you find the icon files for Mac and infos for installation. I don't know if this works the same on Win. It works so far that a correct doc icon shows inside folder lists on Mac. But unfortunately still not on the desktop or in symbol view – I have no clue why this is, maybe someone from Affinity can shad a light on this? Thomas af doc icons.zip
  14. Here is something I don't understand. In this layout some big images are placed. But they are all only linked, not embedded. But why does it need 455 MB then? (The sizes of the .afphoto images combined) Its only the images and a little text on 3 pages. And when I embed the images, the file size is the same. That is not logical at all. Without embedding, it should only be some KB.
  15. okay, I send a test file, only the one image is in it, that behaves rare.
  16. Affinity Publisher is looking promising. But honestly, as experienced designer working with PageMaker, Xpress and later Indesign, I must say, Publisher is just not there yet. Yes, there are functions missing, like edge blurring. But even if working with just what is there, the Results that would have to be sent for printing, are just not reliable yet. Too many things do not come out right in unexpected places. Here is one typical example: On that layout, a hair image (PNG) is placed on the page. As last elements it just happens so to sit over all other elements. The room around the hair is transparent. Now where that transparent parts lay over text, the (vector) text gets pixelated. Things like that can cost one a job. I was lucky to see it before I sent it out. Now as to not risk anything, because it seems one never knows what other surprises come out of Publisher, I have to go back to work with Indesign. And I hate it. But at least I know it works.
  17. I have a afphoto file placed in publisher 1.7.1. Moving it around or zooming page produces strange size changes of the image - see attached video. The image is just plain pixels, no effects or anything, but transparent background. OFTEN it even stucks rendered in wrong size until I try several times zoom or move the page for screen redraw. ScreenRecorderProject2.mp4
  18. haakoo if you mean first that image on the layout select with frametool and then drag and drop, no, thats does not work either. The only things that works is goint into reource list, looking the entry, click replace, search the directory and then select the file to replace it with. drag & drop 10 times less effort if it would work. Psenda - good idea, that would be even better, ask for replace or place new.
  19. Drag and drop images from a file folder into the layout over an existing image MUST replace that image properly. The actual behaviour of instead creat a new image object is not correct.
  20. It is very essential for larger projects to have the ability to save all included files, pictures (newly linked to the publisher document) fonts into a new folder.
  21. Do I overlook it, or is there no "save as package" function in Publisher? It is very essential for larger projects to have the ability to save all included files, pictures fonts into a new folder.
  22. Having the possibility as option is fine with me. But getting an intuitive behaviour that just works how it should in the first place, instead of having to go through several steps first, would be a more user friendly and easier to use approach. This goes generally for many things in affinity products.
  23. "Paste without format" would come in very handy inside the context menu (not only in the top menu) - to paste text without textstyle data.
  24. Strange thinking again by affinity. So its more like a library. That can be useful too. But the most important things for mostly anyone I would say are 1. list of pages 2. list of images those two should be there foremost. But instead, the list of images is hidden 'somewhere' in the menus.
  25. Okay, I see, I have to save pressure curve. Then indeed it sticks to the next path also. Why does this need to be made so complicated. Same thing with every other function in affinity. Its just not intuitive.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.