Jump to content


  • Content count

  • Joined

  • Last visited

About derei

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The absence of bitmap tracing feature is a big minus for Designer... definitely reducing its appeal among professionals. Even Inkscape (free/open source) has a decent bitmap tracing engine. Hopefully Designer will have soon too.
  2. One of the most successful 3D Mesh Modellers was SketchUp. The initial developers (@Last was their name) came with the most intuitive and simple way so far to work in the 3D space. Unfortunately, since Trimble acquired SketchUp, things started to go south and the company is more focused in money making at all costs (and by this I mean sucking the blood out of the people which have little choice but to stay with Sketchup for one reason or another) and did too little to improve the software and the experience. The new version (SketchUp 2019 just moved towards web-based and yearly subscription...and users aren't happy about it. On the other hand, there is another company which thought there would be a bit of a market to compete with SketchUp (Bricsys - https://www.bricsys.com/en-intl/), they are offering the free software Brics CAD Shape (https://www.bricsys.com/en-intl/shape/). The similarities with SketchUp are obvious, but the downside of this one is they won't allow expansion by using plugins. SketchUp's real power came from plugins developed by the community members. Maybe it wouldn't be such a bad idea for Affinity to consider an alternative for SketchUp, following the same principles: take what is good and make it better, but at a decent price. And focused on users, because users will reward you for that. Wishing you best!
  3. done. I added your suggestion. thanks for pointing it out.
  4. Please read the first post in this topic and you will understand when it does it. And why... I experienced the joy of losing work 3 times before I decided to ask here about what's going on.
  5. I was referring specifically to the situation when Affinity can't save (due to remote disk communication issue) and it closes the document on purpose (that's not a crash, is a deliberate command). So, before closing the document, Affinity could simply make a recovery file with everything that hasn't been saved yet and then close. I really can't see what is the issue here. But instead, as it is now, AF Photo will forcibly close the document and any unsaved edits are gone... sad, very sad.
  6. I didn't get any notification for update and when trying to download it, the file received is still 206. Could you please provide a download link? Thank you. @fde101 nvm, I found a link on the forum. Thanks for letting me know about the new version!
  7. Great feature! Maybe there should be another flag added to this function: when an error happens and Affinity can't perform a normal save... I understand that in the event of a crash, it can't operate because.. it crashed, but when the software is operating normally, I don't understand why it doesn't perform a quick recovery save before shutting down.
  8. @fde101 Right-Clicking on that group of layers, on my "normal" page, shows the following menu (see attached): AF Publisher Version: if yours looks different, kindly please share a screenshot.
  9. @dutchshader did you manage to find it? If so, do you mind attaching a screenshot? I can't seem to find those options. Thanks.
  10. I have a Master Page with a text placeholder and I want to have a unique text on each page where that specific placeholder is. The issue is that the text is between two layers, so if I take the text out of the Master Page Group, (which has been created in page's layers when I applied the master page), the text won't be between those two layers anymore (it has to be between the layers, as the layers do some blending). So, I would like to be able to edit my text field on every page, but to not affect the Master Page. In Illustrator is possible to "release" a field so it can be edited independently from the Master Page. Any suggestions?
  11. guess you're right... plus this guys have all our bank account details too... Don't you suddenly start feeling oppressed? :))
  12. I noticed the objects in Publisher are all surrounded with a purple outline, including text. For text this is really annoying as I can't clearly see the fill color and asses that against the document (visual contrast, aesthetics, etc). Is it any way to disable the purple outline? The outline is not some effect applied to the text, it comes from the way Affinity is displaying the elements. I also have an image imported in Publisher which has the same purple outline. - see attached
  13. I understand that, but what puzzles me is that I was able to work just fine all along and edit my work, until I decided to save... when it closed. And it didn't happen once, it was repetitive, at least 3 times it happened until I decided to write on this forum. So, if Affinity needs continuous access, why it was no warning and I was allowed to do my work all along? And why it only happened when I tried to save? Also, on opening, there was a recovery dialog which helped me recover a part of my edits, but not all of them (which is weird also, why AF Photo won't save a temp recovery data when such situation happens). From all talks on this subject, I still see no reason for the following: Why Affinity does not give any option for the user to take action, but instead just informs the user about the unavoidable and then closes (don't you find that rude?) Why Affinity has to close the document and there is no better solution, like automatic check of connection, and/or even allowing the user to manually re-select the path to file? Why Affinity doesn't save the changes until the last one locally (in a temp file), so they can be recovered next time when the file is being open? For me, it all looks like Affinity didn't manage this aspect very well and it would be in their best interest to show their presence here, to let us know they are hearing us and they will take proper action in order to improve user experience on this matter (and not only on this one).
  14. Surprisingly, it seems is not. My issue while saving on my pCloud virtual drive confirmed it: whilst Affinity Photo was NOT able to save, I had no problem opening the drive and interacting with the files there. So, the storage was available, but for some reason Affinity could not access it. What I can assume are 2 things: 1. pCloud is "locking" the file while sending it to the cloud server, so Affinity "thought" it cannot be overwritten/saved. 2. there was a short intrerruption at some point and Affinity did not check again @R C-R I understand your point with cached copies, indeed, too many variables and too many complications in too many scenarios. Most probably this wouldn't be the desired solution. Perhaps then making sure the connection is re-checked, or allowing the user to select the path to the file (in case Affinity can't automatically find it for some reason), and also if possible to save the modifications so they can be recovered.
  15. Guys, this debate became way too generic. There are two types of interruptions: short (milliseconds - seconds) and long (minutes or even permanent). Two different approaches for two different situations: if interruption is short, that means is most probably "sleeping" and it needed a wake-up signal, or it was a short network drop, or something else. But this also means is back in no time. So, after the first failed attempt, the software should warn the user, WITHOUT CLOSING THE DOCUMENT and the user can check the connection of the drive (in explorer, for example) and then try again to save. if interruption is long or permanent (someone simply unplugged the drive, or internet is down), there isn't much to do. Obviously the document has to be closed, but maybe a better recovery system could be implemented so all tools and operations can be recovered since the last successful save on the disk. Now, as long as there isn't any "observer" or "listener" to check connection continuously, I see no reason why there would be any negative impact in performance. Just don't close the document until the user performs another attempt to save. Keep everything on stand-by and there is a very big chance that the connection will be re-established with the help of the user. I really don't see where is the issue here, conceptually speaking. Also, having a cached copy locally would be a safety measure, a redundancy point. Yes, more space occupied on the local disk... and I see no problem with that. The storage media is meant to be used. I'd welcome a setting in Affinity to allow me to decide on which drive to create a "cached copy" of the current documents. I'd be happy to reserve ~10GB or so for that, when Affinity software is open, just to make sure my files are safe. Of course, there are issues here: what if you have Photo, Designer and Publisher open at the same time? Well, whoever wants to do graphics they usually invest in a decent machine with decent storage... there has to be a compromise anywhere.