Jump to content

spedwig

Members
  • Content count

    22
  • Joined

  • Last visited

  1. I recently updated AD to 1.7. It appears that when I made the switch, the "save history with file" setting was not persistent. ie I've opened files that previously were set to "save history with file" and the history is missing. I noticed this after a crash of my computer, so it may be that the recovered versions of the files are the only ones for this that are true. But... speaking of recovery, though I have the file recovery interval set to 300 seconds, after my computer re-start, the recovered files I've opened don't seem to have had any recovered information... only the last saved version, which admittedly was longer ago than it should have been. I have to confess that the excellent recoveries I'd experienced in 1.6 allowed me to become lax in my saving... much to my detriment as now I have lost a not inconsiderable amount of work, as the recovery files have recovered... nothing. I have to say that I don't expect any kind of miraculous recovery of my work, but I do hope that these features can be fixed.
  2. Didn't realize I could select artboards using the move tool by clicking on the labels. I always used the artboard tool to... work with artboards. Thanks for the tip.
  3. Recently updated to Designer 1.71 on Mac, and I'm experiencing new odd behavior working with artboards and the artboard tool. In past, I could select an artboard using the artboard tool and then alt-drag to duplicate the artboard. Now, when I do so, it creates a new artboard where I'm dragging. Similarly, in the past, I could select an artboard using the artboard tool and drag it to move it. Now, when I do so, it creates a new artboard where I'm dragging. It seems I now need to select the artboard using the artboard tool and then switch to the "move" arrow tool in order to either move or (while holding alt) duplicate the artboard. This seems like a huge non-intuitive step backward, involving lots of extra mouse-clicks and tool-switching. Or is there something I'm missing?
  4. If you use the export persona to "hide" artboards/slices that you don't wish to export and then use the file menu export function, there is a setting to not export layers hidden by export persona. The others will be compiled into one pdf with each artboard a different page... or at least, it should.
  5. This. A hundred times this. All the time, I select a large number of nodes (usually when working on things that started as hand-lettering) because I need to make adjustments to a whole portion. Now that I have all of these nodes selected, it seems like I should be able to grab one of them and drag the whole lot wherever. In practice, though, EVERY time I try, it grabs and pulls a single handle. I need to be zoomed out, as I'm making a macro-adjustment and need to see the whole piece, but the only way I can successfully grab a node (and move the whole group of selected nodes along with it) instead of a handle is when I'm zoomed way in. If nodes were prioritized over handles when multiple nodes were selected, there'd be no problem. I can't think of a single time when I've selected a bunch of nodes and then the first thing I wanted to do was to drag a handle...
  6. spedwig

    Designer crashes when moving artboard

    I have this issue as well (on High Sierra), or much like it. In my case, it occurs when I'm using the Artboard tool and alt-dragging an artboard to create a duplicate. It happens in different documents, repeatably. I just thrice tried it in the current file I'm working on; crashed each time. My first experience of this was when dragging down; it has since occurred when dragging left and when dragging right. It doesn't happen every time.
  7. That covers exactly one use case for "select same". In my experience, it's more often something other than changing colors that I want to do when selecting same: Add strokes to all. Create compound path (or Add). Move to a specific layer. Delete. These are just a few examples off the top of my head that are things I've needed to do to all objects of a certain color that using global colors doesn't fix.
  8. spedwig

    CMYK Values not staying same

    Good to know about the other means of adding to a palette. I'll use that to create my palette for now. I do have to state, though, that I was having the problem with CMYK values changing even before I tried creating a palette from them. Unfortunately, it was noticed after a lot of moving objects from a variety of different source files to a variety of other files, so I have no idea how else the problem may have occurred.
  9. spedwig

    CMYK Values not staying same

    Here's a brief screen recording in which I recreate the issue. In real life, I have no idea when the changes first occurred or in what document, but here I'm starting fresh. Originally, I was double-clicking the current object color (in the color tab) to bring up the details and changing the percentages there (because the color tab was set to wheel)... which is where I took note of the hex colors. cmyk_color_change.mov
  10. spedwig

    CMYK Values not staying same

    Yes. All color spaces on all files involved are CMYK.
  11. I'm finding a strange situation in AD; I set a series of color using CMYK percentages. Using objects in multiple files, I notice that the CMYK values are changing. So I created a swatch set with the proper CMYK values. I used those swatches to fill objects... and again, the values are not staying the same. The new values result in a color that is very close to the original... and it looks like the hex# is staying the same... so perhaps it's prioritizing the hex# and changing the CMYK percentages to match the hex#? But the hex isn't what I input, and i'm concerned about what changes might be wrought in the print process (the cmyk percentages are based on process swatches).
  12. Agree. Honestly, the way Illustrator does this seems much less problematic than the way AD currently does. If one opens the drop-down, one is taken to the spot in the font list where that font lives; this is great for when scrolling through and trying out different typefaces systematically (in AD, it always takes one back to the top of the list). If one starts typing, the font list starts showing only results containing those characters in that order (whether or not they're at the beginning of the typeface name — so one can type "con" and all fonts containing that sequence show up... not just ones starting con, but also ones that contain "condensed"; I find this hugely helpful). (in AD, typing opens up the dropdown and... if typing fast enough... will take one to fonts starting with that string only). Both of these functions make finding fonts in a list of hundreds much easier. Maybe something like these could be implemented? There are several different threads making requests like this... and this kind of interface function seems much more fundamental a need than some of the advanced operations showing up on the feature roadmap.
  13. Agree. Honestly, the way Illustrator does this seems much less problematic than the way AD currently does. If one opens the drop-down, one is taken to the spot in the font list where that font lives; this is great for when scrolling through and trying out different typefaces systematically (in AD, it always takes one back to the top of the list). If one starts typing, the font list starts showing only results containing those characters in that order (whether or not they're at the beginning of the typeface name — so one can type "con" and all fonts containing that sequence show up... not just ones starting con, but also ones that contain "condensed"; I find this hugely helpful). (in AD, typing opens up the dropdown and... if typing fast enough... will take one to fonts starting with that string only). Both of these functions make finding fonts in a list of hundreds much easier. Maybe something like these could be implemented? There are several different threads making requests like this... and this kind of interface function seems much more fundamental a need than some of the advanced operations showing up on the feature roadmap.
  14. Agree. Honestly, the way Illustrator does this seems much less problematic than the way AD currently does. If one opens the drop-down, one is taken to the spot in the font list where that font lives; this is great for when scrolling through and trying out different typefaces systematically (in AD, it always takes one back to the top of the list). If one starts typing, the font list starts showing only results containing those characters in that order (whether or not they're at the beginning of the typeface name — so one can type "con" and all fonts containing that sequence show up... not just ones starting con, but also ones that contain "condensed"; I find this hugely helpful). (in AD, typing opens up the dropdown and... if typing fast enough... will take one to fonts starting with that string only). Both of these functions make finding fonts in a list of hundreds much easier. Maybe something like these could be implemented? There are several different threads making requests like this... and this kind of interface function seems much more fundamental a need than some of the advanced operations showing up on the feature roadmap.
  15. spedwig

    Add search font field

    Agree. Honestly, the way Illustrator does this seems much less problematic than the way AD currently does. If one opens the drop-down, one is taken to the spot in the font list where that font lives; this is great for when scrolling through and trying out different typefaces systematically (in AD, it always takes one back to the top of the list). If one starts typing, the font list starts showing only results containing those characters in that order (whether or not they're at the beginning of the typeface name — so one can type "con" and all fonts containing that sequence show up... not just ones starting con, but also ones that contain "condensed"; I find this hugely helpful). (in AD, typing opens up the dropdown and... if typing fast enough... will take one to fonts starting with that string only). Both of these functions make finding fonts in a list of hundreds much easier. Maybe something like these could be implemented? There are several different threads making requests like this... and this kind of interface function seems much more fundamental a need than some of the advanced operations showing up on the feature roadmap.
×