When I move a Scapple mind map into Scrivener, as described in section 9.5.4 of the Scapple manual, this is the result:
[attachment=1]Screen Shot 2021-01-11 at 7.27.51 AM.jpg[/attachment]
I don’t remember that being a problem in the past. Is there a way to make this work??
PS When I move old maps into Scrivener, they display properly:
[attachment=0]Screen Shot 2021-01-11 at 7.38.33 AM.jpg[/attachment]
What version of Mac OS? What version of Scrivener? What version of Scapple?
What you’re actually seeing is the Mac OS Quick Look preview of the Scapple file. So it’s unfortunately not something that we have a lot of control over, from either the Scapple or the Scrivener side. Alternatives would be to import as a PDF file, or to open the file in Scapple directly.
Feel free to move this to the Scapple forum.
Mac, Scriv, Scap versions: 11.1, 3.2.2, 1.4.
I don’t want to sound confrontational, but:
Like the resolved problem with the jagged or cloud Scapple notes, you do have control over how Mac displays your maps.
This happens within Scapple also. If you load the attached Scapple file, and move one note from one to the other, you’ll see the same issue. To get this, I dragged and dropped the note “Desires” from one Scapple mind map to the other.
[attachment=0]Screen Shot 2021-01-11 at 3.03.21 PM.jpg[/attachment]
[attachment=1]Scene Louella Discusses Arthur.scap[/attachment]
Moving to Scapple forum.
Mentioning up front that the same problem appears in Scapple itself would have been helpful.
Bug reports are most likely to reach the appropriate person if you open a support ticket, here:
I didn’t realize that until after I started this thread, when I started debugging it. That is, I wanted to see why some maps displayed okay, and when I dragged something from a known bad map to a test one, I saw that the problem happens in Scapple also.
I suspect this is related to the fix to the jagged/cloud, but I don’t have time to continue investigating it.
Are you seeing this happening with any newly created boards? If so, it may be related to this bug, that we spotted shortly before going on holiday.
New boards will have a larger amount of padding around notes, while older boards retain their original padding for the sake of maintaining original layout. If we didn’t do that, then you would get results exactly like this in the board itself. Note in that thread, the bug is in printing and exporting to PDF—we forgot to add the backward compatibility code to those functions it looks like. The issue may be the same for the Quick Look engine.
If you can confirm it only happens with old boards, then I’ll add it to the list for that specific bug. And note that in that thread I linked to, there is a workaround you can use to “upgrade” a board to the new padding model.