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

R C-R

Members
  • Posts

    26,305
  • Joined

Everything posted by R C-R

  1. I agree, but at the same time the list of requested features is huge. Many of them have been deemed "essential" or "must haves" by a few users, including many that most users would never use. So this is also about which ones would benefit the most users, as well as how much work it would take to add & debug them without destabilizing or otherwise compromising the features we already have. I suspect if everyone compiled a list of their most wanted features & improvements, there would be very little agreement about which ones are the most important.
  2. Unfortunately, you can't save different workspace configurations & recall them. This has been requested by several users. The developers have said this may be added to some future update or upgrade, but there is no guarantee that will ever happen. However, you can configure panels in many different ways, including 'undocking' any of them so they 'float' in the display, grouping them differently in the left or right Studios, & enabling/disabling individual ones from the View > Studio menu flyout (& assigning custom keyboard shortcuts to them so you don't have to go to the menu to do that). You can also double-click on a panel's or panel group's name to minimize it to just the title bar & single click on that to expand it back to its previous size. The main toolbar & the Tools panel can also be customized to include, exclude, or rearrange its items, & you can also assign custom keyboard shortcuts to activate the tools. All these configurations are 'sticky' between app launches, so while there is just the one workspace configuration, at least you don't have to keep setting it up repeatedly.
  3. You did not say if you were using Affinity Designer or Affinity Photo but for both there are "Lock" & "Unlock" items in the Layer menu & a Lock icon at the top of the Layers panel. You must have a layer selected to lock it.
  4. You should be able to get similar effects using Affinity Photo's Channel Mixer adjustment, for example with settings like this: I suggest experimenting with different Blend Modes & Opacity settings to see what works best. Average seems to work fairly well at 100% opacity on the images I tested with; while Screen, Add, Glow, etc. were much too strong & artificial looking unless I reduced the opacity considerably.
  5. SVG files can include a mix of bitmap ("pixel"), vector, & text objects so what you get on import depends on what each file contains.
  6. But do you know anything specific about Affinity's code or how it is optimized for the three very large & complex operating systems the Affinity apps support? If not, how could you possibly do anything besides guess about how much work it would take to 'puck' whatever you consider to be the "low hanging fruit" Affinity has yet to do?
  7. This advice is worthless. DPI is irrelevant for web pages; what matters is pixel resolution (how many pixels the image contains). If your thumbnails contain too few pixels, they will look pixelated regardless of how much or little they are compressed. There should be very little loss of detail at 85% or higher JPEG export quality.
  8. What specifically do you mean by "low hanging fruit" & how do you know how much work it would take to 'pick' it? Do you have some special "insider" knowledge about Affinity's code you would not mind sharing with the rest of us? Consider that Affinity is doing something that almost no other company has ever tried to do, that being a single "native" file format that any app in the suite can open without conversion or loss. Think that might possibly move the 'fruit' just a wee bit further up the tree? What about serialization or maintaining high memory efficiency or other "under the hood" things we might not know anything about that contribute to a user experience that many have commented make the Affinity apps fun to use?
  9. But not every company requires a "membership" to continue to use its products, particularly when many of its longtime customers have been very vocal about how much they dislike that.
  10. Apologies for continuing with this in yet another tl;dr post but maybe the following will make clearer what I am talking about. Please just ignore it if this is of no interest to you. Consider this RTF formatted TextEdit document & the symbols it uses for indents & tab stops. Compare that to the raw text in the file (here displayed using TextWranger to make everything visible): In a RTF document, everything preceded by a backslash is a "control word." Consider the line "\pard\tx2820\li540\fi740\ri720\pardirnatural\partightenfactor0" in the info section. "\pard" denotes the beginning of a paragraph & "\li540" & "\fi740" denote its left indent & first line indent respectively. (The numbers are in "twips," the RTF unit of measurement equal to 1/20th of a point.) If the paragraph had included tab stops, the RTF document would have included control words for them as well, like "\tx600" to specify a tab stop at 600 twips from the left margin. Other control words define the kind of tab stop. (For the few interested in such things RTF specs can be found on the web, for example at http://latex2rtf.sourceforge.net/rtfspec_7.html.) From all this I hope it is evident that at least for RTF or anything else that uses similar "under the hood" methods for controlling text positions that tabs & indents are completely different things, even when they have the same effect.
  11. How do you know that there is an "automatic" tab stop at the left indent & it is not just the first line indent setting that is positioning text as if there was an actual tab stop at that setting? It seems to me that if it really was an actual tab stop, even if it was automatically created by the software, it would show up in the list of tab stops for that paragraph. Do you see that or any other indication it is not simply the first line indent function being applied?
  12. No, all that does is insert a tab character in the text at the current text insertion point. It has no effect on the first line or left (or right) indent setting of the paragraph, & it will not do anything to position the following text unless a tab stop is set in that paragraph.
  13. Do you mean pressing the Tab key on the keyboard or the Add New Tab Stop button in the Paragraph panel? Either way, neither one sets any of the indents (first line, left, or right). Each paragraph will have exactly one of each type of indent, but a paragraph can have as many tabs & tab stops as you want. Tabs & indents are not the same thing, nor does one substitute for the other.
  14. There is no tab stop so of course inserting a tab in the text won't do anything besides set the text insertion point to the left or first indent of the paragraph. What did you expect to happen? Edit: an indent is not a tab. Is that maybe what is confusing you?
  15. Your screenshot of the Paragraph panel still does not show that you have set any tab stops. Pressing the tab key does not set a tab stop. It just inserts a tab character in the text at the insertion point. If there are no tab stops set in that paragraph there is no place for it to 'stop' (so to speak) & the next character you type will just be placed wherever the indents, margin, & justifications of the frame dictate. In your first screenshot in your last post, it looks like the insertion point is at the beginning of a new line. If the Paragraph panel in the next screenshot is what it looks like with that insertion point active, you do not have any tab stops set, at least for that new paragraph. If you did, the tab stop would appear as indicated below: The Paragraph formatting online beta help topic is for Macs but it should be the same for windows. Note what it says about how to add tab stops. If you never click on the Add New Tab Stop button, no tab stop will be added. That button is immediately to the right of the tab stop input box, set to "0 mm" in your screenshot.
  16. I cannot duplicate than in any Mac version of Designer or Photo. Are you sure you are not confusing the default tab stop setting with actually setting a tab stop?
  17. I don't see any problems using it with a Mac. On the U.S. & possibly other Apple keyboards, the bullet character can be entered directly by typing the 8 key with the alt/option key held down (Shift+option+8 enters the degree symbol.) But regardless of that, did you see what I wrote about there being no tab stops in the screenshots? If the section below "Tab Stops" in the panel is empty, there are no tab stops set in the currently selected paragraph(s). The text field with the up/down arrows next to the two buttons does not indicate any tab stops have been set, only the value (or increment) that will be set if the add stop button is clicked.
  18. Jack, be sure to read & heed the info in the first post of the beta thread. As it says, saving files in the 1.6 format may make it impossible to open them in 1.5 versions, so it is a good idea to make backups of any of your 1.5 version work that you want to test with the 1.6 betas.
  19. Which Affinity app (Photo or Designer, trial or retail, Mac or Windows) did you download & which tutorial did you watch?
  20. Hmmm. I just checked again in Affinity Designer 1.5.5 for Mac, & in the AD Mac customer beta & in Affinity Photo 1.5.2 for Mac. All of them show the same behavior -- when I set the Left Indent value the First Line Indent value is automatically set to the same value. That may have happened for @modiophile because his screenshot shows both set to the same value: I don't see the first (or any) tab being set automatically to anything other than the default tab stop value. Speaking of that, in both your & modiophile's screenshots, it does not look like any tab stops have been set. The "0.02 in" shown is just the default value that will be used if you click the "Add New Tab Stop" button to the right of that numeric entry field, but until you do that, the list of set tab stops on the left will be empty, signifying that no tab stops have been set. That is probably why your screenshot doesn't match the indentation of the text. I also noticed yet another oddity in the Mac Paragraph panel: when I set the Left Indent to some value & the First Indent adjusts to match it & then reset the First Indent to zero, if I then decrease the Left Indent value, the First Indent value adjusts proportionally to a negative value: However, this doesn't actually create an 'outdent' & the moment I touch that value it reverts to 0 or a positive value. So there is definitely something funky going in that panel, at least for the Mac apps.
  21. @toltec On Windows, do you see the same annoying behavior I mentioned above about setting the Left Indent also setting the First Line Indent to the same value, which is what I see on my Mac? I suspect this is by design, based on the assumption that if a paragraph's left indent is set to >0, then the user usually intends for first line to be indented by the same amount.
  22. You may find it helpful to watch the Affinity Photo - Clipping vs Masking video tutorial, particularly at about the 2:30 mark.
  23. @modiophile Which version of Designer & which OS (Mac or PC) are you using? In your screenshot, it looks like both the Left Indent & First Line Indent are set to the same value (0.118"). Apparently, at least on Macs the First Line Indent is automatically (& annoyingly!) set to the same value that you enter for the Left Indent, but you can reset the First Line Indent to zero afterward to fix that. Also, if you have already entered text & it spans more than one paragraph, make sure all the paragraphs are selected when you set or change values in the Paragraph panel, or those values will only apply to the currently selected paragraph.
×
×
  • 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.