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

rubs

Members
  • Posts

    645
  • Joined

  • Last visited

Posts posted by rubs

  1. Today's tools accept most standard bitmap formats

    It depends of which tools you are talking about. BMP is an old format and has no use on the web, agreed. But its most distinctive characteristic is that it is super simple to implement as it is just an uncompressed bitmap (at least in the original specs) with a very small header. As such it is blazingly fast to display since it requires no extra decoding steps. This is probably the reason it is still used in some gaming platforms, specialized software and embedded hardware like some POS terminals my company worked on.

  2. Hi,

    We can discuss as we like, but I believe there is no interest from Serif to pursue this and other issues. We would know, if they bothered to talk with us. I recall a time when they were actively responding to customers via this forum, which was very nice. But this was several years ago: they stopped doing it all of a sudden. And it's hurting their business, no doubt. My company has switched to Figma already and we're not looking back (here's my comment from last year). Figma does not completely replace Designer and they are already semi-deaf like Serif, but their software performs much better for large designs and is not ridden with bugs.

    Have luck,

    Rubem

  3. Hello @Fizmarble,

    On the contrary, BMP is one of the easiest image formats to deal with because it is quite simple and not compressed (at least by default). It is just a pixel map with a simple header and that's it. The first time I implemented BMP I did it in straight C, which is now considered a very low-level language, using the already excellent documentation available from Microsoft. Today things are much easier because there are plenty of third-party libraries (several of them free and/or open source) that will take care of the task for you.

    The reason Serif won't implement it is not technical at all, you'll have to look elsewhere.

    Best regards,

    Rubem

  4. On 12/15/2020 at 3:06 PM, vaporizationator said:

    I'm so surprised

    Don't be, it's just the way Serif is. They had the most promising product once (AD 1.5-1.6), but now they are always busy doing something new. They stopped fixing things and listening to users several years ago. I keep receiving forum notifications, but all I see are old issues like this one never getting addressed and new bugs popping up all the time. I gave up already, my company and myself have switched to Figma for all new designs. No regrets.

  5. On 4/11/2020 at 9:21 PM, Highvoltage said:

    Switch to Figma. You won't regret it

    My team is already using Figma for all new projects, and it's great. We use AD still because we have a lot of documents already produced in it, but we are making the switch fast. Unfortunately this is what happens when a company refuses to hear its customers and won't care about fixing severe bugs like these. So here Affinity Designer is the new Xara Designer: It's used used only for legacy work.

  6. Just now, Seneca said:

    The only way to put this feature on the map, as it were, is to ask for it. So, I would encourage you to post officially request for it in the appropriate Designer forum.

    Oh, I've done it many times already. Same thing for those bugs which are there for ages. To be fair, some of the bugs I've reported were fixed and suggestions I've made were implemented in the past, but Serif is way too slow.

    @Jens, if you read carefully above you'll see that my main issues are broken features like constraints and incredibly bad implentations (exclusive to AD!), like non-visual tab settings and no image compressing. I agree with you on "distort / perspective", though :D

  7. 6 hours ago, Seneca said:

    Could you explain what you mean by that, please?

    Sorry, not clear. I mean a visual ruler for adjusting indentations and tab sizes.

    image.png.dacafec0fef3b008faf421e271c16755.png

    image.png.e1d013283d56d9662505f96060a401fd.png

    The examples above are from vector drawing programs, and of course any text processor (even MS WordPad) has it. For my screen mockups in AD, I avoid using tabs altogether since they are so difficult to work with. I don't know about APub, though.

  8. Serif working on a new AD version is always good news. At the risk of repeating myself for many years (sorry guys), however, I wonder if this time at last they will address those pesky old bugs and obvious omissions. I'm talking about buggy constraints / symbols, bloated embedded images, unselectable objects, slow text editing, missing visual tab adjustments, no distort / perspective, and many, many more. At least as of build 1.8.0 these problems are not yet being addressed. :(

  9. 3 hours ago, Arun Sarkar said:

    Personally I think it is just a commercial decision to protect each application.

    That's not necessarily bad. Serif must make a profit in order to stay in business. And artboards are powerful enough for most design tasks.

    When I started using AD I thought I would miss pages (coming from Corel and Xara), but today I find artboards better and more flexible. They could be improved in several ways, but this is a separate subject.

  10. 6 minutes ago, Dan C said:

    The error message is due to Pixel data missing, this doesn't happen very often but when it does there's no 'trail' left in the files data to explain why.

    I've manually found the affected layers, these were 2 pixel layers on Artboard 020 - Serviços. After removing these 2 layers and saving the document, the error no longer appears when opening.

    For our future reference and so was can narrow down on what may have caused this, could you please confirm;

    1. Did you even receive a file saving error with this document?
    2. Has the document ever been opened in Publisher beta, or any of the other 1.6 betas?
    3. What was the contents of these pixel layers? 
    4. Had the contents been opened or edited in an external app (either Affinity or otherwise)?

    The more information you can provide, the better - many thanks in advance!

    The file was made in a previous 1.7 Beta by a colleague, but he doesn't remember if there was any saving errors. We never tested Publisher, nor opened the file in any other app then Designer. What might have happened (can't be sure at this time) is that this particular file was created by editing a previous AD 1.6 document. Fortunately we keep several previous versions of all our work.  I've just uploaded them for you to check:

    • v01-v03, apr 4-9, no errors.
    • v04, apr 18, smaller file with error, maybe with the pixel layers were lost here.

    Perhaps you can find what's missing by comparing versions 3 and 4.

    P. S. I wish Serif support was always so quick to respond, :D thanks!

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