USER FORUM
(you are viewing a thread; or go back to list of threads)
linking dimensions, and reopening a crashed file (by Jim G)
I have two questions:
1) I'm creating an assembly composed of several individual parts that bolt together. The spacing between the bolt holes of mating parts needs to be the same. I have been creating a sketch of each of the bolt hole patterns, then linking these sketches to the parts and extruding them. It works, but the file size is larger than simply extruding the holes directly in the part when the part is extruded. Is there some way I could link dimensions between features of parts, e.g., the spacing between bolt holes?
2) I created a file using Solvespace 2.3 on my ARM-powered single-boad computer running Debian 8, but it hung while doing an extrude. I tried to reopen it but it hung up again when I selected "retry opening file". Now it hangs when I open th efile, and I'm not given either option of reopening last saved. How can I get back to a state where I can reopen the file? The error I'm getting, FWIW, is:
The program 'solvespace' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 1120 error_code 8 request_code 73 minor_code 0)
I can attach the file, but it's linked to other files.
1) I'm creating an assembly composed of several individual parts that bolt together. The spacing between the bolt holes of mating parts needs to be the same. I have been creating a sketch of each of the bolt hole patterns, then linking these sketches to the parts and extruding them. It works, but the file size is larger than simply extruding the holes directly in the part when the part is extruded. Is there some way I could link dimensions between features of parts, e.g., the spacing between bolt holes?
2) I created a file using Solvespace 2.3 on my ARM-powered single-boad computer running Debian 8, but it hung while doing an extrude. I tried to reopen it but it hung up again when I selected "retry opening file". Now it hangs when I open th efile, and I'm not given either option of reopening last saved. How can I get back to a state where I can reopen the file? The error I'm getting, FWIW, is:
The program 'solvespace' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 1120 error_code 8 request_code 73 minor_code 0)
I can attach the file, but it's linked to other files.
(no subject) (by User1)
Could you give your file, where last step not applied?
(no subject) (by whitequark)
The error you're getting is indicative of a graphics driver bug. Do you think you can check if the bug still reproduces on master?
You can attach all the files by putting them into a zip archive.
You can attach all the files by putting them into a zip archive.
(no subject) (by Jim G)
To update to master, I'll need to upgrade to Debian 9, as master now requires gtkmm 3.0 >= 3.16 while the latest version available in Debian 8 is 3.14. Give me some time and let me see what I can do.
graphics problems with master (3.0) (by Jim G)
I compiled master on my ARMv7 single-board-computer, this time running Ubuntu 16.04. I don't seem to have the crashing problem I had before, but the window menu (File-Edit-View-etc.) is not displaying consistently.
It sometimes looks normal, sometimes only a portion of it shows up, sometimes parts of it show up in blocks (i.e., without a full background), and sometimes it doesn't show up at all unless I mouse over it (especially at startup).
Attached is a composite image of how it looks at different times. FWIW, I'm running the XFCE window manager. I didn't have this problem before running (precompiled) v2.4 on XFCE.
It sometimes looks normal, sometimes only a portion of it shows up, sometimes parts of it show up in blocks (i.e., without a full background), and sometimes it doesn't show up at all unless I mouse over it (especially at startup).
Attached is a composite image of how it looks at different times. FWIW, I'm running the XFCE window manager. I didn't have this problem before running (precompiled) v2.4 on XFCE.
(no subject) (by whitequark)
Yes, this is a known issue on master.
Post a reply to this comment: