It's in the to-do list. See forum for details.

My first reaction as well. I wasn't aware of how many times I use cmd+/- in PS/Sketch.

Yup - i'm experiencing the same thing. funnily enough, when I publish - it looks more like I expected. I also find that working with breakpoint really breaks the rendering of the editor too. Containers will move, and items will lose their position. Shame. If they iron these out - it's a great prototyping / proofing app.

Checkout Webflow.com (I'm one of the co-founders and designers). A lot of people compare Webflow to Macaw, but the approach each takes is different. Macaw wants to be the tool designers use to show their website's intent to the developer - kinda like handing off a Photoshop file but with more native responsive website interaction. Webflow wants to be the tool designers use to build their whole website from start to production without relying on a developer. Macaw generates layout code for while Webflow lets you decide what kind of CSS is best to create your responsive layout. Try them both!

Here, Tuts provides a $30 disaccount coupon code: http://webdesign.tutsplus.com/tutorials/getting-to-know-macaws-tools--cms-20480

I agree it seems a bit expensive. 100-150 would be more in my range. I'll wait till they fix some more bugs before checking it out.

The thing is, it's not a subscription, so you only get 1.0 + patches... with this many bugs I think I'll wait till 2.0 before throwing 150$ after something that might not fit in my workflow. I guess though, that 1.0 users will get a discount for 2.0, but I'm not sure it's worth it

I do not see the trial they're referring to at all? Lol?

EDIT: Okay there it is, guess I should have cleared my cache.

See my comment below

what is this paddle that everyone is talking about?

Say you're a designer with no coding background wanting to make simple one page sites for clients. Is the code output really so bad that this isn't a valid use? I have to agree with others saying that a visual design solution to front end coding is an inevitable future. A common theme of posts and articles has been "Why am I drawing pictures of websites and then starting over in code." Some people are moving to design in the browser, some are introducing more and more tools to their repertoire to compensate and creating more and more convoluted workflows for themselves (maybe that's not a fair statement) - but an obvious answer is a photoshop-like software that's built purely for web design and at the very least creates the groundwork for the code. Maybe MACAW isn't that answer, but it's the closest thing out there currently - and I think that's something worth investing in.

I'm hoping it's a better way for me to give designs to front-end devs.

The automated code isn't an argument for me. The web-centric layout engine is.

Photoshop, Illustrator, Sketch or Fireworks documents are all absolutely positioned (everything with X and Y coordinates relative to the canvas). What I'm looking for is a way to communicate what the layout is, and how it behaves. In browsers.

I understand Macaw's code output might be marginally better than competitors, but for us it'll be thrown away one way or another. If its generated pages can provide a real-life reference to use during front-end development, though, I'm all in.

Found mine in the spam folder.

Then wait for 2.0 and feel happy that you didn't buy something which is clearly still in beta. "Price is a flat fee and not a subscription. Price includes all updates to version 1 of Macaw."

I've been using it since the Beta, and I think it's pretty amazing!