Thoughts on a Development-specific engagement

@anton please see the post above from @Razor
– This is exactly what I’ve meant three days ago in the other thread.
I quote myself from that thread, please read it line for line (especially the last textblock in it):

.

I simply can’t believe that Razor now asks for reports with examples!

  1. It is IMPOSSIBLE that someone who really uses Anytype for real purposes, doesn’t already know about the OBVIOUS differences between the layout’s appearence on screen and the print result!
    – Simply print one real Page!!! In most normal cases you will see the differences!
    If not, put some elements more on that Page and print it again! Now you MUST see it, you can’t pretend the opposite!
  1. It WAS ALREADY reported by me, more than a year ago!
    For unknown reasons, the old thread is tagged as “implemented” and moved into the cemetery!?!?!
    – But it isn’t solved or “implemented” at all!

  2. I’m not the only person who has moaned again and again (in different threads) about the problems with printing and exporting.
    It should really be well known for everyone: each user, and even more for each team member!
    Someone who prints more then “Hello world” WILL know that we not get what we see on screen!

– Why on earth do I now need to create new reports with examples if most problems with print and PDF export are absolute obvious and also known for a long time?

It will cost me HOURS again:

  1. to create good example documents that show each problem separated.
  2. to write a separate report for each single problem.
  3. to make screenshots and PDF exports.
  4. to record good videos.

Why all that?

OK, OK – I want to be a good boy and play after your rules!
I will do what Razor asked for, even though I don’t understand that burden – we have here an obvious case that should (for years!) be well known for everyone!

I’ll do all that and I appreciate that Razor is at least willing to look what he can do!
But @anton , please also try to understand my point of view and how frustrating it often feels if team members, even devs, pretend to know nothing about well known longtime issues that are obvious and peeve each normal user nearly every day!

It is not only me. This is what also the other users have meant in the linked thread.
Please see my long text here as a constructive feedback that points exactly on the communication issue that us users here disturbs again and again.