Jump to content

Lagarto

Members
  • Content count

    633
  • Joined

  • Last visited

About Lagarto

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ok, good to know that there is a possibility to customize these things. The palettes work totally wrong in Affinity apps (to my liking) and I would want to rework them and have them autoload as per workspace color mode.
  2. I deleted the goddamn thing (fills.propcol, under C:\Users\<user name>\AppData\Roaming\Affinity\Publisher\1.0 (Beta)\user and restarted Publisher (beta), and now it let me delete it. I do not understand why it did not let me delete / change its values as I checked that there were no problems with user privileges. But I am happy that it's gone now. And now I noticed that I can delete fills.propcol over and over again and get it re-generated on app startup with a new default "Greys" palette that, INDEED, is named now as "Greys" and not "Grays". So can this really be an US/UK issue? I have my user interface set as US English (because already in beta, only US English worked properly with the documentation, and I have never bothered to write those extra u's in words like "color"). But now it works as expected. I can edit any value of the "Greys" palette, and the modified values are permanent. Problem solved.
  3. Ok, will try to locate that... Thanks. Searched now. All instances found have full write privileges for the sign-in account so no problems there. Id' imagine Affinity apps to show an error message if there were problems with privileges. I'll do complete uninstall and re-install of both rhe release and beta versions and hope for the best.
  4. Yes, so it seems. @MikeW can you confirm that you have actually managed to edit the factory default Grays palette? Where are they stored, I could check if e.g. BitDefender could block Affinity apps from writing there (these damn things do these kinds of things at times)... Actually: Have another anitvirus app on my laptop, not BitDefender, which is quite aggressive in this respect. But absolutely no clue why I cannot do this.
  5. Yes, this is completely clear. But based on this thread, I assumed that it is in fact possible to get rid of the "Grays" default palette, or change its values. The UI menu commands also let you assume that this should be possible, as they let you access both operations ("Delete" palette, and "Edit fill..."). Yet I cannot do either. Can this really be done, and if this does not work, what can I do to fix this?
  6. When I try to delete the factory default "Grays" palette, or try to edit any existing color definition in that palette, I cannot have any of the changes to be actually fulfilled. When I try to delete the "Grays" palette, the application asks confirmation whether I really want to do this. I confirm, but nothing is deleted. I can edit any of the existing swatches in the default "Grays" palette eg. to change "Black" from rich black to CMY0 and K100, and press Enter to confirm, but when I subsequently check if the value has changed by re-editing, nothing has changed. What am I doing wrong, or is there something that protects factory defaults from changing (e.g. no write privileges in locations where palettes are stored)? I actually once created a bug report on the case but never got a reply, on absurd UI feature to allow changing of inbuilt palettes (UI allowing to do this but changes never carried out), so based on what is written in this post, I am assuming that this should really be something that one can do. Yet I cannot, none of the changes are carried out. User-defined app palettes can of course be loaded and edited (like your K-only palette, which works perfectly), and no problems there, that's what I have been doing right from the start. It is just that I'd like to get rid of the factory defaults like "Grays", since they do not operate as I like them to operate. That is, delete completely, or change swatch color values permanently, but I cannot do either. Please advise!
  7. Completely agree, because this is how Adobe apps and CorelDRAW and many other apps in the business work. Inbuilt palettes change according to the document main color mode. If you need others, you can always load them, but those that are at hand, work as expected. Having RGB "grays" in e.g Gray/8 color mode, resulting in CMYK rich blacks in PDF export is not something that one expects, exactly
  8. The same on PC, I just have not understood that this is something that stays (in a way that it is clear that swatches added in the doc and app palettes stay), so never have bothered to edit these values! This was good to know, just one thing more where one's own habits make it hard to see that something can be done in another way...
  9. What do you mean, can the inbuilt palette definitions somehow be modified? To me they have been completely useless because I have thought that they are all RGB based. That would be valueable indeed. Can you share the information how this can be done? EDIT: Ok, I see from the post above that you actually just can replace the default with your own, or..???.
  10. Hopefully the key object based alignment (with Ctrl key) will sometimes be implemented in Affinity apps, as well. Much more effective than "last" or "first" selected method (which for some reason is disabled for distribution).
  11. Unfortunately it is not a grayscale ramp, no matter what your document color mode is. It is an RGB based palette in all color modes (even in Gray/8), and when exporting a print PDF where assignments from the "Grays" palette are used, these colors are always rendered as rich black.
  12. I am not sure if I understood what OP meant (I used Google translate), but possibly the problem that when a PDF exported by Desinger or Photo is imported back to these apps, it is not possible to check whether an image on which a PMS color was assigned, has retained its spot color status in exported PDF, because the color assignment is not shown. PMS color assignments are retained for vector objects and shown when using the Color panel, but not for the bitmaps. The point of the post seemed to be that Affinity should provide some means to verify that the exported PDFs have proper color modes and assignments so that the user did not need to use Adobe Acrobat Pro or third party prepress tools (intended mainly for prepress professionals and commercial presses) to check that their PDFs are deliverable. Opening the PDF in an Affinity app (especially Publisher) allows basically checking most of the other things, but not properly the use of spot colors.
  13. Affinity Photo's index image support is basically limited to GIF palettes but color reduction cannot be controlled there effectively (nor interactively), and all images are dithered. The closest that one can get within Photo would be using posterizing and different kinds of blurring filters, resulting in something like this (here median blur is applied): This could then be further manipulated e.g. by colorizing with the HLS filter and manually using brushes.
  14. The package contains filters that are based on image processing techniques of standard libraries that are in the root of other, more advanced manipulations also in "modern" filters that are algorithmically more sophisticaed and can use the power of modern technology effectively. So even if many of GIMP filters are clunky, they can do things that cannot easily be done with mere 24-bit fiters. E.g., the Farbpapier-Collage (“Cutout”) Photoshop filter probably utilizes indexed image techniques built in the app when it reduces colors and abstracts the image, while using the full power of the system for calculations and for varying the effect with user-provided parameters and for smoothing out the jaggies. (The G'MIC also has a clone of "Cutout", that does much the same as Photoshop filter even if far less smoothly and without softening the edges.) Not having index-based tools in the box is a serious shortcoming, but (free) help is not far away, and after a short visit in the wonder world of lesser bits it is easy to make further manipulations with the fluid, modern tools that are available in Photo. The point in including index-based support would be more in providing a toolbox than offering ready-made effects. In creative processes 1 bit and 8 bits are by no means an outdated, "old-school" thingy.
  15. It have installed it now, it really is a treasure chest.
×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.