Jump to content

Last Chance

Members
  • Content Count

    34
  • Joined

  • Last visited

Posts posted by Last Chance


  1. I've been using Photo for some time now, but a few ideas have come to mind that might be adopted (or perhaps they already have been):

    1. The use of the 'Shift' key to retain aspect ratio when dragging, e.g. crop box.
    2. Snap the crop border when exceeding the actual image size, but allow it to exceed the limits if so wished.
    3. Introduce a 'bias' when resizing the canvas. Although the nine individual biases are useful, sometimes I would find it useful to introduce a variable bias. For example, reducing the width, but biased 20% to the right and 80% to the left. Perhaps a dialog with a thumbnail and adjustable sliders. I appreciate that a simple crop does that job, but it's not always easy to do it at a pixel level.
    4. A right-click of the mouse to call up dialogs pertaining to the tool in use, e.g. size, flow, hardness
    5. Make the tabs for each image a set size (not the entire width of the window) and only reducing them when there is a lack of room.

    As I said, these are just suggestions that may prove useful to some users.


  2. With a very simple layout featuring two text frames linked together on opposing pages, an object defined with text wrap has no effect on the second (linked) text frame. Moving the object across to the first text frame and the wrapping works fine.

    • Changing the style of text wrap or its parameters have no effect.
    • Deleting column/page break makes no difference

    Obvious word-around is to use a non-linked page, but this will present many problems in a long document. Currently using v1.8.3.641.

    Any help much appreciated.


  3. 14 minutes ago, OzNate said:

    The way I understand it, the only thing that makes a Designer file different to a Photo file or a Publisher file is the filename extension. Inside they're all the same.

    You can try it if you like. All apps will open all files. The difference you'll experience is how each program works with that file and the options and tools it exposes.

    So that's why it's tricky to add something to Publisher, because you're also simultaneously adding it to Designer and Photo, and on all platforms.

    I can understand that to a certain degree, such as importing a single page Pub file into APhoto, but isn't that making a rod for your own back? Surely it's simpler to convert to a PDF first?

    It seems to me this is a case of "creeping featuritis" and in doing so Serif has managed to excessively complicate the process. Ultimately, endnotes are an essential part of publishing that have no cause to be imported into Photo or Designer and if you're hobbling the software simply to support this "feature" I think the coders need to take a step back and rip out this integrating code.


  4. As has been noted numerous times throughout this thread, the lack of this feature doesn't affect everyone, but there are plenty of users who consider this to be such a fundamental part of DTP that APub is lacking without it. Some of us cannot move forward until this feature is included, making APub more or less redundant.

    @Kevin ScallyI also advocated a few pages before that a partial implementation (of endnotes) would help many users who are in dire need of this feature.


  5. 1 hour ago, Ralph said:

    I feel its like Microsoft saying that WORD2010 cannot read WORD2007 file formats. It just wouldn't be acceptable.

    Perhaps because foot/endnotes aren't supported? How can you import some documents that have these included, when the source program is incapable of supporting it.

    Anyway, I'm with you guys. It doesn't bode well when there is such a stubborn silence when a simple mailshot informing us that it is in progress would assuage any bad feeling.


  6. I'm having to think back, but are you are referring to my much earlier suggestion about exporting the book from MS Word (or whatever) as a PDF and then importing that back into APub? It's not particularly labour-intensive, but as long as you remember that there will be limitations on adding text once it's imported as the footnotes will be difficult to reposition.

    My current book has chapters that have in excess of 1,000 endnotes - that's the problem I'm facing :)


  7. On 4/10/2020 at 8:57 AM, Helmar said:

    @garrettm30 @Seneca @Patrick Connor

    Is it just me or are endnotes just a quasi-clone of a TOC? The only difference: you would set an anchor in the text (already possible), which gets converted to a glyph (shouldn't be difficult), and a dialog box opening to add the respective end-note text. The rest is exactly the same process as the TOC. You'd either insert it or create a new text frame at the end that. And once that block has been created, you can, if need be, still do some style editing.

    Whaddaya think?

    Absolutely 100% correct - my thinking all along.


  8. I find all these ideas very interesting and highly thought provoking. @A_B_C, I must congratulate you on some highly imaginative forward thinking.

    But if I can just interject with a thought: of all the different styles of 'notes', I would think that endnotes are the easiest to achieve as it entails placing a single block of 'notes' at a specific place in the document, i.e. end of chapter or end of book. This, from a personal point of view, would satisfy me and probably many other book publishers, so would it be worth Serif progressing this feature to completion prior to all the other different types?


  9. On 2/29/2020 at 1:26 PM, walt.farrell said:

    Just to clarify:

    • Which Affinity application, and which OS?
    • Are you talking about opening a native Affinity file (.afdesign, .afphoto, .afpub) or a PDF file?
    • And are you Saving it as a native Affinity file or Exporting a PDF?

    It is being experienced in Publisher. The OS is Windows 10 and yes, this is when opening native .afpub files.

    It's easy enough to correct (find/replace), but thought I'd just raise the issue 🙂 Here's a snapshot:

    image.png.a63dd7ff9565ff032b05c1a272d3bae6.png


  10. Thanks all, most helpful. I'll see which is the best option.

    Fixx, I just reckon that some correct auto-correction is better than none at all and a space/en-dash/space is one that should be invoked virtually every time. Date ranges, however, are always wrong (e.g. 1910-1920 should be 1910–1920), but I agree it is difficult for any program to distinguish when the correct instance is required.


  11. Apologies if this feature has already been suggested, or even implemented, but I cannot find either.

    The feature is one found in InDesign and which I found genuinely useful: a 'size to fit' for textboxes. This would cause any text boxes to resize, whether it was an overflow or to shrink to the available content. I seem to remember it was Alt-Ctrl-C, but perhaps someone can correct me.

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