(2024-12-03, 17:19)Cam's Bricks Wrote: I have just had this thought again and if its not possible to to add basically a check box on this dialog to create a bin for the selected folder, then would it be possible to have a tool to make a bin file from the contents of a folder?

(2024-12-04, 20:46)Roland Melkert Wrote: I could add a button to generate a pbg for a user location, but it isn't guaranteed to appear as you expect as pbg content is always loaded against the current search path order.

Quote:I am just trying to see my custom parts in a parts list that is at least semi-automatically, if not fully automatically, generated manner so I dont have to update the pbg every time I add a new part or parts to my library. 

(2024-12-04, 21:08)Roland Melkert Wrote: I forgot I added a location name field to the upcoming beta2 and filter options for them in the filtered pbg's.

So what you want is already kind of possible in beta 2. You just need a unique name for the user location(s) and add a custom pbg filtering on it.

It still will load trough the search order mechanics, meaning a 3001.dat in your user folder will only show in the bin if your user location is above the official library.

(2024-12-05, 16:32)Cam's Bricks Wrote: So I would need to have a filter PBG that will say look in \Trained_Bricks_Rods and then it will show those parts in that folder?
Just a bit lost on how this all works. Thanks for your help.

(2024-12-05, 18:42)Roland Melkert Wrote:  (so you must use a parts folder inside the root one.)

example pbg:

Code:

[options]
kind=filter
caption=Custom parts
description=My custom parts

<rules>
include libName myCustomParts

(2024-12-05, 19:23)Cam's Bricks Wrote: So it has to be in the LDraw root folder to be included? I can manage that.

(2024-12-05, 19:39)Roland Melkert Wrote: No it has to be a library location meaning it has (a) parts and/or p subfolder(s). These should always be parallel to the official one. Using a location inside e.g. the official library WILL mess things up.

Quote:etc?

(2024-12-05, 19:53)Roland Melkert Wrote: More like:

d:\LDraw\myParts  -> use in prefs dlg
d:\LDraw\myParts\parts  -> your custom part .dat's
d:\LDraw\myParts\parts\s -> if needed
d:\LDraw\myParts\p -> curstom prims if needed.

this along side your other libs, e.g

d:\LDraw\complete.zip

or unzipped

d:\LDraw\2410

(2025-02-10, 5:30)Yx Wang Wrote: I found the 1.7 version default does not include brick with modifier in the plain brick catalog. While 1.6 version does. I tried to do a clean install but it still couldn't sort the library. I tried this among all three windows computer and a mac.

(2025-02-10, 5:30)Yx Wang Wrote: On one computer I downgrade 1.7 back to 1.6 under same directory, all the font is gone and this happened to both windows pc and a mac.

(2025-02-10, 20:43)Roland Melkert Wrote: I changed the default bin configuration with 1.7, the old group has been split into two: with and without patterns. You can go back to the old configuration if you want by replacing the partBin folder of 1.7 with the 1.6 one.

(2025-02-11, 1:20)Yx Wang Wrote: Since I switched from studio is there a way to change this sorting similar to the one with the studio one? I found that one breakdown each item in much detailed path. I just found some parts info at C:\Users\XXX\AppData\Local\Stud.io\NewParts.
But the files under C:\Program Files\Studio 2.0\ldraw seems unsorted and files under C:\Program Files\Studio 2.0\data has such a different structure from LDCad partbin.

(2024-01-11, 0:51)N. W. Perry Wrote: On MacOS under Wine. The problem first occurred under Ventura, and an upgrade to Sonoma didn't fix it. Wine version is the Crossover FOSS 23.0.1 but I also got the error under Wine Stable 8.0.1.

I'm also able to confirm that it's the off-screen issue, by choosing Show All [program] Windows from the dock. Then the missing window will appear, and indeed it's a tiny little sliver of a thing. But if I click that window preview to activate it, it goes back to its far-away position and is hidden again.

EDIT: Two things…

First, it is an error with any drop-down menu (not just from the manual rotation dialog). When you open a drop-down, the new pane will appear as a blank void with no menu options displayed. If you then move the dialog menu window, the drop-down pane will now populate with the menu options—but it will stay in place and not follow the window as you move it around. You can then dismiss the dialog using ENTER or ESC, but not until you move the window again will it actually go away.

It's at this point that the program appears to be hung, as window inputs are no longer responsive. You can now quit the program via hotkey, but nothing will happen until, once again, you try to move the program window. Then, the program will suddenly quit (or ask you to save changes, if any). But it will save the config file with those weird window dimensions I posted earlier.

Second, the error does not occur under Wine 8.0.2 (and Wine 9.0 also seems to be OK). But you can see a hint of it, as the drop-down menu pane will still be stuck in place as you move the dialog window, but it will then jump into its proper place and function normally once you put down the window. So I'm not sure if the problem is in Wine itself, or something about LDCad, but it does seem to affect Wine Crossover specifically (which is just Wine 8.0.2 but with Codeweavers' flavor added somehow).

(2025-03-10, 7:17)Yx Wang Wrote: I had exactly the same issue but just before the error occur. I can confirm there was some error showing prior to the frezze up in the terminal. I do not have that error in hand though. My wine version is 10.0 and LDCad was 1.7 Beta 1.

(2025-03-10, 8:32)Roland Melkert Wrote: I'll upgrade wxWdgets to the latest version for beta2, hoping it will fix this.

It's the only thing I can do as far I know.

(Yesterday, 8:18)Yx Wang Wrote: I'm not quite sure does this has anything todo with the sudden freeze up. Today it did crash again. But it did not show any error in the terminal.

(7 hours ago)Roland Melkert Wrote: This is most definitely a wine problem.

Did a quick search and it seems this kind of problem acts up on the mac branch now and then, going back as fas as 2008.