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

Search the Community

Showing results for tags 'formats'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 9 results

  1. It's my own mistake, but I upgraded at significant cost to myself and my situation in the hope that the long requested feature of DDS support in Photo/Designer would have been done as part of the 2.0 feature set. Yet to my frustration I find that it's still been ignored. This is such an important feature for those working with games on cross-platform that I can't underestimate it's significance. PLEASE ADD SUPPORT ASAP.
  2. There's been a few threads on these forums about JXL but no real feedback from Serif on their plans other than an answer that it might happen some day. I really do think Serif should consider JXL seriously and be a first mover in regards to this format. The reasons for supporting JPEG XL is many, a new actually great format for >8bit final export, possibility of lossless quality, transparent conversion to JPEG for compatibility, better compression and more. Some sources: source 1, source 2. The reason I think Serif should be a first mover in regards to this format is that no new format will ever get the chance at dethroning JPEG from it's role if nobody ever implements it in their software. Browsers do support JPEG XL (JXL) but the enablement is hidden behind browser flags currently, partly because nothing else supports JPEG XL at this time.
  3. I reported this to Serif via email (I wanted to send a screen shot and chose email because I can't add screenshots here due to some forum bug). If anyone has the time to test this, it would be useful to know if anyone else can replicate it. The problem: trying to update an existing paragraph style fails because the "Update <name of style>" command is absent from the menu where it's expected. Procedure: from https://fonts.google.com download the font named Lobster (the one having only a single variant, not the similarly named font having four variants). This should display the font: https://fonts.google.com/?query=lobster (Not my favorite sort of typeface but it's called for in a class I'm taking.) After installing the font: In Affinity Publisher, use the Artistic Text tool to create a small amount of text and format it using the Lobster typeface. Go to the Text Styles panel, locate "Heading 1," and right-click it. If the bug occurs, the menu will not contain Update Heading 1 at all. In my test document I then added text in a new frame, this time using the Text Frame tool. I assigned Arial to the text — and again the Update Heading 1 menu item did not appear. I deleted that text frame, made another one, formatted the text inside it using Arial—and this time the Update Heading 1 menu item did appear. In what way were these two operations different? I have no idea. To keep testing...I added another text frame and used a typeface called Aleo (also downloaded from https://fonts.google.com). With that block of text selected, the Update Heading 1 menu item does appear as expected. This is baffling. Is the disappearing menu item caused by a font problem of some sort? Or is there something I'm doing wrong in assigning formatting to text?
  4. Hello ! Quite a few times, I find myself in a situation where being able to handle/modify .afdesign and .afphoto programmatically would have been really handy. However, after a couple of google searches, I couldn't find any information about those formats. I've tried to decompile the AD and AP apps using decompiler such as dotPeek and dnSpy, but didn't make any progress. Analyzing the files with binwalk or strings was of no help either. Now, I'd like to develop a tool that would generate .afdesign files based on user input, and it is impossible to do without even any basic information about this format. Anyway, as you've probably guessed, I'm posting here to ask if we could get some information about the files formats. I know writing documentation for a piece of software instead of working on new features or patching bugs can be really boring and time-consuming, so I'm not asking you for a full-blown documentation, but at least a sufficient level of information to work with those files programmatically and maybe being able to create/modify them, that may include the different memory sections/segments, how shapes/colours/palettes/text/filters/effects/references are stored, etc... I know it's probably not gonna happen, because it's too time-consuming or costs too much, but I sincerely hope that it will be a resource soon available to the community. Thanks for reading, waiting for your reply.
  5. I would love it if Affinity Publisher outputted all standard eBook formats and allowed for interactivity in eBooks where supported by file type. Interactive features would include: popups with texts animation sound files ability to turn features on or off within the book page jumps on choice Since Affinity is the future and interactive books are the future, seems a perfect match to me. Right now, there are some add-on interactive features programs or software that are limited to very specific outputs; Kotobee, iBooks Author, Aquafadas, inkling, Interact Builder, DemiBooks, Atavist, Talespring and others. My perfect workflow would be to draft the book, illustrate it in Designer (with Designer allowing frame animation), design in Publisher including any interactivity, and export across a wide variety of formats. I realize this is a huge technical challenge, but it is my fantasy workflow. Thank you.
  6. Table Formats tab: when I try to modify a table format and either click or hit enter/return, it forces me to click or enter/return twice before the dialogue will close out, but then it generates two instances in the Table Formats list. The screen clipping was the result of only three attempts of modifying and saving a table format. As you can see it generated two per attempt.
  7. I often have to create a lot of files in various formats for my customers. What would be a really good feature would be a "Bulk Export" Dialog, were I can choose: the formats I want to save with checkboxes The location to save A name for the files I think the best way to do this regarding settings would be to take the last export settings from the regular export dialog.
  8. I am Beta testing Affinity with a view to upgrading to it from PagePlus, but there seems to be no way to open PagePlus files. Is this intentional (if so seems short sighted)? D Green
  9. When I save to other formats, Tiff, Jpg, Psd, Pdf and direct it to a file folder nothing seems to happen and the file does not show up in the folder. What am I possibly doing wrong if anything? :wacko:
×
×
  • 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.