Issues with 'Pieces'

Bug Reports / Issues
1

Hi all, After the update (and repeated installation according to the bug fix), I am now unable to view the properties of any previously created ‘Piece’ (P), nor can I create any new ones (N,P). The currently existent pieces’ properties were viewable and editable.

If I select any piece and right-click Properties / or type ‘P’ the window is locked and responds with an unpleasant Windows ‘Bloinnggg’

On creating a new piece, and following the rules for that operation, the procedure ends without apparent errors, but there is no new ‘Piece’ present. I even zoomed out to see if it was hiding from me, but there was nothing to see.

I would appreciate any tips / hints / ideas on this … BTW: I have a projector (Epson EB-685W) and the images from existing PDFs and SVGs are projected quite well … but seam allowances (red) don’t show up properly and some cut lines on curves are ‘spotty’ to missing entirely. Remedies such as changing the colours (webApp Pattern-Projector.com) were also not successful! Can these ‘Cut-lines’) be set bolder / as bold as the normal lines?

2 Likes
2

One additional information: although no error message appeared, there was also no follow-up dialogue - the initial properties setup I believe.

1 Like
3

You can set the pref for cut lines in Pattern->Paths->Cut line:

image
image578×623 47.8 KB

2 Likes
4

You have to select a piece 1st… which will show the bounding box:

{8BEB4979-F927-4938-8A34-193B5E0A4AB2}
{8BEB4979-F927-4938-8A34-193B5E0A4AB2}165×305 8.63 KB

Then you can use the P shortcut.

Or you can just use the right mouse button context menu:

{C45E699E-55F9-4866-8D14-6F4A95B9E18A}
{C45E699E-55F9-4866-8D14-6F4A95B9E18A}377×428 16.4 KB

The N,P is only for use in draft mode:

{64E21FBB-1611-46E7-A4C3-C6E213573B29}
{64E21FBB-1611-46E7-A4C3-C6E213573B29}243×120 5.08 KB

I just tried it with this week’s build (4/20) and it works fine for me.

1 Like
5

That / those steps is/are exactly what is non-funtional :roll_eyes:

1 Like
6

I have done all that + restarted windos + re-installed seamly … still no ‘joy’ …

1 Like
7

Do you have the piece(s) locked?

Screenshot 2026-04-23 124001
Screenshot 2026-04-23 124001244×244 6.06 KB

Locked pieces will not open the Properties…

{3CABA1D0-DB0B-4729-BB53-2D3D2541793F}
{3CABA1D0-DB0B-4729-BB53-2D3D2541793F}403×154 7.17 KB

1 Like
8

BTW… another way to open unlocked properties is by double clicking a piece in the Pattern Pieces dock:

{A8E6B46F-911D-42F4-A415-5CB24F42E60B}
{A8E6B46F-911D-42F4-A415-5CB24F42E60B}430×256 11.5 KB

1 Like
9

image
image1575×1104 80.8 KB

With the difference that after the n-th attempt, I did manage to creat a Piece in a new ‘virgin’ pattern, but as before, it is not possible to access the properties of the object.

1 Like
10

OK… I think I can see what might be going on. Something is probably not right with the seam allowance and youre unable to select pattern piece. Try the double clicking method… it by passes the need to select the piece.

2 Likes
11

@DavidDeb

Please share one of your patterns that is having problems, along with its measurement file.

Thanks!

1 Like
12

@Douglas / @Sue Hi guys, sorry for the delay …

I wrote a really long piece this morning, but it seems that I did not hit ‘Send’ (WTF!) and its gone now.

The bottom line: The ‘issue’ and cause (both ‘me’!) has been resolved. I had in the dim & distant past, a second monitor, which I was using for various apps (Seamly2D too) … I then removed the monitor and forgot about the settings!

When I attached the projector (:= Monitor#2) the properties dialog was sent to this device. This occurred to me during the night and I corrected this today at 06:30 CEST (currently 17:39 )

Sorry for the kerfuffle :roll_eyes:

2 Likes
13

I had to check… and I’m not sure why that was the case… it should not have mattered that the 2nd monitored was removed as I accounted for that:

// If second monitor exists and user pref is to use second monitor, open dialogs on second monitor.
if (qApp->Settings()->useSecondMonitor() && (screenList.count() > 1))
{
    m_screen = screenList.at(1);
}

But then I never checked by unplugging my 2nd monitor. I would think Windows is smart enough to remove the 2nd monitor from the list of available screens without having updated the system settings… but then I could be wrong. :thinking:

2 Likes