Jump to content

spedwig

Members
  • Posts

    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. 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.
  7. 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.
  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. 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.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.