spedwig

Members
  • Content count

    18
  • Joined

  • Last visited

  1. 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...
  2. 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.
  3. 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.
  4. 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.
  5. 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
  6. Yes. All color spaces on all files involved are CMYK.
  7. 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).
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. It is incomprehensible to me that this feature so long requested and by so many is not only not already implemented but has no ETA. Add to the growing list of frustrations currently making AD untenable as a replacement for AI.
  13. Hmmm. It does seem to work that way when using the gradient tool on a group. Since I've been working with a few specified gradients, I had tried to paste the style (shift-cmd-v) on a group, which doesn't work... but does work for individual objects. Thanks for the tip; this will help with this specific application... it'll still take longer than it should (having to use the gradient tool and set my stops over and over again) because groups can't be style-pasted (and the union is broken).
  14. Great. In the meantime, this operation that should take less than 5 minutes is dragging on for hours, as I have to take a 10+ minute break every time I try to create a compound... waiting for it to eventually resolve (when it resolves at all).
  15. It seems that AD just can't any longer deal with this massive amount of information. Moving, copying, pasting... everything is now lagg-y and elicits the beach ball of death. See attached screenshot of the selection that's causing all this trouble.