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

Roqoco

Members
  • Posts

    44
  • Joined

Recent Profile Visitors

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

  1. "Save failed due to an internal error. This should be reported to the development team." In case anyone might be having a similar problem: It seems that my project had become corrupted probably by a glitch/crash in 1.9.0. To fix it I created a new project and copy pasted the shapes from my old file into it. Since doing that the new file has worked reliably (on 1.9.1 that has some fixes) for several days and I'm reasonably sure this was the right diagnosis.
  2. Yes - Thanks for the input, you made some interesting points and got me to clarify, which is all good. And it is nice not to feel one is firing one's posts into a vacuum especially during lockdown, when I sometimes think I'm living in a sensory deprivation tank.
  3. @walt, @dominik yes I realise you can do that, but I haven't found a way of simply dragging stuff between the two views (obviously copy pasta is going to work, but it never pastes where you want and will probably put it in the wrong layer so that is a hassle) and it is pretty messy as it always covers up UI elements I need to see. Would much prefer to split the views... I also find that the views you make this way are strangely connected - try opening a master in one view and a page in another, not sure exactly what is going on there... Feature request #3 :).
  4. This would be really handy if there was a way of showing both the views at the same time in split screen, rather than in different tabs, so you could drag and drop between them. At least I haven't found a way of doing that if there is one?... Feature request #2 perhaps?
  5. Sure, but as spreads are so much more useful than artboards, if you have to choose, then I think "deprecates" is fair. But, maybe I didn't make my suggestion clear: The *suggestion* was that it would be nice to have *both* in the same document, especially if Serif made the implemention of artboards a little more flexible, so that you can drag them over your main design window and so use them as a palette. Actually, that is what I expected from artboards when I first saw them in Designer on day one - what a great feature! I thought for putting work in progess in... In general, although I am finding Affinity to be excellent (I wouldn't bother to comment if I didn't plan to use it) I think it still lacks some features for working on large projects with lots of separate elements, that are related to each other. Studio link is a great start...
  6. Yes Walt's idea of using master pages is a work around for stashing stuff: But, obviously master pages were not designed for this or as scratch pads and have limitations. In particular it takes you away from the context you are working on. When I design a new element I want to see what I am working on and to be able to pick colours and other elements from the surrounding design. Like you want your tool bag near the ladder you are working on, not in the garage :). And moving things between windows/pages takes more steps and context switches than just dragging shapes into place from a palette. Using the master pages is little different than opening a scratch file in a new window, except it keeps things in one place. As to whether it would be easy to implement, that is a question for Serif. I am just suggesting that since they have already implemented something not so different, that isn't being used any more in studio link, that it could be the basis for something I and maybe others would find very useful. The idea of scratchpads, viewports etc. is something that works well in a lot of other applications and contexts, you don't have to look any further than a good file manager, such as Qdir. That is how windowing UIs should work!
  7. Thanks for replying! Yes, I do in fact use the asset panel, but you can't directly edit shapes there, it is just a repository. All I am really getting at is that I missed artboards because they were quite useful as scratch pads before they were deprecated in favour of spreads, for those who use studio link and Affinity publisher (which is itself an awesome feature), even though they were not really designed for that. And given that the code for artboards has already been written, it might not be very hard to add the ability to make them float on top and then they would be useful alongside spreads as scratch pads. That is the basics, but there are all sorts of other things you could put on your scratch pads in the same way that an artist uses a palette board and maybe you could load and save scratch pads independtly. Another consideration is that when working on very large projects, the layer tree can become very convoluted and it is easy to forget and insert stuff all over the place or even lose it entirely, so it is often simpler to experiment on new ideas with a blank slate layer setup and then drag into your project when complete. Or am I the only one who spends lots of time refactoring layer trees? Reminds me of my days writing code. M
  8. Can you be more specific and say what you were doing at the time? Is the program freezing or exiting to desktop? Also have you upgraded to 1.9.1, released a few days ago?
  9. I had thought/hoped this problem was solved in 1.9.1, but it has just recurred. There are some signs that it may be related to a memory leak, given it tends to happen when my system has been on for a long time. That is something to investigate, I think.
  10. I did not install the beta of 1.9.1, even though I had problems with 1.9.0, because of possible registry mix up, which still sometimes happens with windows. It might be a good idea then to completely remove all serif applications, then take a checkpoint on your registry and run a registry cleaner such as the one in CCleaner to improve the chances of removing registry traces. Also check that no file/directory traces remain. Then do a clean reinstall from scratch. But, maybe you tried this already.
  11. Here are my results: https://photos.app.goo.gl/dEwfH1CwhkDsU56K8 I notice that my results for 1.9.1.979 release version are similar to your beta results (with a few anomalies, my processor is now > 6 years old and GPU several gens old). This suggests (captain obviously) that something went wrong on your setup between beta and release, but my results I think suggest that it isn't necessarily a problem with the Affinity release itself. BTW a new Nvidia driver was released on the 25th. I used this in the benchmark. Just a random thought - I know that Windows pro has some quirks, for instance they recently released a restrictive safety extension that some users found hard to completely eliminate... Anyway, it seems to me that given the experiences of others with the windows version your problem is most likely due to some incompatibity or glitch with something in your specific configuration. Not easy to tie down what that might be. my system: Core i7-3770 (this is old now around 2014), 16gb, GTX 1080, Windows home.
  12. Is also working on my nvidia 1080 late jan driver. Also 1.9.1 appears faster and more stable (failure to save and other problems appear to be fixed). Might be worth posting your specs.
×
×
  • 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.