Jump to content

fde101

Members
  • Content Count

    3,388
  • Joined

  • Last visited

Everything posted by fde101

  1. This thread is yet another duplicate of several others, most notably:
  2. From the application menu, choose Preferences, navigate to Keyboard Shortcuts, and click Apple Defaults. That will reset any customizations you may have made to your keyboard shortcuts, but will set most of the text editing keys to be the more correct ones for working on a Mac.
  3. Serif removed the roadmap thread as it was causing more problems and complaints than it was helping to solve.
  4. Another way to handle this is to take the text from one of the photos and add it to your Assets panel; then you can simply drag that onto the next photo and edit the text, formatting intact.
  5. All, there is really no point to all of these "me2" posts and the like - check the "Recommended" post at the top of the page: they are already working on implementing this. Step back and give them time to do it right. It's coming.
  6. I don't see this option either - you can choose single or double underline and can change its color. This is a great feature request and I would like to see more options for this too. Currently you can set a "cell stroke" which has similar options but strokes around the entire characters; it would be nice to have a popup like that to control each of the underline and the strikethrough as well... and maybe options to control the spacing between the text and the underline, and spacing between the two lines when doing double underline or double strikethrough? You could manually position a line underneath the text and anchor it to the text so that it moves along with it, but that would be a bit extreme if you have a lot of these to do.
  7. Hi @Lizibulle, welcome to the forums! Division is already there (it is labeled "Divide"): I had to look up what the Outline button does in Illustrator; I agree that one currently doesn't seem to have a direct equivalent in the Affinity products. The closest would probably be Expand Stroke followed by Divide, but I don't believe that would be exactly equivalent?
  8. A bit lost on what you are expecting here... you can just add the desired content to the master page you are using.
  9. Don't forget Apple has been through this before... twice. They switched from the 680x0 series processors in the original Macs to PowerPC, then from PowerPC to Intel. They also made the quite major change from classic MacOS to the UNIX-based MacOS X, which is derived from OpenStep (originally NextSTEP), which is a rather major shift itself. I wouldn't count them out so quickly. https://appleinsider.com/articles/19/04/08/steve-jobs-predicted-the-macs-move-from-intel-to-arm-processors
  10. I absolutely agree with this, but it doesn't matter how quickly you can produce bad results. The real problem with the colors in the surrounding UI is not how they look, but in how they change the way your document looks. Too much contrast will do this as well. The suggested changes as demonstrated in the sample images have the potential to cause the user to misjudge the colors of the document, and that would be a problem in an application whose primary function is design work, in which color perception commonly plays a big role. Yes, the visibility of which tab is active should certainly be improved - I have struggled a bit with that one too so I do know what you are saying - but it needs to be done carefully, so as not to compromise the accuracy of the user's color perception.
  11. Hi @sujithta, I'm not exactly sure what you are requesting here, and using overly large text in your post doesn't make it any easier to understand. To create a mask from a pixel selection, you can choose Layer -> New Mask Layer, or click the Mask Layer button along the bottom of the Layers panel. If you have an existing mask layer and select it, you can use the brush tool (for example) to modify that mask, and it will be restricted to make changes within a pixel selection if you have one. Option (alt) clicking on a layer (on the Mac at least) takes you into isolated editing mode for that layer, hiding the other layers while you are working on it. Shift clicking a mask layer toggles it on and off. To invert the mask, select it in the Layers panel and choose Layer -> Invert (menu bar), or use the keyboard shortcut (Command+I on the Mac).
  12. Yuck. The suggestions above look ugly. I agree that it could definitely stand out better, but this is an application for design-oriented people - it should still look appealing. Also, it should not stand out so well that it draws attention to itself (and thus away from your work). @Jowday definitely is correct that the use of color here would be a big problem and needs to be avoided. Not only is it a potential distraction, but the whole point behind the neutral gray interface is to avoid throwing off your perception of the colors in the document you are working on. Colors in the user interface surrounding the document are likely to do that, particularly if as prominent as a tab just above it. Sharp differences in brightness could similarly throw off perception so the whole near-black vs. near-white thing is a no-go as well.
  13. It has been explained on numerous other threads why this is not practical. I would not expect this to happen, ever. Not practical outside of document palettes. They are already created as global by default when using the commands that create them as global swatches. Simple stuff. I agree that these would be very nice... #12 was already brought up on other threads though. This has already been discussed on numerous other threads. That is because the eyedropper is picking up the color from the display on the screen, not from the document. It always captures in RGB from what I can tell, and can pick up colors that are from other objects on the screen which are not actually part of the document (from the UI itself for example, or even from outside of the Affinity applications). Finally, a few reminders from the guidelines which are not being followed here:
  14. I have it sitting next to my keyboard in place of the mouse. Once in a while I still connect a mouse for one reason or another, but most of the time it is the keyboard and the tablet.
  15. I use a Wacom tablet on my Mac, the newer editions of which behave like a massive trackpad when used with your fingers. At that size you can even use four or five finger gestures if you are so inclined to learn them... plus you get the pen to use for drawing and the like. Having gotten used to that, a mouse feels very limiting. I generally plug one in for playing certain games that don't play nicely with the tablet... but for doing "real work" the tablet works best for me so far.
  16. A Photoshop document may contain images, but it is not itself an image according to the Affinity products. Same with Affinity Photo documents - they are treated as documents, not images, by the software. Note that I am not arguing against providing the sizing information for embedded or linked documents - if it is provided for images, it should likely be provided for embedded/linked documents also, for improved consistency - but I do agree with the delimiting of PSDs as documents rather than simple images.
  17. If you are referring to the flood fill tool, there is one in the pixel persona for working with pixel layers (which is the equivalent of what you would be doing in MS paint too).
  18. The virtual paperwork involved in implementing a new feature within the product of an organization often adds multiple times the amount of work to a project that the actual coding does. Add to this the need to update the product documentation (in multiple languages), the time taken to test the feature (and to verify that adding it did not break something else), possibly determining how well the selected modifiers work across different keyboard layouts... Multiply parts of that by the three platforms they are supporting if the input system for the modifiers is not sufficiently well abstracted by their framework. Suddenly that 1 hour coding change could amount to a several days or more of work when spread across multiple individuals involved in making it happen (developer to write the code, testers, documentation team, management...), depending on how Serif structures their project internally, assuming it was even that fast of a change to begin with (which is by no means established here - only Serif knows how this is coded internally or what it would take to add this feature).
  19. Interesting find. If I set the spacing to anything less than 4 pixels the grid becomes invisible regardless of zoom level. I suspect this should really be in the bug report forum?
  20. PSD files, like PDF, are considered embedded documents (or linked documents) rather than images, and this information is not currently displayed for embedded/linked documents. With images (JPEG, PNG, TIFF, RAW files, etc.) this is displayed in the context toolbar.
  21. Yes, and those of us who have been around on the forums (or who actually take the time to read the online help) know that, but someone who randomly stumbles on the program on one of the various app stores (or the Serif web site) might not be expecting to need to do that. If they create documents which are then made public it has the potential to make their name publicly available in a manner they might not have anticipated, and depending on the nature of the material and its distribution, that can sometimes be a bad thing.
  22. How large are the files? Try having Activity Monitor open (under /Applications/Utilities) while those "slow" operations are happening and watch to see if the CPU usage ("System" or "User" at the bottom of the "CPU" tab) or I/O bandwidth ("Reads in/sec" or "Writes out/sec" at the bottom of the "Disk" tab) has a significant spike while that is going on. That should help to narrow down where the bottleneck is.
  23. I personally think they should default the title and author fields to blank.
  24. Anything that can be done layer-based can also be done node-based and then some. There have been indications elsewhere on the forum that have suggested that the engine behind the Affinity products is in fact node-based behind the scenes (the layers you work with in the interface are translated into nodes to be rendered) so I don't think you have a case that being node based automatically makes it slow. I personally find node-based interfaces to be VERY intuitive to work with. That said, I also think node-based interfaces are most optimally applied to non-destructive data pipelines, while the Affinity products by nature are organized around destructive editing, particularly of pixel layers, so I am suspect of this request as a general interface mechanism for the Affinity products - though an image processing filter from within the Affinity products that allows a node-based approach to defining a custom filtering algorithm could potentially work quite well.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.