Jump to content

robinp

Members
  • Content Count

    448
  • Joined

  • Last visited

About robinp

  • Rank
    Advanced Member

Recent Profile Visitors

716 profile views
  1. @Gabe @MEB any chance one of you could communicate how essential this is to someone that can do something about it? Being able to find the scaled size vs the original size of a placed file (I honestly don't give a monkey's if it is a JPG or a PDF, both should behave the same) is really incredibly important. It cannot just be those of us working in the built environment that find this omission a total pain in the bum. There must be loads of designers and people preparing instruction manuals etc who need to know what size an image will be output at.
  2. Well that’s: a) pathetic and b) really unhelpful Our workflow requires it. So you’d better make sure this is something that does work. Working on files across a network is not a new thing. Does Serif consider the suite to be suitable for professional use? If the answer is yes, then working on files across a network is about the first feature on the list. Sorry for the tone, I am just completely stunned that this might actually be a legitimate and genuine approach. Someone needs to get a grip, because it is laughable. Anyway, it’s been fine working across a network since even the earliest public betas. Since linked files have worked properly it improved greatly. I can’t really share a work flow. Unless you want me to show you a video of me clicking save from the file menu. As for file samples, as you can imagine, I rescued from a back up and got rid of the corrupted ones. Next time it happens, I’ll be sure to keep them.
  3. I've never had a problem until recently. The file is not massive although if all the linked files were embedded then it would be huge. File is 68MB. But I'm getting 100% CPU use for extended periods when duplicating or deleting pages. This is crazy. Saving takes about a minute. My network is not that slow.
  4. I cannot be the only one who needs this but I've been after it now for a couple of years. Most of our documents include scale architectural drawings. Often, we might have consecutive pages with different drawings of the same project. For example, floor plans for a multi-storey building. When inserting these, we want to: Know the scale at which these files are inserted Be certain of the positioning such that when move from one page to the next the drawings align with each other. For example, page 1 has the ground floor and the next page might have the 1st floor. These should be positioned exactly on top of each other so that it doesn't jump around when viewing on screen Currently, doing these two very basic and essential things are a complete pain in the bottom. Summary of the problems: If you crop an image (either as a frame or an inserted image), when replacing the linked file the positioning changes. I would say this is probably a bug. When replacing a placed image its positioning should not change between the page and the inserted image / PDF. it should be possible to identify how an image has been scaled relative to the paper size of the image. For example, insert an A1 PDF drawing that is at 1:100 scale and reduce it in size by 50%. That would then be at the scale of 1:200. All very well when inserting it. If you come back later or if someone else works on the document it is impossible to find out how it has been transformed. The only option is to reinsert it. That is stupid. Related to the above, preflight reports when images are not scaled proportionally. Can I find a control / information within the interface to control this? Of course not. This is puzzling. These two (three?!) things are making it REALLY difficult working with scaled drawings. If anyone has a good workflow / workaround for these failures please let me know because I'm pulling my hair out and simply don't get how these a) were left out in the first place and b) have still not been sorted out. Hopefully it's just that I am looking in the wrong place and this functionality is there somewhere.
  5. It seems that things are really not very happy. So many crashes. VERY slow to save. Huge pauses when duplicating a spread. Images are linked rather than embedded so the file size is not crazy big. It's driving me a bit crazy. Anyone have any tips of things I could try to get it working well? @MEB
  6. I'm having a lot of crashes when saving files to a network drive. It results in corrupted files. Needless to say, this is a really big problem.
  7. Hi Chris I’ll have a look. Having experienced this problem a few times a quit and reopen or restarting of the machine typically fixes it. So I don’t think it is file related. This happens periodically and I’ve mentioned it before over the years but this is the first time I thought to record it before restarting etc. Over the last week or so I’ve been working with about 50 images. Open RAW files, develop (or merge to HDR) and then make adjustments. It seems to occur after working on many files in a row. It never seems to be the first few files where this weird behaviour shows up. Re photo persona, I really don’t like the persona thing and ignore it. I have no idea I’m afraid. I open RAW files and work with them. What goes on on the top left isn’t something I pay attention to.
  8. I've been working with RAW and Merge to HDR images all afternoon. Suddenly the grid on this one is behaving all weird. Screen_Recording_2020-06-06_at_17_32_56.mov
  9. When changing spreads from facing pages to single pages, all guides on master pages are lost. Pretty major problem. And one that has been around for ages and ages.
  10. I made a similar suggestion somewhere previously. I thought of it more as a ‘tag’ system. But essentially the same as you’re suggesting for the second part. I’m assuming the first part of your suggestion is dealt with by the file format structure. Or at least it should be.
  11. The message was from about half an hour ago saying it is one of the next things on the list.
  12. I can’t quite believe it. It is also kind of funny that it comes in a different thread to the one that’s been going for years and years
  13. Yeah, there’s a lot of excuse making that goes on in this and other threads for why really simple features haven’t been implemented. Quite often they veer towards the “we should want something better than the basic solution offered elsewhere”. Except what everyone is crying out for IS the basic solution available elsewhere as a minimum. There are, of course, obviously many ways the ‘select same’ tools in Illustrator could be improved upon. It sounds like Freehand had a much better solution for example. And probably there are much better ways that are available now than there were ~20 years ago with computing power being dramatically increased and resolution of computer screens allowing much more UI detail / info than before. But, it doesn’t get away from the fact that a basic feature could and should be able to be implemented very quickly. That would be sufficient for people to get their work done. If an earth shattering revolutionary solution is coming years down the line then great, but please just deliver the basic one quickly first so that we can get on.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.