Bug 345630 - connect shapes does not save lines correctly
Summary: connect shapes does not save lines correctly
Status: REPORTED
Alias: None
Product: braindump
Classification: Applications
Component: application (other bugs)
Version First Reported In: 0.10.9
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Cyrille Berger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-28 23:17 UTC by Luke
Modified: 2021-03-09 05:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke 2015-03-28 23:17:57 UTC
Multiple shapes can be created and laid out fine. They can then be connected by using the "Connect Shapes" button and drawing the lines from node to node.
The lines will draw fine with each type of line, standard through to curve.

However, the lines will not save correctly. It appears that the lines will save in the whiteboard, but upon reloading, they will be bunched together in an area the same size as a single node in a seemingly random place on the whiteboard.

The lines can be scaled back up to the correct size manually, and placed in the correct place. But once again on a quit+reload, they will be bunched together in a single node size.

other types of lines drawn free-hand are unaffected, only the lines drawn by connecting nodes will not save correctly.

Reproducible: Always

Steps to Reproduce:
1. Insert two shapes and connect with a line from a node each.
2. Quit the program.
3. Reopen the program.
4. Lines will be bunched together in one spot the size of a node.

Actual Results:  
Node connected lines are bunched together in a single spot. upon reload.

Expected Results:  
Node connected lines should be saved correctly and reloaded, connected to the nodesthey were drawn to.

Same results from Arch standard package repo, as well as AUR git compiled, and also fresh git compilation.
Comment 1 Justin Zobel 2021-03-09 05:27:06 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.