Jump to content


  • Posts

  • Joined

  • Last visited

About rjvela82

  • Birthday 02/02/1982

Profile Information

  • Gender
  • Location
    New Jersey

Recent Profile Visitors

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

  1. The bug is on Windows for not including it. The Text Frame is formatting tool for text layers, so it should absolutely be part of Affinity Designer.
  2. Thanks for pointing out the Staff badge. Goes to show I'm not here on here much. No I definitely I'm not married to this idea! There are different ways to accomplish things, and sometimes keeping things rudimentary remains the best course of action. I work for a software company and telling customers that databases don't work like the human brain is a common response but you can't blame people for venturing to cut corners.
  3. Everybody, look.... I couldn't believe my eyes. Only found it because I'm trying to do text on a curve path. Clicking random buttons and the Text Frame shows up. Case closed.
  4. @Old Bruce are you Serif tech support ? Not relevant, just curious. Yes, bleed is paper that is trimmed off and used to make sure color bleed or lack thereof results in a good print. The text frame panel allows for fill color to apply on a text frame, I'm sure you know that by now. If a text frame with color is used to go into the bleed, than that text frame's inset must account for the bleed to improve alignment with other aspects of the software that facilitate a user's design and workflow like grids, rulers, margin guides, etc requiring the user to do the extra math on every edge of a text frame that borders a bleed. To answer your question: The value is applied to each inset in the text frame when the option is toggled on/off including insets with a value of 0. It would work like this: Left Inset + Left Bleed = new adjusted Left inset, Right Inset + Right Bleed = new adjusted Right inset, and so on.
  5. Bleed is somewhat of a variable that could change based on the printing job and this could adversely affect a user's workflow since they are now forced to account for bleed on every inset of a text frame bordering bleeds within the whole project. It would be great to have an option in the Text Frame panel that adds all 4 bleed values as insets using a single option "Add Bleed Insets" or similar. This value would stack on top of the main Inset settings. The benefit of this option would allow a user to change Bleed which is at the Project Setting level and have complete confidence that it won't be necessary to adjust many text frame insets settings in the project. Instead, the only required step is for the user to adjust their text frames height and width to border the new bleed. That's it, everything else would maintain its intended alignment. Example: As you can see in the screenshot below, the user has created a comfortable grid to work with. The inset settings they would naturally be inclined to use would be based on their grid, but the bleed is now forcing the user to adjust the Text Frame Insets to account for it. The work involved (a little bit of arithmetic), for every edge of a text frame for how ever many text frames are found in the project make the transition to use another bleed setting for the project a daunting task. If they had such a setting and applied it as they were adding text frames, then all they would have had to do is adjust the current text frame height or width and everything would be aligned as intended automatically. One last clarification: Yes, only one option is needed, and when used all 4 bleeds are added as inset in the Text Frame. It's uncommon for bleed settings to be different across all four edges. Moreover, you will notice there are more options in the text frame panel for adjusting the relative height of a text such as baseline and vertical position but these would be supported by such a feature, not reduce their usability.
  6. I feel the same way as you, but the gradient tool is a rudimentary part of Affinity Designer. The community has been asking for it to be overhauled, reimagined, reinvented, whatever and it needs to be. Consider the fact that 4K monitors are now more prevalent than ever and on such a high resolution screen you are forcing users to focus in one little area of the screen. It is not a good experience. This brings up another grievous point I have with the Gradient tool. An issue where the Opacity is not being maintained upon color change. A user has to re-initialize the opacity either in the value field or the control to reapply the desired opacity. Whatever programming reasons existed for this, it doesn't matter because there is no reason to constrain the user's process by forcing them to select the color before selecting opacity. I don't like getting into programming discussions either, hell I dont even like having to come to the community to complain, but its a given that development frameworks provide toolkits to address these scenarios but developers sometimes unwittingly choose to be hyper-efficient and will refuse to believe that some level of verbose programming shouldn't be handled with garlic and stakes to someones heart. If a Serif developer is reading this, pls consider addressing this problem. The proper fix is that the current behavior be exactly maintained as it is now, and the only difference is that the user no longer needs to re-initialize the opacity value in the gradient nodes. In other words, don't pass the opacity directly to the color selection, handle so only the gradient tool will show nodes with opacity.
  7. No because the 100 value is a constant. Moreover, the code is already checking which ID the node is along with its position when copying so the scenario would be considered in compliance.
  8. I'm not sure you're a developer at Serif but a proper Copy function of the 100 value, means creating a new insertion in between the last stop or 0 whichever comes first and the 100 location with the Color value maintained from the 100 End location.
  9. I have to do a Reverse, then use Copy on the Start Node, and then click Reverse again.
  10. Problem: The page list panel only displays Page #s alongside their thumbnails which means users either have to look at thumbnails carefully or remember page numbers. Not a huge deal breaker, except when there are projects that are not page number based. For example a set of sales sheets where each page might be a product. Currently, users must remember which product is a certain page number. But you might say they can use large thumbnails to navigate the project, true but its not that helpful since its common for these kinds of projects to have pages that resemble each other. Suggestion: Have an option in 'Document Properties' that enable Custom Page Names. This option will then display the Name field in the Spread Properties for regular pages that users can edit the page names, (the way it is in Master spread properties). When enabling: the user should be warned that Page name labels will stop updating automatically when moving pages around in the project. When disabling: the user should be warned that Page name labels will be overwritten by Page numbers. Then as pages are moved around again, each page name will update with the number like before.
  11. Okay I get it, I guess I'll use the "Edit in..." options to switch between apps when I have to touch the text frame panel. Thanks.
  12. Back on here squeaking this wheel. The Text Frame tool deserves to be in Designer. Adding it no way overlaps with Publisher since content is managed completely different in both apps, pagination vs artboards. Pls add this to Designer!
  13. Welcome to the dark side! There's an app called PixelSnap that is 'pro level'. You can also find this app for free on Setapp, a $10 subscription services that lets you download any number of apps. The apps are curated and I personally use 26 of them, that's how useful they are to me. I highly recommend trying it out.
  14. I think the Frame Text Studio would be a great addition to AffDen because they are two vastly different workflows in need of managing text. AffPub of course manages workflows through pagination, but AffDen manages workflows through artboards. Each app serves hugely different purposes, one is flat and one is hierarchal. There's no real reason to be restricting AffDen from providing a way for text content to be managed with the defined set of parameters that is possible and available with the Frame Text Studio. Pls add it to AffDen!
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.