![]() Allowing that pretty much requires programming logic and the possibility of bugs. Trouble also comes when you want to represent multiple "stateful" elements in one screen. Easy enough for completely modal views, but if they aren't, then often you want the content below to be part of the transition and that means your transition has to account for any number of combined screens (overlay + background). Overlaid content is one thing, and the simple case can be solved, but there are always questions about whether a transition out of an overlay screen should behave the same regardless of the content underneath. Thanks for the feedback, we can improve in this area. I hope you keep on truckin, cause I think you're headed in the right direction. The ability to quickly string together a number of screens feels great. FLINTO FOR MAC TUTORIALS MACI love the speed & stability that a native Mac app provides. To the team at Flinto: you've got an awesome looking product. Which is why I'll be sticking with InVision for now. Having used InVision's solution to this problem extensively, I haven't run into any of the "programming logic" or "bugs" mentioned. The folks at Flinto insist that this "prevents any kind of programming logic and bugs from entering into your prototypes". The transitions you build also won't respect scroll state either. What that means is if you want a modal or menu that appears in multiple screens, you have to build multiple versions for that modal or menu. The Flinto team explains their reasoning as an attempt to make sure "you can never reach a state that you didn't explicitly design." I remembered the #2 reason for dismissing Flinto was the poor support for popovers, dropdowns, and modals. Well, giving Flinto another shot ended rather abruptly. Accidentally sending 14 Artboards instead of the one I'm working is a very uncomfortable experience. Would be neat to save the last used options or keep it pre-selected when an Artboard is selected. **I pretty much only use the export with "Export only selected Artboards". FLINTO FOR MAC TUTORIALS UPDATE*The name can't be the underlying mechanic as I can update the name of Flinto by updating the name of the Sketch Artboard. The old Flinto screen inevitably shares the same name as it's new sibling but with a "1-" prepended to it. But sometimes my Sketch Artboard does not replace the equivalent Flinto Screen but makes a new Flinto screen. Result: Most of the time this works as expected, I just don't know exactly why. Sometimes it's been a while since I last opened the sketch file. I do: I open a sketch file and check that the names of the Sketch Artboard and Flinto Screen is the same* and send it over to Flinto**. Important as this will retain the other screens links to the screen I'm replacing. Intention: I'm trying to have my sketch file's Artboard replace its equivalent Flinto screen, effectively "syncing" the two. The problem is when Sketch Artboards and Flinto Screens fall out of sync. Understanding the logic behind the re-import of layers is probably more work than fixing the odd unintentional duplicate or deletion. Occasionally layers or links can get confused but it happens so seldom that it's never frustrating. That works miraculously well most of the time. I have a bunch of sketch files, with a bunch of Artboards each, that I import into one large Flinto prototype. I'll try and outline what I'm experiencing here in case anyone else has any ideas. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |