When using the scissors, we still have a malfunction in some operations. This applies to ver.2.0.04 and RC versio.
I think it’s an old saying and I’ve reported it quite a few LB versions before.
When using the scissors, we still have a malfunction in some operations. This applies to ver.2.0.04 and RC versio.
I think it’s an old saying and I’ve reported it quite a few LB versions before.
Interesting! How is Lightburn supposed to know which end of that red line to jump to?
I think it is made ambiguous because you have a 3-line corner, which is supposed to be a violation for vectors. Do the Marching Ants travel along the red line AND the tab?
What happens if you put a Break in the line indicated by the red one?
Can you upload the .lbrm2 file? I am not sure how you added that tab and I would like to play with it. ![]()
Hi Mike, I can’t remember or find the file I’ve been working on, I’ve been very busy here the last few days. I just managed to make the screen dumps and continued my work. Typically with finger joint tasks I’ve seen it.
As I said, the problem has been there before and I actually think it was fixed…, but now the error is there again.
I’ll save the file itself the next time it happens ![]()
This is the documentation I made last time.
Scissor-Test.lbrn2 (4.3 KB)
Figured it out, I think. It is because the small square is a separate object from the big square. For all it is worth, it could be on a different layer.
Image #1 shows what you are operating on. That little box shares nothing in common with the big one. It is the same X & Y, but not the same Z (one [big] is on top of the other [small]).
In Image #2, we see what you are claiming. It makes what appears to be a wrong choice. But still the small square is not part of the A-B-C-D vector and gets ignored. We have to somehow bring them together. Otherwise, Lightburn does not see the small square as part of the A-B-C corner. In other words, it has no way of knowing whether to go to A-C or A-D with the Snip.
By selecting the small square and not the large (see Image #3), we flatten out the vectors and remove the correct segments of the small square (Snippit Tool took the mouse focus, and my red lines, so I penciled them in). A second application of the Scissors Tool takes out the corner as expected. The is the same end result as the Boolean Assistant, but is actually performing a different type of operation on that corner.
I am not sure how the developers can flatten both squares and still maintain the integrity of the small square, which may get different operations on it.
It appears that LB fails because the smaller rectangles have edges that overlap on the larger rectangle. If you select the smaller rectangles and break them apart, then manually delete the smaller rectangle lines (in red) that overlap the larger rectangle, the scissor then works.
I don’t know about you guys, but I am having fun with this ![]()
This happens primarily at the corner objects. The selection is correct but the result is not what the selection suggests/planned, that’s what’s confusing. It’s not the piece to the nearest node that gets cut - even though it’s marked as the one being processed.
The small squares are the same and are aligned to the large square, without gaps or overlaps.
Btw. The scissors also work and interact fine across layers in the same project ![]()
It’s always fun to find out why things work the way they do - or why I don’t understand how it works ![]()
I know, but only if the right conditions are met.
I agree we have a BUG. I went back in with a fresh copy and selected the small square (marching ants). This time, it does not remove a segment of the small square, but the large one instead. It appears what I did is not repeatable, but that does not negate what is happening.
I thought the difference was that I move the small squares to the C1 layer, but I shut down and restarted it all with a fresh file.
As a programmer, I learned when things are not repeatable using the same simple series of keystrokes, that is a bug.
@JohnJohn , I think we have something interesting for the programmers to investigate. ![]()
Addendum: I did a Boolean subtract on the other 2 small squares, then tried the left one. I got even a 3rd result (could only delete 1 of the small square segments A-B using the Scissors Tool, but not the B-C one although the small square was still selected).
There are two of us now! ![]()
Interesting.. thank you for sharing a sample file. Is this on the MacBook Pro listed in your profile? (Big Sur 11.6.3)
I agree. I appreciate all the enthusiasm, testing and sharing. It goes a long way to contributing to the quality of the software. Looking forward to testing, replicating the issue and reporting as well.
Again, thank you!
Acer i5, 250Gb HD, Win10
Acer 27" monitor, laptop display not on (no multi-screen)
LB v2.0.04
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.