Many bugs please fix

Hi, great work i really love this plugin u made, but it seems like many bugs also

i really want to buy this plugin to support u ❗️❗️❗️

but i cant because too many bugs at now hope u can fix that as soon as possible

---

• OS X EI Capitan v10.11.1
• Sketch v43.2
• Framer Inventory v3.0.1

---

I follow your video tutorial, i also download the files which related to that tutorial

i.e.

• Uber with Framer Inventory.framer
• framer-inventory-3-uber-example.sketch

but i have no idea why i cant do the same things which u do in that video

u can see the details in my video ❗️❗️❗️

e.g. bug1

I copy the layer - card_content in Artboard - uber/map, and i paste that code in Framer, but the y position of card_content is wrong !!

e.g. bug2

i copy the layer - card bg of Artboard - uber/map & uber/ride after i paste the code in Framer, i get the below . . .

card_content = new Layer
	width: 1312
	height: 1200
	x: 64
	y: 2292
	image: "images/card content.png"
	style: {"-webkit-filter": "drop-shadow(0px 0px 80px rgba(0,0,0,0.3))"}

card_bg = new Layer
	width: 1440
	height: 1920
	x: 0
	y: 0
	backgroundColor: "rgba(1,0,204,0.5)"

e.g. . . .

[timurnurutdinov]

Hi,

I’m on a vacation this week so replying with a delay.

A2: https://www.dropbox.com/s/h7c762jws0vd4el/more options.mov?dl=0 A3: No, it’s not. If you have several artboards and all of them to be included in prototype – this option will be very handy. A4: I was talking about something like this: https://en.wikipedia.org/wiki/Iterative_design So usually just one prototype is nothing, and you have to iterate with various designs/logic/etc. That’s why I show in video how you can “update” prototype by changing something on artboards.

[timurnurutdinov]

Hi again,

You are correct, it’s not a tutorial video, it’s just a demo of how to use the plugin with a real life example. Tutorials are boring and almost nobody would watch them to the end. So let me explain some details:

A1: You have to add “layerA.parent = layerB” code by yourself. Why? At this time I think it’s more secure because you import only layerA and plugin can’t predict the parent name (ex. you can create a scroll component with code and want to add a content with plugin).

A2: How did I generated the states for arrow? It’s an easy answer. You’ve got “more” button on the right bottom side of the panel and you can select a layer and generate “Shown/Hidden” states. It just makes opacity 0/1 states, because I reckon nobody likes creating hidden layers on artboards ^^

A3: “Layer” gets code for this layer only. “States for page” means plugin will take a look for entire page (= all artboards) and generate available states if there are some differences. If not, the result will be the same. Pro tip: select layer and some artboards to generate states for selected range.

A4: With Framer Inventory you can get states and write additional logic on the top of this. In this section of the video I’ve shown that you can change something on artboards and reimport to update visuals in your prototype – there are iterations, the way you provide the best solution possible. The movement of the elements is synced the way it depends on states and it’s a custom block of logic written (you can download Framer project to take a look at it). It’s really where to show that the states are not just animations but controllable transitions to be created with Framer Inventory.

P.S. Thank you for your questions, really appreciate your enthusiasm. Thinking about posting an article with a deeper look at all this stuff. Also I suggest to think about principles of Framer Inventory rather then of just certain examples because every prototype is unique and sometimes you can get almost everything with Framer Inventory and for some – a little (ex. it you generate patterns or populate data). Feel free to ask any feather questions!

Best wishes!