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

walt.farrell

Members
  • Posts

    42,379
  • Joined

  • Last visited

Posts posted by walt.farrell

  1. 2 minutes ago, Eugene Tyson said:

    I made my own topic - nobody replied.

    Serif staff do not necessarily reply to topics in the Suggestions forums, unless they have something meaningful to say.But Serif reads them all, and notes them for future reference.

    Others (us normal users) may comment or not. I, for example, usually won't comment except to offer a workaround or point out a function that already exists.

    In any case, you only posted that 3 hours ago. If it's going to be noticed and commented upon for its technical merits, it's more likely to happen in its own topic.

  2. I suspect that the Insets settings on the Text Frame panel are not working correctly. There are 4 settings (left/right/top/bottom) but they are always forced to contain the same value. E.g., if I put ".2 in" in one of them the others also adjust to that value. As all are settable, it seems  more likely that Publisher is intended to allow non-symmetric values, but it doesn't.

    [Edit: As mentioned below, it was really a UI rendering flaw in Publisher where the link/unlink icon is not shown properly. This should be fixed.]

    image.png.8a7477abd93faee34d4f8f962d3c9563.png

  3. 5 hours ago, Seneca said:

    Contextual menus should definitely be improved upon. That what they there are for.

    I agree. However, there's a conflict that Serif may need to resolve, somehow.

    Consider that with the Text Frame, you have two possible context menus that could be of interest. Currently you get the context menu for the text within the frame, but perhaps the settings of interest to you would be on a context menu for the frame itself. How to show both, or how to enable the user to easily indicate which to show (and, also, to even realize that there are two different context menus possible)?

  4. 4 hours ago, GabrielM said:

    Each time you create a new document, you have to set the working units, and they will be consistent across the tools.

    In my experience the Affinity applications will also infer a units setting from the user's chosen Page Preset in File > New. The A0 through A10 presets default to millimeters and Letter through ANSI E default to inches.

  5. I have a Text Frame that is too big:
    image.png.2a176281b8454e63d1221a8472467eee.png

    I double-click on the bottom middle node to have Publisher resize it to fit, but Publisher apparently makes it slightly too small. Note the "eye" icon for overflow:
    image.png.a7d4bd5a5d1f601d5bb1dae36b80934a.png

    By the way, if the bottom line happened to have a letter with a descender, the frame would not include all of the descender:
    image.png.e65d7fecfd3940d1bc40e0573d7760bd.png

    Note the "y", "p", and "g". But, somehow, also notice that Publisher thinks this one fits (no overflow icon)?


     

  6. 1 hour ago, stmartin said:

    Maybe I'm totally wrong but how do you apply multiple masters to one single document page? And what is this good for?

    In the Apply Master dialog you have the choice of replacing any existing Master that's already applied to a page, or not. If you choose not to, then multiple Masters apply to that page.

    How is it useful? You could have one Master that contains a set of elements that need to be on all pages, and other Masters that contain elements needed for different subsets of pages. The subset Masters only need their unique data, as the document pages can inherit from two or more Masters.

  7. Typically the camera sensor produces more pixels than the manufacturer advertises, but the pixels around the edges may be less accurate than the other pixels. So most software ignores you "extra" pixels and never shows them to you.

    Affinity Photo, on the other hand, includes them so you can make the decision yourself, in case you decide they have useful info.

    That's one possible reason. There may be others, but we'd probably need to have additional info such the lens you're using (if that camera supports multiple lenses.)

  8. 2 hours ago, csbro said:

    Why must I "rasterize" the tutorial image below in order to get the "Flood Select" tool to work, albeit temporarily. 

    {When I use the FS tool without rasterizing it initially selects a portion of the sky (maybe) then the mountain is selected, then the screen goes blank & after re-painting, the entire image is selected.

    After rasterizing the image, the tool selects the sky correctly but then the image goes blank, & after re-painting,  the entire image is selected.}

    1. Is "Rasterize" an integral part of the "Flood Tool" process?

    2. Why does the document image re-paint & re-select?

    1. When you have the image open, look in the Layers panel. Do you have a (Pixel) layer or an (Image) layer? If it's an image layer, you need to rasterize because many tools (including Flood Select) work only on pixel layers, not image layers. The kind of layer you will start with depends, to some extent, on how you opened the image. If you followed the Tutorial instruction and used File > Open I would expect it to be a pixel layer, with no rasterization needed.

    2. It may depend on how you followed the instructions in the tutorial. The tutorial says to click and drag in the clouds, and keep dragging right to increase the tolerance until the entire sky is selected. If you drag into something inappropriate (too different in color) and increase the tolerance too much, you'll select too much (and possibly the entire picture).

  9. On 9/6/2018 at 10:44 AM, TonyB said:

    The option is currently on the "More" button. I think we should move it to the main panel though.

     

    @TonyB: Or, if not the main panel, could it at least be outside of the scrollable set of options on More? Or higher in the list so one doesn't have to scroll to see it? I was convinced I didn't have it, until I looked at the screenshot just above this post, and realized I wasn't seeing the spot color, bleed, etc. settings either because I hadn't noticed the list of options was scrollable.
     

  10. I think you have placed the Table panel in a location (floating over the Pages panel) that Publisher doesn't expect it to be in. On Windows, Publisher provides a scroll bar when there are enough pages showing that they won't fit on the panel, but it seems unaware of other panels that you might have decided to place on top of (vs. docked with) the pages panel. Thus, it doesn't account for them, and doesn't provide the scroll bar if they happen to hide information on the panels underneath them.

    Should it account for that? Perhaps, but I'm not sure whether it's a bug or an intended part of the design. Someone from Serif should be able to say, though :)

×
×
  • 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.