thisleenoble

I am adding support for SVG sprites to one of my website frameworks. I'm loving the fact that in AD I can export all the individual icons as SVG in situ from the designs supplied, rather than having to assemble them in their own separate document. Being able to select each layer, create a slice and then adjust that slice's dimensions if I need to is fantastic.
The end result is I get a lot of separate SVG icons.
Then I expended a lot of energy installing Node, Grunt, SVGO, you name it in order to do the following:
Optimise the SVG files Create an SVG sprite Copy all the individual icons into the sprite as symbols I realised it would have been SO much easier if AD (or AP) offered the ability to export selected slices as a sprite. I thought that might be what the Continuous checkbox did, but alas, no.
 
For reference, my starting point for this was this page: https://24ways.org/2014/an-overview-of-svg-sprite-creation-techniques/, the section beginning HTML INLINE SVG SPRITES (specifically the latter section dealing with external sprite.
 
It would also be advantageous to me if the style="fill:#HEXCOL" could optionally be dropped on each element on export as it prevents styling the elements with CSS.
 
Thanks for making a great app even greater.

I've found numerous topics on the subject of adding a mail merge feature to Publisher but couldn't see anything relating to Designer. Appreciating that Publisher might be the best place for it, I can't help thinking it would be an enormous benefit in Designer.
I've been producing flyers and posters for a local film club for years. I had templates set up in Pages and each quarter I would have to place the images, change the dates, print to PDF. convert to image, crop, zoom etc. I made it as efficient as I could in that program and it took a lot of initial effort to create the starting templates, so the thought of doing it all over again put me off for a while. This weekend I finally re-did the whole thing in Designer. Symbols are used throughout for the film posters and dates and QR codes and colours. I now have an artboard called Resources that contains all the base elements and compiled symbols:
Then the other artboards contain separately the portrait and landscape posters as well as the quarterly season flyer:

All I have to do is modify the resources, drop new images into place and change the dates in the calendar, tick or untick the correct layer for the BBFC film rating, drop in a monochrome QR code and it's all done. I can hit one button to export all the posters and flyer and differently sized image slices for social media. What used to be in seven separate documents with a heavy post-process can now be done in literally minutes (hopefully - I'll find out next quarter).
However, I would LOVE the ability to have document variables. Variables that can be used in ANY input. Obvious initial examples would be for the film titles and dates. Also applicable to product ingredient lists and allergy warnings in other layouts. The colours used for each panel could also be document variables. At the moment I've just used a pair of squares swatches that are repeated as symbols and stretched to cover the spaces in the final layouts. Being able to define the colour in the palette dialog as [%COL_A%] and the accent as [%ACC_A%] would mean I could just change those variables in the document properties and have the whole theme change. There are loads of places where I could do this rather than have to use symbols and I think it's worth your consideration.

I am adding support for SVG sprites to one of my website frameworks. I'm loving the fact that in AD I can export all the individual icons as SVG in situ from the designs supplied, rather than having to assemble them in their own separate document. Being able to select each layer, create a slice and then adjust that slice's dimensions if I need to is fantastic.
The end result is I get a lot of separate SVG icons.
Then I expended a lot of energy installing Node, Grunt, SVGO, you name it in order to do the following:
Optimise the SVG files Create an SVG sprite Copy all the individual icons into the sprite as symbols I realised it would have been SO much easier if AD (or AP) offered the ability to export selected slices as a sprite. I thought that might be what the Continuous checkbox did, but alas, no.
 
For reference, my starting point for this was this page: https://24ways.org/2014/an-overview-of-svg-sprite-creation-techniques/, the section beginning HTML INLINE SVG SPRITES (specifically the latter section dealing with external sprite.
 
It would also be advantageous to me if the style="fill:#HEXCOL" could optionally be dropped on each element on export as it prevents styling the elements with CSS.
 
Thanks for making a great app even greater.

I realise that this, if it were remotely possible, would be way down the list of priorities but it might be an eventual necessity for me.
I'm used to receiving "flats" produced in Illustrator and can happily open ai, or pdf (and photoshop) files directly in Designer and start exporting layers directly into my projects. The design house we work with is experimenting with Adobe XD as it helps them to demonstrate UX to their clients and the most recent project I built was primarily put together in XD. The experience for me has been awful. Some assets (Photoshop embeds apparently) come out horribly pixelated and can't be used. I have to ask for those assets to be supplied separately which destroys my established workflow. 
The experience has been so bad [for me] that we might have no choice but to migrate to an Adobe only workflow [waah! I don't wanna! I'm into Designer now].
I sat with the designer to see if we could figure out a way around the issues. XD files couldn't even be opened in Photoshop or Illustrator and there was a distinct lack of export options when it came to embedded images. So, if you could just do a better job than Adobe have with their insider knowledge of file formats used by their own software that would be grand. Cheers.

Eep! Yep that's the difference!
This is surely a bug.
The original "Fit to Plane" correctly generates a pair of values for Rotation and Skew. It is as if that isn't being removed / zeroed before the new values are calculated.

I have previously filed an overlapping feature request but after consideration I actually think this is a bug in the Isometric/Cube grid implementation which if it were to be fixed would do wonders for the usability of this amazing feature. The attached video demonstrates.
1) Draw three identical squares int he flat view.
2) Move each square in turn to the Top, Side and Front planes, bring them together and you get a facsimile of a cube.
3) Now move one of those faces to a different plane by highlighting and clicking "Fit to plane" in the Isometric studio palette and you'll find the apparent dimensions change.
This action should retain the intrinsic dimensions of the original flat shape, enabling the user to flip objects between the planes. Returning them to the 2D view would also be desirable as the application "knows" the original dimensions it seems like this should be possible.
 
Cube-Bug.mov

Your grid is a perfect isometric grid so the skew values are identical for all three planes.
For a minute there I had hope that I'd missed something. You gave me the hope!

I've had a further thought on this, and I think I might have guessed where you're heading with the solution for the perspective transform. Ok, so I was playing with an isometric-ish grid and moving flat objects onto grid planes. The next logical step, for me, is to be able to move objects from one plane to another, switching from front to side. I mean the objects clearly have current knowledge of which plane they are in so that the regular transform handles conform to that plane, the point being it "knows" it's real dimensions if it were face on, so despite the fact there's no way to return an object to the flat face-on plane, it doesn't seem that much of a stretch to be able to do so. Then once you can freely move objects from flat view to any plane and back again this gives you far more control if you wanted to change the underlying grid.
For example, say you start with a straight isometric view and build out some objects, and latterly decide you want a lower perspective, you can change the grid but you're stuffed when it comes to migrating your objects to the new grid. However, if they have a reference size described in the flat view, those objects could be transformed through that flat view and back into the newly defined grid planes.
Combined with the ability to "pinch" the grid cube to create non-parallel 3D grids you'd effectively be able to change the perspective on any 3D construction (with obvious certain limits).
This would be the type of thing that I see fitting under the umbrella of "wanting to do the right thing and not just copy how other software works (i.e. the perspective/warping tool)".

As far as I am able to tell, this facility is only accessible via the contextual menu on an object. My understanding of the intent for a contextual menu is it should only present options which are also accessible via the normal menu hierarchy. I have been unable to locate it there and it doesn't appear to be listed anywhere in the shortcut preferences either. Maybe just a simple omission but it would be handy.

Hi,
 
AP 1.5 beta is coming - in a couple of weeks or so.. here are a few of the things we can look forward to:
 
- HDR merging.
- HDR toning.
- Full 32bit unbounded linear editing, including (correct) OpenEXR, Radiance support.
- Focus merging.
- Live Projections (edit in perspective projection, equirectangular projection).
- Macro recording and playback gallery.
- Batch processing.
- Layer linking.
- Magnetic selection tool.
- Polygonal selection tool.
- Ability to round-trip PSD (for use with DAM applications).
 
- Lots of small improvements.
 
Hope this helps,
 
Andy.