Thanks for the report! this is fixed now in 2.1.3
baj
Creator of
Recent community posts
Hey thanks for all of your tests!!!! I could publish the linux “unpackaged” files if that would make this easier? Also, I just finished the most heavy dev part, so maybe I can focus now on your flatpak idea? I’m active on the discord if you want to brainstorm something! http://discord.gg/t7GJXTTqmg
Hello thanks for the report! I’m not very knowledgeable about windows antiviruses, so can’t help you there unfortunately. I’d say that, in general, if in doubt, is probably is best to not install (the app is not even signed with windows store)
v2 was temporarily unavailable for a bit just recently but It should be online again.
About JS.Siggen5.44590 its seems to be related to http://github.com/medikoo/es5-ext package which is a dependency, of the app. check out this topic: http://github.com/medikoo/es5-ext/issues/186
Hello! Thanks for the feedback! I’ve logged these into: http://community.drafft.dev/tags/feature-request
-
A customizable database: This has been brought before, while I don’t personally like the visual form approach I will consider it if there is enough interest. Having said that, I’m working on a better grid section, which will support more data types and images. It is not the same as you are asking as we don’t have support for nested properties (its just a 2d grid). In parallel we have this idea for “template”. It’s not very defined yet though: http://community.drafft.dev/questions/D1O2/template-system
-
small diagram/flowchart maker I like this! I’ve added to the backlog for when I finish porting all the missing v1 editors.
-
Zoom bug: I’ve noticed it too, something related about the available space changing. Added to the backlog
Thanks for your inputs!
Hey thanks for the suggestions! I wrote a really long reply but lost it when I click a link …
-
The edit toggle suggestion is great! I also considering moving that to the tabs toolbar: http://community.drafft.dev/questions/D1y2/fr-move-the-whole-lock-save-undo-area-to-the-actual-tab-toolbar
-
+1 to everything! logged it here: http://community.drafft.dev/questions/D1z2/fr-dialogue-tree-0-0-indicator-and-a-button-to-re-center-the-graph
-
The status bar idea is great, it could trigger the info panel (which I plan to overhaul in the future with comments, custom metadata, etc) did you found that? its “Show info panel button” in the toolbars
Loved the background concept! I guess it could be quite easy to implement via css and a file url.
yes, the primary color is an issue if the user uses a light color, maybe I should expose a “foreground color” picker as well.
I will keep the logo color idea, could look really nice!
Great suggestions, thanks for taking the time to write!
If you have time, could you try this example, and see if it works on your end? (or any shift key example in the page)
http://react-hotkeys-hook.vercel.app/docs/documentation/useHotkeys/basic-usage#keystrokes
thanks!
Great thanks for confirming! The dangling activation is a side effect for a fixed bug in v12. You can manage your activation here: http://app.lemonsqueezy.com/my-orders/ or let me know your email and I can do it. (can reach me via support@drafft.dev)
Thank you!
Hello Ether, thanks for the feedback and taking the time to reply!
-
Thanks for bringing this to my attention, email should be working now! I’m fine with keeping this place on itch.io but as the store has moved away it feels a bit… wrong! Still testing the community platform (apache answer) so it might not be a good fit, or maybe yes :)
-
Shortcuts: Strange! I’ll investigate, I think it might be related to the keyboard code for shift as seems like ctrl+p is working for you, have you tried left vs right shift?
-
I think that is a good Idea! I will see how crowded it looks, but it should be visible on node selected only so it should be fine, added to the backlog!
-
Docs: yes! I need to spend some time on docs. But for now I’m prioritizing bugs and hopefully bring the other editors from v1.
Thanks again !
I think I have a clue on what this is, there are some reports involving a username with long/special characters http://github.com/electron-userland/electron-builder/issues/6865 questions:
- can you run the uninstaller manually in: C:\users\youruser\AppData\Local\Programs\drafft?
- if it fails, can you delete the uninstaller file and try again?
- if it still fails, v2.0.9 uses the old name “drafft” without space, which might be the reason its not working, vould you try that?
Thank you!
Hello! We do have yarn syntax highlighting for scripts but that’s all. That would mean that you won’t have dialogue trees out from the source text nor speech identification if you use their syntax.also the source text won’t covert to dialogue trees
Having said that, you could write and store your source files without issues. you will have to do the parsing outside of course, the app will give you a json file (or basic JSON api)
The demo is unrestricted do feel free to experiment with it!
I like this idea. Global variables. So when the document is in view mode it shows the value? In edit mode shows the real $variablename?
What about game export,I guess we render each var.
I think the idea of multiple .env files is also nice… Like a $(prod.server) or $(player.name) where prod and player are different .env files.
Maybe the misc collection can be upgraded to a metadata collection where we can have a customizable list of documents that can be directly accessed via this specific syntax. Like meta.env.xx or meta.menu.startgame etc etc… Or… Maybe this syntax is a shorthand for displaying any value of any document of any collection. Similar to the new picker feature , but it could target any prop.
$(items.sword-01.description) or $(actors.kenji.properties.height) or even $(script.script-1.modifiedDate)
This would give items/misc/quest a whole new value specially when used in god/scripts.
The main issue is finding a good typeable name as the name is not unique and the id is quite long. Maybe the doc alias should be user editable.
Great idea!
hm this issue leads me to apparmour profile again and also a strange case where the appimage has a space in the path.
do you have any space in your path? http://github.com/electron/electron/issues/44414 http://github.com/electron/electron/issues/41066
BTW: Electron builder 26 which have apparmour support/fix will be stable soon apparently.
Sad to hear about the flood damage! Hope everything is ok! I’ll set a docker compose and add it to the documentation as the “official” setup.
I’m not sure about your environment (are you running Debian?), bu maybe you can try:
Possible Solutions
- Run with No Sandbox (Quick Fix):
./drafft-appimagefile --no-sandbox
- Use the –disable-setuid-sandbox Flag: ./drafft-appimagefile –disable-setuid-sandbox
I got you. I think it makes sense! I’m actually adding a notes/comments panel on every document in v2 (no matter what type of doc it is) so it’s actually developer notes instead of content. This might be also useful on multiuser setup with the potential of becoming some sort of comment/review thing in the future
Thanks! I get what you mean, and I will definitely try to add something in the future, once I get this v2 stable. My take is that we want to have some sort of “idea tracking” utils: mind-maps, storyboards, moodboards, scratchpads or a combination of those.
About the tabs: v2 does not have split layout (yet?) but we do have full multi tab support and I thinks it is a huge step up:
Thanks for the feedback! great suggestions!
-
Grid snapping. +1
-
sub-graph node (or grouped node with it’s own input and output), (+1)
-
comment node (or note). (+1)
-
Scripts: Repeatable properties should be easier to input. – Yes, have autocomplete for actors and commands in scripts. I’m considering some sort of template system for the other editors
-
More node types like purpose node, condition node, random node (for success rate), trigger node (link to quest for event trigger).
About the last bit, how would differ with the script node? I wouldn’t want to try to cover all the possible nodes logic, and should be implemented by the user. Maybe some sort of node labeling for the common script node?
Thanks as usual for the feedback!
In v2 we have a registered protocol drafft://
which is used by internal links and the app will use them to route to a document if it founds it. this has the benefit of being used even outside the app, (a chat message for example – need to test it in different platforms yet)
so drafft://scripts/script-unique-id
will focus the app, create a new tab, load that document on it, and focus that tab.
this is also usable in gdds (with a nice ui picker) to link between differt documents
New endpoints are a great idea, add it to the wishlist.
Thank you again!
Yes I can see the issue, in my case, in arch, I use appImageLauncher which conveniently moves the .Appimage into a specific folder and “integrate it” into the system. But I agree this goes against the appimage portable principle :)
I took the liberty of using your explanation (with credits) on the new website (wip) , hope its ok! http://drafft.dev/docs/troubleshooting/app-armour-issues