kevboh / longform

A plugin for Obsidian that helps you write and edit novels, screenplays, and other long projects.
Other
664 stars 31 forks source link

Moving a scene from one project to another fails to prompt-to-add in the latter project #117

Closed KennyRN closed 1 year ago

KennyRN commented 1 year ago

Longform 2 is a vast improvement upon LF1.

However I'm having a similar issue with 2 which caused me to drop 1.

When I create a project I don't create a 'full' project (as in a full book), but part of a book and I move scenes between projects depending upon their status.

Currently I've got 2 projects which help me keep track of my book: 0) (not a project) Scenes being worked upon (as in unfinished scenes). 1) Need Editing / To Be Uploaded 2) Uploaded

It's not as easy as I would like to move scenes between each project. Would it be possible, please, to add some way to easily move scenes between projects.

Thanks :)

kevboh commented 1 year ago

If you move the note (in the first-party Obsidian file explorer) Longform should detect it and prompt you to add it in the new project (and will remove it from the old one). If that's not happening please let me know.

KennyRN commented 1 year ago

It doesn't quite work like that for me, sadly.

Moving from 0 to 1, yes, that works well. (Sometimes I need to pop into the Longform project first, and then move said scenes.)

It is in moving from 1 to 2 is where I've got the pain. To work constantly I've got to move the scenes into a random folder (I end up using the container folder which holds the 2 projects). Then pop into the Longform project. Then move the scenes. After doing that, finally I get the button to add the scene to the project (which I love, thanks, that's great).

(and thanks for the reply, if you're interested I can send you a series of screen shots next time I'm doing this)

------ Original Message ------ From "Kevin Barrett" @.> To "kevboh/longform" @.> Cc "KennyRN" @.>; "Author" @.> Date 12/11/2022 16:55:51 Subject Re: [kevboh/longform] Moving Scenes Between Projects (Issue

117)

If you move the note (in the first-party Obsidian file explorer) Longform should detect it and prompt you to add it in the new project (and will remove it from the old one). If that's not happening please let me know.

— Reply to this email directly, view it on GitHub https://github.com/kevboh/longform/issues/117#issuecomment-1312526514, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4EUIRLKQKNEZQ5TB4R6M2LWH7DZPANCNFSM6AAAAAAR6HMEP4. You are receiving this because you authored the thread.Message ID: @.***>

kevboh commented 1 year ago

Ah, interesting. So, to restate: moving a note from an existing Longform project to another Longform project doesn't show the prompt to add the scene, but moving a note from a non-project to a Longform project does?

If so that's a pretty clear bug. Let me know if my summary is correct and if so I'll retitle this and look into it.

KennyRN commented 1 year ago

Kevin, that's correct.

I cannot move a note from a Longform project to a Longform project and get the prompt to add the note.

------ Original Message ------ From "Kevin Barrett" @.> To "kevboh/longform" @.> Cc "KennyRN" @.>; "Author" @.> Date 28/11/2022 13:58:18 Subject Re: [kevboh/longform] Moving Scenes Between Projects (Issue

117)

Ah, interesting. So, to restate: moving a note from an existing Longform project to another Longform project doesn't show the prompt to add the scene, but moving a note from a non-project to a Longform project does?

If so that's a pretty clear bug. Let me know if my summary is correct and if so I'll retitle this and look into it.

— Reply to this email directly, view it on GitHub https://github.com/kevboh/longform/issues/117#issuecomment-1329153129, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4EUIRKSNYEO5JKXFXZYCC3WKS27VANCNFSM6AAAAAAR6HMEP4. You are receiving this because you authored the thread.Message ID: @.***>

kevboh commented 1 year ago

This should be fixed in the next release.

kevboh commented 1 year ago

Fixed in 2.0.2.