Jump to content


  • Content Count

  • Joined

  • Last visited

  1. I usually hit tab which hides the UI, drag the window down, then tab again to bring the ui back. It's a lot easier than dragging the toolbar around, but I agree, it gets tiresome dealing with it. I think the problem is that the top bar ui has no "presence". If you're like me and make larger windows to see more of the design, then the default system stacks new windows, but the top toolbar doesn't register as an obstacle. It would be wonderful if this was fixed in a future release, although I think this should be registered as a bug rather than a feature request.
  2. It's their desktop folder, I hope they have read and write permissions. :)
  3. I compared Toon Boom, Flash, and Anime Studio Pro at one point wanting to do the same thing. The main question is what is your end deliverable (format), and how do you want that animation to be seen. If you are just delivering video or sprite sheets for games, any animation package previously listed will work. If you want to deliver svg animations, currently Flash has the best support, being able to push to HTML5 (CreateJS Exporter) and now WebGL. I used Flash and CreateJS workflow working on a project for HTML5 games, it's pretty great, and the only thing I am missing in my non-Adobe toolset. Toon Boom turned me off on their high pricing structure, I ended up buying Anime Studio Pro, but it's missing svg/HTML export capabilities (I posted about this on their forms here: http://www.lostmarble.com/forum/viewtopic.php?f=3&t=24969). My main decision on going with Anime Studio was the ability to export FBX files, which I could bring into game engines. There's also http://www.synfig.orgwhich is open source, but it felt a bit clunky. Although, it's free and you could at least start/try it and see how you like it.
  4. That file seems like a cached version? One thing you could double check is the permissions with Terminal. Open Terminal, then each line type and hit enter cd desktop ls -al (If the third column doesn't say selfagency for the file you want to open) sudo chown selfagency fileName.jpg
  5. If I ask for a feature, I'll try to answer at least one question.

  6. By the way, if this is the issue, and you need thickness on the handle as well, you just need to think slightly different when creating the objects for svg optimization. Also attached is creating the handle like yours, by creating the shape with "Rectangle with round edges" (in the tool palette), you can customize the amount of curve on your box (handle). Then just boolean (subtract) an amount and put it in place. The advantages of this way of doing it is when you're scaling the object, it maintains it's proportions. While using lines with strokes does not, i.e. draw an object with lines, put a stroke on it to give it thickness, then scale that object. You'll notice that the thickness will stay the same when scaling it, breaking consistency. Also attached is my version of the search icon with the examples, and the final svg output for you to compare. One thing to look at is the file size of the svg of mine versus yours. search-icon.svg is weighing in at 1,019 bytes (1kb), and I have a feeling yours will be 3-6x in file size due to all the extra data (nodes). You can open svg's in any text editor to compare as well. search-icon.afdesign search-icon.svg
  7. I have a feeling this is due to AD's "Expand Stroke" not being overly optimized at the moment. Attached is an example of two different ways of creating that circle like you have for the search icon. First way uses two circles which the inner circle is subtracted from the other; notice there are four points on the outside and the inside. It's very clean. The second process is creating a circle, then using Stroke > Expand Stroke. After expanding, there are a huge amount of nodes on the paths. Looking at your attachments, it looks like you are creating your objects from lines and then expanding (noticing it from the search icon handle). So, until the expand stroke feature of AD is optimized better, I would either create the SVG export as either the line with a stroke amount (don't expand it, like you did with the handle), or use the boolean operators for cleaner nodes.
  8. I did a search on feature requests on slices, and didn't really see anything on this or in the roadmap. I did see a post that there is more to come for Exporting Personal, but here is a feature(s) I've come to want while working with AD. In Export Personal (AD), if you create multiple slices, they are literally all over the design, yet we have a palette dedicated to the management of those slices. I would suggest that the palette be the "controller" of showing and hiding slices created by a simple selection(s). So, instead of slices constantly cluttering the design, with only corner anchor points being the highlight a slice is selected, hide the slice unless that slice is selected within the palette. This would greatly clear up the interface and provide good UX. Especially since you already have to select the slice that you want to export, this would give clear visual feedback of what a user is exporting without all the clutter of other slices. In addition, to further enhance this, by selecting multiple slices within the palette, it could group slices as a composite export selection. This would allow us to define potential elements of export through slices, without literally having to create every possibility. See attachment. So, since the slices palette already is the determining factor of what is getting exported, and if we hide the slices unless selected, then being able to select multiple elements for different variations of exports would be wonderful as a composite of those selected slices. If anything, at least hide the slices' bounding boxes unless it is selected within the slices palette. Otherwise, it can get very unruly.
  9. I took a look at this since I use Blender as well. I figured out the problem after going through a bunch of tests myself. It's due to the width and height properties. Designer 1.3.5 sets width and height to 100% for both, this causes Blender to import at the smallest scale possible. If you define the width and height to a non-percent, it works how it should. Designer 1.1.2 defined the width/height to an actual number, as well as all other svg exporting apps you mentioned. You can open the svg file with any text editor, just remove the % sign from the width and height, even width="100", height="100" works, or increase it if you don't want to have to scale within Blender.
  10. Lol, poor devs, make a good product and we users always get greedy. :)
  11. Adjust, spacebar, adjust, spacebar, zoom, move to different location, spacebar, zoom out, spacebar, adjust, spacebar...
  12. Here is another use case for the ability to hide this transformation box. When working on a design with fonts, and you're trying to get an idea of composition, the box really is visually disruptive. A start would be at least hide the box when going through fonts – since it's hard to even judge spacing. A smaller font size would even be worse to manage or see.
  13. Will that also fix using boolean on low node objects that has an inner cavity, like a hollow circle? This was a subtraction, but it it only subtracts at node points.
  14. Still getting these blocks at random times. I can pan through the document and the blocks stay, only forcing a zoom will it refresh. And when zooming, I get "see-throughs" at adjusted zooms even when the background extends past the document boundaries – this is also random. The see-through disappears when Command+0/Zoom to Fit is used. I can see a noticeable "compressing" (~1-2 pixels) of the document moving from one zoom level down (Command+-) to Zoom to Fit when the see-through occurs.
  • 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.