LDCad 1.5 Beta 1 (win+linux)


LDCad 1.5 Beta 1 (win+linux)
#1
Hello all,

It took over a year since 1.4 Beta 1 but I'm hoping it is worth the wait / time spend.

For those who somehow missed the massive 1.5 Alpha thread on the forum, the major new features of 1.5 are:

Detachable color and part bin windows, of whom you can have multiple instances or none at all.
Extensive (optional) LDraw source window, with full nested editing support and a growing selection of line type property editing dialogs.
LDraw file reloading and external changes detection, and you can finally close files now.
Library part (shadow) editing, mostly intended for myself in order to add part snapping info so it is disabled by default and far from a full LDraw part editing solution.
Compressed (e.g. complete.zip) library support.
Single instance protection.

There are also loads of minor improvements etc, some of which are:
Better scrollbar handling
Bin window(s) can be used at a smaller width.
Part bin windows can render vertical or horizontal orientated.
And many more tweaks and adjustments etc.

I also added almost 600 new part snapping files to the default shadow library including info for doors, windows, windscreens, fences, bars, antenna's, plane parts, boat parts, minifig hats/hair and minifig accessories. Do note some (especially the doors and windows) need some additional work as I'm not sure how they behave/fit in real life any help on that is welcome.

Here are a couple of screen shots showing possible window configurations.

The 1.5 mascot example

An alternative layout

Editing shadow (snap) info

And I will add a new youtube demo clip later, if there is something particular you would want demonstrated feel free to ask.

As always the new version can be found at
http://www.melkert.net/LDCad/download

The windows setup version can be used to upgrade any previous version including ones installed by the AIOI.

I will update the documentation on my website to reflect the newest version in the next couple of days / week. For now the only thing you might need to know is how to dock windows. This is done by holding down 'ctrl' after you position the loose window roughly at the place you want it to go.



Lastly there might still be a problem with occasional crashes during closing the program at seemingly random intervals. I have tried a number of things to fix this and I haven't had a crash since the last adjustment myself, but as it might sometimes take days between occurrences I'm not sure it's really fixed.

So if you do have a crash on close down, please send me the contents of the logs folder as I added some extra messages to help pinpoint the crash location. The crash it self is relatively innocent as it will only result in a failure to write/update configuration files as it happens fairly late in the shutdown procedure.


Hope you like the new major version, any feedback / questions / suggestions are welcome.


Attached Files Thumbnail(s)
           
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#2
I'm loving it so far Roland, thank for all your continued hard work.

I did my usual dark mods to the gui, really enjoying the flexibility with the layout now.

   
______________________________________________
OS = Ubuntu 14.04 LTS (64bit)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#3
Nice work.

Here is the layout I find most useful:
[Image: 800x482.jpg]

Once I get sufficiently inspired, I'll make some icons for the toolbar functions that are missing them.

Owen.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#4
So I imagine if I fire up my second monitor again I should be able to drag all the tools to one side and have a full editor canvass on the other side?
______________________________________________
OS = Ubuntu 14.04 LTS (64bit)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#15
Jason Smith Wrote:So I imagine if I fire up my second monitor again I should be able to drag all the tools to one side and have a full editor canvass on the other side?
At the moment this is only possible if your (dual head) graphics card supports it and you stretch the application window it self across both screens. I do plan to add the possibility to open a second os level window containing a second OpenGL context / panel in a future version though.

I myself have two screens but I usually end up using the second to display the building instructions site/pdf so I didn't think it would be really needed Smile
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#5
Okay, I'm sure I've missed the answer already somewhere but how do you lock the newly placed windows so they remain on startup. Also would locking that get rid of the top window header with the close button as you can see in my above ss.

EDIT: I have clicked on the "Lock docked Windows" in the GUI menu but it doesn't do anything.

EDIT2: I'm clearly doing something wrong as my main model panel (top right) gets buried and so does my compass.
______________________________________________
OS = Ubuntu 14.04 LTS (64bit)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#6
Jason Smith Wrote:...how do you lock the newly placed windows so they remain on startup.

If I create a new window, docked or just floating, it appears again the next time I open the app. Maybe try uninstalling and re-installing this beta version.

Jason Smith Wrote:Also would locking that get rid of the top window header with the close button as you can see in my above ss.

"Lock docked Windows" just prevents you from dragging the docked windows you have somewhere else, you can still re-size them though. Also, if you dock a window it gets rid of the header bar with the "X" button. I haven't played with it much, but just did some testing and you can see a screenshot of what I threw together for testing. If I close and re-launch, they all come back.

   
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#7
Played with a new install and same thing. I can't get rid of the header on top of the new windows probably because the windows aren't docking or sticking, not sure what they're supposed to do.

3 images attached.

1st - windows setup before closing, 2nd - Opened after closing. 3rd - With model open, you see the compass just peaking out on the bottom left and the upper right panel is hidden under the parts window.


Attached Files Thumbnail(s)
           
______________________________________________
OS = Ubuntu 14.04 LTS (64bit)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#8
Jason Smith Wrote:Played with a new install and same thing. I can't get rid of the header on top of the new windows probably because the windows aren't docking or sticking, not sure what they're supposed to do.

3rd - With model open, you see the compass just peaking out on the bottom left and the upper right panel is hidden under the parts window.

Based on your screenshots, your windows aren't actually docked, they are just floating, and if they are floating they will cover up the compass and the session panel. If you want the compass and the session panel to be visible, you'll have to dock the windows and that will "push" them out. To dock a window, get it close to a side where you want it and then hover the mouse over it, press ctrl and then left-click and drag it to the side you want to dock it to (FYI, this is mentioned in the first post by Roland Smile). That should dock it and get the header out of the way. It will also push the compass and the session panel into view.

Jason Smith Wrote:1st - windows setup before closing, 2nd - Opened after closing.

As far a why it's not saving the layout, I don't know. I set mine up just like your screenshot and when I closed and then re-opened it they were all still there and in the same/correct positions. For information, I'm running this on Windows 10.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#14
Jason McReynolds Wrote:As far a why it's not saving the layout, I don't know. I set mine up just like your screenshot and when I closed and then re-opened it they were all still there and in the same/correct positions. For information, I'm running this on Windows 10.
This might be a Linux only issue as I noticed before the main application window sometimes starts very small on xwindows. This probably caused the saved window positions to be truncated to keep them inside, I'll look into this issue.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#9
Those windows aren't docked: they're still floating, but you've resized them to look as though they're docked.
To dock a window, hold down CTRL while you're placing it.
When they're docked, they won't cover up the compass etc.

I can't speak for the repositioning on startup though. But that problem should fix itself once the windows are docked properly.

Owen.

EDIT: Beaten to the punch, it would seem.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#10
Thank you Jason, the control method worked and I'm a fool for not reading it in the first post. The windows also persisted when opened again so I guess they must need to be docked to remain in position. Wow, all this cause I didn't read a line... Sad To be newbie friendly I vote for a simple right click dock option.

I'm having a lit bit of trouble placing a couple side by side, they just want to go full width, I'll keep playing.

Thank you as well Owen.
______________________________________________
OS = Ubuntu 14.04 LTS (64bit)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#12
This is a excellent exchange on expected usability.

I too struggled to understand the docking procedures on my first experience - I found it in an exchange on eurobricks somewhere.

I imagine there are probably very good reasons why LDCad's docking functionality was implemented in a very non-standard manner - like having your car's accelerator on the paddles behind the steering wheel - but to the unsuspecting user it can often be painful.

I also vote for a simple click-and-drag dock/undock function. I also vote for a solution that can undock outside the application window.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#16
Trevor Sandy Wrote:I imagine there are probably very good reasons why LDCad's docking functionality was implemented in a very non-standard manner - like having your car's accelerator on the paddles behind the steering wheel - but to the unsuspecting user it can often be painful.
As far I know the ctrl key usage is fairly common, only difference being it usually prevents auto docking during dragging. Something I found very annoying as the window will jump all over the place, so I inverted the key sort to speak.

Trevor Sandy Wrote:I also vote for a solution that can undock outside the application window.
This is something I would like to add at some point. At first I was thinking to keep it for version 2.0, but as I don't see myself starting from scratch anytime soon I'll probably try something in 1.7 or something Smile
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#11
Hello Roland.

I was curious what is the difference between last Alpha and this Beta and I must say I'm fascinated! Of course, because of the snap info editor. It was easier to add missing snap info to the part then to place it manually to minifig's hand. Great!

One does not need to start MLCAD any longer and the created snap info is ready to use immediately, with no LDCad restart, no reconfiguration of ldraw library paths etc. I simply have two models open: the main one and the one with the part to fix. That's great not only for the main work but even for testing of the snap info correctness.

Unfortunately, I was not able to save the new information in any way then. Is that a bug or I missed something, please?
My workflow:

Saving:
1. turn snap editor on and click on the "Edit" icon of the desired part
2. new model for this part is open, add/fix the snap info there
2a. LDCad warns me that the original snap info comes from the zip file and so I'll have to save the result elsewhere
3. pressing "ctrl+S" does not cause any error message but saves nothing (expectable, after that warning, but some message would help here)
4. "File"->"Save as" menu item is grayed out so I cannot save it under another name or path
So what to do?

My workaround attempt:
Copy desired source file lines to the clipboard and edit the shadow file in the external editor (add header lines and save it to the parallel path as suggested in shadow/readme)

Using:
How to use that file? The ldraw configuration dialog does not allow two shadow paths for one library line. I can neither add another line with the same library path but different shadow path. Note this is a different case than with Unofficial parts: I have edited the info of the official part so (I believe) this info must be "coupled" with the official library of parts.
So I used a trick: a copy (symbolic link) of ldraw directory on the filesystem. But that does not work, too. The new snap info is simply ignored. Moreover I do not want to have such symlink as a permanent solution Smile

So far, it's easy to fix the snap info but I'm able to use only that what I created in the current editing session. Help, Roland! Big Grin

Edit: The example file I created is attached now. To check if I understand the mechanism correctly.


Attached Files
.dat   u9180s01.dat (Size: 259 bytes / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#13
Hi Milan,
Your problem is that you try to edit the zipped version of the shadow library, and LDCad can't save your modifications in this format (here I got a warning telling me about the problem). What you must do is to open the shadow library file as a zip file (offLibShadow.csl in %appdata%\LDCad\shadow\offLib), extract its content in a folder, then change library location in LDCad to point to this folder (prefs->ldraw->search library paths).
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#17
They way Philippe wrote is the intended way of editing shadow files.

I usually have the official library compressed and the shadow library non compressed during shadow editing. This way you will be sure no official files are save to disk (this will otherwise happen when LDCad e.g. corrected the case of a type 1 line reference).

Milan Vančura Wrote:The example file I created is attached now. To check if I understand the mechanism correctly.
I somehow missed that one while working through the accessories group.

You info looks ok, I would add a bit more detail though, like so:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 5   R 3.5 15] [slide=true] [pos=0 40 0]
0 !LDCAD SNAP_CYL [gender=M] [caps=two] [secs=R 4 13.5] [slide=true] [pos=0 16 0]

And maybe also some hole info for the stud hole. But you version should be enough for most situations.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#26
Roland Melkert Wrote:They way Philippe wrote is the intended way of editing shadow files.

I usually have the official library compressed and the shadow library non compressed during shadow editing. This way you will be sure no official files are save to disk (this will otherwise happen when LDCad e.g. corrected the case of a type 1 line reference).
Thank you both, Philippe and Roland. I misunderstood the warning because I hoped for a separate path of modified shadow files. However, this is not possible, true? So I extract the zip archive before running LDCad and use the 'diff' command later to find my changes I want to send you, Roland, back.

Roland Melkert Wrote:You info looks ok, I would add a bit more detail though, like so...
OK, I study the documentation Smile

Roland Melkert Wrote:
Philippe Hurbain Wrote:Great job on connectivity editing! It's a pleasure to be able to define connectivity and test it at once in the same session.
Thanks, but I must say it was mostly for my own convenience Smile
Hehe Smile I hope we already showed you the opposite is true! This is THE feature, pushing LDCad to completely new level of usability. Really great job!

One of this feature effects is that more people can contribute the snap data and (hopefully) save some of your time.

About the repository: good idea! I just, if I can, recommend git even you are familiar to svn so far - with git, you do not need to handle user rights (because we'll not need the write access), merging of branches is no longer a headache and, most important for you: you can see every commit as an e-mail (or "submit request") before you apply it to your tree. What saves a lot of time of the tree maintainer.
Of course, I'll respect any repository format you setup, I just wanted to share some years of experience to help you...
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#31
Milan Vančura Wrote:
Roland Melkert Wrote:
Philippe Hurbain Wrote:Great job on connectivity editing! It's a pleasure to be able to define connectivity and test it at once in the same session.
Thanks, but I must say it was mostly for my own convenience Smile
Hehe Smile I hope we already showed you the opposite is true! This is THE feature, pushing LDCad to completely new level of usability. Really great job!

One of this feature effects is that more people can contribute the snap data and (hopefully) save some of your time.
Did not expect the shadow editing feature to be this popular indeed Smile

Milan Vančura Wrote:About the repository: good idea! I just, if I can, recommend git even you are familiar to svn so far - with git, you do not need to handle user rights (because we'll not need the write access), merging of branches is no longer a headache and, most important for you: you can see every commit as an e-mail (or "submit request") before you apply it to your tree. What saves a lot of time of the tree maintainer.
Of course, I'll respect any repository format you setup, I just wanted to share some years of experience to help you...
My preference for svn is probably the result of me using it as a single user for my daily work. And I might be a bit bias as I didn't like the tortoisegit installation which was massive compared to the svn one. And for some reason git wont store empty folders which is something I use quite often.

But I might try git anyway as this will be a secondary storage after all.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#34
Roland Melkert Wrote:Did not expect the shadow editing feature to be this popular indeed Smile
Sure it is. One does not need to wait only but can fix problems himself. Hurray!

For example I often plan my vignettes in LDCad so I want to go through Minifig Utensil and similar categories. It's improved a lot comparing to last Alpha but there is still some room for fixes. The first set of my suggestions is attached:

95528 Minifig Bottle Cylindrical - false snap surfaces deleted, caps added - plus it uses the improved stud2 now
0 ~Minifig Conical Flask - Neck - I improved my previous version using also your comment (even I do not know what can fit to the hole of diameter 3.5 other than electrical pin)
stud2 - I believe there is not a reason why it should not snap to bar-like ends - or is it?

Edit: I fixed my nick in file headers and added a dynamite Smile


Attached Files
.zip   mod01.zip (Size: 1.9 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#36
more accessories fixed, plus flowers and their stems as a bonus Smile

I have checked all these connections with real parts, to be sure. Esp. those which may be surprising. All of them work perfectly.

Only problem I have is a snap definition of binoculars: each snap itself works well but two binoculars, one behind the other, do not snap correctly. Only one half/ocular (left or right) snaps each time. Can you look at it, please, Roland?


Attached Files
.zip   mod02.zip (Size: 8.79 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#37
thanks for the mods Milan,

Milan Vančura Wrote:Only problem I have is a snap definition of binoculars: each snap itself works well but two binoculars, one behind the other, do not snap correctly. Only one half/ocular (left or right) snaps each time. Can you look at it, please, Roland?
I worked for me except it wend to far on one side (is that what you meant) which is caused by it having no caps. The aStud was also using caps=none instead of caps=one or was that on purpose?

I've corrected it, and replaced the identical ones with grid usage.
Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=two] [secs=R 4 13] [slide=true] [pos=0 0 -7] [ori=1 0 0 0 0 1 0 -1 0] [grid=C 2 1 12 0]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 4 6] [pos=0 0 -18] [ori=1 0 0 0 0 1 0 -1 0] [grid=C 2 1 12 0]
0 !LDCAD SNAP_CYL [gender=M] [caps=one] [secs=R 4 2] [pos=0 0 8] [ori=1 0 0 0 0 1 0 -1 0] [grid=C 2 1 12 0]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [pos=0 4 0]

I'll take a closer look to all your (and the other posted) files in the thread, and pack a new offLibShadow.csl later this week.

On a side note I've received some crash reports about using the part editor mode combined with the source window. So be sure to save often Smile I think using the window undocked makes it more likely to happen though, not sure though as I'm still looking into this hard to replicate bug.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#38
I've found the cause of my problem with binoculars: wrong expectation of mine Smile
In other words: you can ignore that report of problem, at least for this version of LDCad. It is a feature request instead.

Because what I did was I tried to move a (slightly) rotated binoculars behind another ones and expected the snapping algorithm to "match both oculars snap points" => correcting the rotation angle of the new part. However, this is not supported in LDCad for any part or set of parts, only one snap connection is used each time - am I correct?

However, what about an improvement of this feature in next LDCad version(s)?
* let the user to choose the snap point (e.g. a center + axis of SNAP_CYL) as an origin of coordinates for part rotation
* let the user to turn on (temporarily) the snap function while moving or rotating the part using keyboard

The idea is to combine both the above, of course: turn the hinge until it snaps the other part of the model etc. Or rotate binoculars until the part snaps to the other binoculars Smile

But not only that. One can use the second feature in case there is too many snap points in a small space. For example, it's difficult, sometimes, to place 40teeth gear on the axle because it snaps too often to pinholes instead of the central axle hole, esp. when viewing the gear from some angles.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#44
Milan Vančura Wrote:However, this is not supported in LDCad for any part or set of parts, only one snap connection is used each time - am I correct?
Yes currently the closest/best single connection is used to snap the whole dragged object. It will try to align the Y-axis though and for axles the roll. But still only for that one connection. I'm hoping to do multi connection matching in a future version but I'll have to figure out a efficient, multi threaded, way of doing it.

Milan Vančura Wrote:* let the user to choose the snap point (e.g. a center + axis of SNAP_CYL) as an origin of coordinates for part rotation
* let the user to turn on (temporarily) the snap function while moving or rotating the part using keyboard
How would you think choosing which connection to use should work in such a case?

Milan Vančura Wrote:The idea is to combine both the above, of course: turn the hinge until it snaps the other part of the model etc. Or rotate binoculars until the part snaps to the other binoculars Smile
The current 'official' way of doing that is to select the existing bionculars before adding the second one. This will cause the second one to use the same orientation normal and snapping does the rest. Alternatively you can set a relative grid and press home while dragging a new part to reset it to the grid orientation.

Milan Vančura Wrote:But not only that. One can use the second feature in case there is too many snap points in a small space. For example, it's difficult, sometimes, to place 40teeth gear on the axle because it snaps too often to pinholes instead of the central axle hole, esp. when viewing the gear from some angles.
Yes this kinda annoys me too, I've tried to improve on it by letting sliding part 'stuck' to their last matched hole so it at least wont skip to another when you finally have it at the right place Smile Letting the user choose a snapping point manually would solve this issue, but again how to do it gui wise.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#50
Roland Melkert Wrote:
Milan Vančura Wrote:* let the user to choose the snap point (e.g. a center + axis of SNAP_CYL) as an origin of coordinates for part rotation
* let the user to turn on (temporarily) the snap function while moving or rotating the part using keyboard
How would you think choosing which connection to use should work in such a case?
I believe this is possible to do because LDCad already has all functions we need to combine. This is my idea as an example:
Start with a selection. When user presses a hotkey (newly defined) LDCad shows a mark for each snap position in a similar way it already does - a function "show snap points (F11)". Just use a mark shape which shows the orientation of that snap as well - something like a little pyramid pointing to the direction of the snap object axis (SNAP_CYL etc.). Then user can click on such pyramid and local grid is set according to that.

Thanks to the LDCad design, the above is enough and we do not need anything like "a hinge mode" etc. Only what the user needs to be able to do is to find&select the local coordination system.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#54
Milan Vančura Wrote:* let the user to choose the snap point (e.g. a center + axis of SNAP_CYL) as an origin of coordinates for part rotation
* let the user to turn on (temporarily) the snap function while moving or rotating the part using keyboard
This sounds very doable, I'll take a look at it when I solved the current stability issues. Thanks.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#42
Quote:On a side note I've received some crash reports about using the part editor mode combined with the source window. So be sure to save often Smile I think using the window undocked makes it more likely to happen though, not sure though as I'm still looking into this hard to replicate bug.
Noticed that too, even with a docked window. I hoped to be able to get more significant diagnostic before reporting...
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#45
Philippe Hurbain Wrote:Noticed that too, even with a docked window. I hoped to be able to get more significant diagnostic before reporting...
It is caused by an outdated source tree cache, but I'm having a hard time finding where it gets out of sync.

Only thing I noticed it tends to happen after file reloads (f5) combined with an undocked window (on top of an editor). any click on a source line might crash it in that situation. It does so more often when used on a slower pc. (e.g. it will crash before the 3rd time trying on my old xp pc).
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#61
The rest of Plants category is fixed in this archive, plus some bonus parts.
Enjoy.

P.S.: For Sea Grass, even the trick with 'Ins' key was not fast and precise enough. I wanted an automatic solution. But that meant I had needed to remind pieces of my linear algebra knowledge, after more than 20 years. I must say I still feel loud mess in my brain as many neuron paths, freshly woken up, are upset and crying, surprised why they cannot continue to sleep Smile


Attached Files
.zip   mod3.zip (Size: 9.51 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#62
Milan Vančura Wrote:The rest of Plants category is fixed in this archive, plus some bonus parts.
Enjoy.
Thanks.

I see you've been editing them externally given the spacing in some of the matrices etc. You also seem to have used the comma for decimal separation which isn't that bad as LDCad doesn't care if . or , is used it will thread both as the decimal separation (as a result thousands sep is not supported though). I'll correct them though to keep things uniform.

Milan Vančura Wrote:P.S.: For Sea Grass, even the trick with 'Ins' key was not fast and precise enough. I wanted an automatic solution. But that meant I had needed to remind pieces of my linear algebra knowledge, after more than 20 years. I must say I still feel loud mess in my brain as many neuron paths, freshly woken up, are upset and crying, surprised why they cannot continue to sleep Smile
LDraw has a way in making those old math skills useful again Smile There might be a number of part authoring tools to help with these kinds of things though.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#63
Quote:You also seem to have used the comma for decimal separation which isn't that bad as LDCad doesn't care if . or , is used it will thread both as the decimal separation (as a result thousands sep is not supported though).
I always set up my windows to use '.' instead of ',' as decimal. I have yet to see a drawback of doing this and constantly get the benefit (such as beeing able to cut and paste LDraw source value to/from calculator)!
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#64
Roland Melkert Wrote:I see you've been editing them externally given the spacing in some of the matrices etc. You also seem to have used the comma for decimal separation
Mea culpa. That's, again, about Sea Grass part - I made some calculations in LibreOffice Calc and forgot to set the export LANG to US, sorry.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#65
Roland Melkert Wrote:
Milan Vančura Wrote:The rest of Plants category is fixed in this archive, plus some bonus parts.
Enjoy.
Thanks.
I'm working on Animals category now.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#35
Roland Melkert Wrote:My preference for svn is probably the result of me using it as a single user for my daily work. And I might be a bit bias as I didn't like the tortoisegit installation which was massive compared to the svn one. And for some reason git wont store empty folders which is something I use quite often.

But I might try git anyway as this will be a secondary storage after all.

Setting up the public svn repo and be aware of all attacks and hacks from internet is... Say, something I want to use as a punishment when/if somebody does something really bad to me. That's probably the most diplomatic phrase I could find Smile

With git, nobody does not need any write access to your tree, no accounts at any server just to be able to cooperate with you - and you have even better and easier control what you accept. All you need is to publish a read-only access to your tree. We can send you our commits via e-mail or publish them here, in forum. As you wish, what's more comfortable for you. And we'll see which commits were accepted, automatically.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#18
Milan Vančura Wrote:I was curious what is the difference between last Alpha and this Beta and I must say I'm fascinated! Of course, because of the snap info editor. It was easier to add missing snap info to the part then to place it manually to minifig's hand. Great!
Beta 1 has 33 bugfixes over Alpha 4 and mainly adds part editing feature and has some part snapping meta tweaks. You'll find a full listing of changes in the docs\changeLog.txt file.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#19
How can I change the large font size in the main window center footer area?

In main.gui, startMenu_cap looks about the same font size but changing it does not affect the center footer area.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#20
It's currently not adjustable as it size is the result of the other text using two lines. It's also the only text not rendered using OpenGL but plain GUI (wxWidgets) components. I have been considering an on/off option for the whole status bar after I add hint balloons though.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#21
Great job on connectivity editing! It's a plasure to be able to define connectivity and test it at once in the same session.

I added connectivity to a few parts that missed it, zip file attached (is it the best way to share such information?).
One thing mildly bothers me: when you press insert to duplicate a snap meta, the new copy doesn't inherit it's parent parameters (this also annoys me for flex part control points)

Some notes on the parts I edited:
- arms of the 2717 Technic seat are not wide enough, that's why the connectivity cylinders poke inside.
- The Technic Chain Tread 38 connect easily together, but if I cap the bar part at both ends to limit sliding, I get no connectivity at all...?
- Speaking of sliding, what would you suggest to make these parts slide properly http://www.ldraw.org/cgi-bin/ptdetail.cg.../18942.dat http://www.ldraw.org/cgi-bin/ptdetail.cg.../18940.dat?


Attached Files
.zip   shadow.zip (Size: 1.77 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#22
Philippe Hurbain Wrote:Great job on connectivity editing! It's a plasure to be able to define connectivity and test it at once in the same session.
Thanks, but I must say it was mostly for my own convenience Smile

Philippe Hurbain Wrote:I added connectivity to a few parts that missed it, zip file attached (is it the best way to share such information?).
Loose parts are ok to mail / or post here, and I'll add them to the default shadow (after some optional tweaks etc) if they are new to it. But if you are very keen on donoting info it might be a good idea to work on a specific category bin group or range of themed parts etc. That way I will avoid them while processing pars myself Smile

Philippe Hurbain Wrote:One thing mildly bothers me: when you press insert to duplicate a snap meta, the new copy doesn't inherit it's parent parameters (this also annoys me for flex part control points)
The insert key always adds the current 'work' part in its neutral state, unless there is a multiselection active in which case it will duplicate that. To always use duplicate even on single selections you can use ctrl+d .

Philippe Hurbain Wrote:The Technic Chain Tread 38 connect easily together, but if I cap the bar part at both ends to limit sliding, I get no connectivity at all...?
It might be grid stepping related or a bug, I'll look into it.

Philippe Hurbain Wrote:Speaking of sliding, what would you suggest to make these parts slide properly http://www.ldraw.org/cgi-bin/ptdetail.cg.../18942.dat http://www.ldraw.org/cgi-bin/ptdetail.cg.../18940.dat?
I would use square cylinder metas (or round ones, as it doesn't really matter in this case) using a group name to limit matches to these parts only.

Thanks for the part info.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#23
Roland Melkert Wrote:
Philippe Hurbain Wrote:I added connectivity to a few parts that missed it, zip file attached (is it the best way to share such information?).
Loose parts are ok to mail / or post here, and I'll add them to the default shadow (after some optional tweaks etc) if they are new to it. But if you are very keen on donoting info it might be a good idea to work on a specific category bin group or range of themed parts etc. That way I will avoid them while processing pars myself Smile

What about creating a repository on GitHub for all the shadow parts? That might be the easiest way to tack all the changes.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#24
Jason McReynolds Wrote:What about creating a repository on GitHub for all the shadow parts? That might be the easiest way to tack all the changes.
I have been looking into setting up svn.melkert.net (as I still prefer svn over git) for another reason so I might go that route.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#25
Roland Melkert Wrote:I have been looking into setting up svn.melkert.net (as I still prefer svn over git) for another reason so I might go that route.
That's great, a centralized, managed repository could come in real handy. svn, git, whatever, doesn't matter to me. Smile
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#29
Jason McReynolds Wrote:
Roland Melkert Wrote:I have been looking into setting up svn.melkert.net (as I still prefer svn over git) for another reason so I might go that route.
That's great, a centralized, managed repository could come in real handy. svn, git, whatever, doesn't matter to me. Smile

Milan Vančura Wrote:About the repository: good idea! I just, if I can, recommend git even you are familiar to svn so far - with git, you do not need to handle user rights (because we'll not need the write access), merging of branches is no longer a headache and, most important for you: you can see every commit as an e-mail (or "submit request") before you apply it to your tree. What saves a lot of time of the tree maintainer.
Of course, I'll respect any repository format you setup, I just wanted to share some years of experience to help you...

I think I might reverse my impartiality a little after Milan's comment and side more with git. I think I was more excited about a central repository than anything. Thought I'd add a little more to Milan's comment about git. Not trying to gang up on you Roland! Smile

I remember when I first started looking at version control software I used svn (was doing Android development). Then I talked to my brother, who had been doing web development for a decade, and he recommended git (he had used svn before). One of the big selling points for me with git was that it didn't litter all the directories with additional files. So, I tried it out, liked it, switched to git and haven't looked back. Haven't really had any gripes about it, but I'm no power user either. Merging is pretty straightforward too. My brother also mentioned Git-Flow (more here), which seemed pretty cool. However, my experience with git has been mostly for personal use. Just sharing my experience too. Smile
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#32
> About the repository: good idea! I just, if I can, recommend git even you are familiar to svn so far

I just wanted to fully agree here. svn is nearly dead now, and git is a really good choice.
I can warmly recommend the graphical user frontend SmartGit
for it if you don't want to use the command line.
It is free for non-commercial users and far better than gitk.
(And, no, I don't get money from them, just use that for years now in my job.)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#27
Quote:But if you are very keen on donoting info it might be a good idea to work on a specific category bin group or range of themed parts etc. That way I will avoid them while processing pars myself Smile
Difficult to tell what I'm going to do next (probably the Technic engine block and related parts), I feel motivated when I need something Wink
But I did a just series that I missed, the Technic buckets - zip attached.

Quote:To always use duplicate even on single selections you can use ctrl+d .
Thanks, I'll remember this one...

Quote:It might be grid stepping related or a bug, I'll look into it.
No, it was just sheer stupidity, I used a female cylinder insted of clips. Once the male cylinder was capped there was no way to get in Wink Corrected in the zip.

I also considered doing the small tread link, but then I realized that stud3 was missing connectivity (the plates that can connect to tread link through stud3). Is there a good reason not to define stud3 shadow?

Going a bit deeper on stud connexions, I see this message in your stud2 shadow:
Code:
0 //Do note parts using this still need to (optionally) add the hole part of the stud.
0 // This is not done here because in most parts it will extend beyond the stud.
This should actually not happen with stud2, but only with stud2a (if the hole is longer, then the 4-4edge at stud2 base is not needed, so part author should use stud2a).


Attached Files
.zip   shadow.zip (Size: 2 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#28
Quote:(probably the Technic engine block and related parts)
Done now, attached!


Attached Files
.zip   engine.zip (Size: 1.34 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#30
Philippe Hurbain Wrote:But I did a just series that I missed, the Technic buckets - zip attached.
Philippe Hurbain Wrote:
Quote:(probably the Technic engine block and related parts)
Done now, attached!
Thanks do you mind if I change the License to the non commercial one if I use these files for the default shadow. The auhor line will be preserved of course.

Philippe Hurbain Wrote:I also considered doing the small tread link, but then I realized that stud3 was missing connectivity (the plates that can connect to tread link through stud3). Is there a good reason not to define stud3 shadow?
None that I can think of, I probably thought it isn't needed and might cause unwanted snapping (like with stud4.dat) using the current one on one matching implementation. I'll check to see if it impacts many non plate parts and add it.

Philippe Hurbain Wrote:This should actually not happen with stud2, but only with stud2a (if the hole is longer, then the 4-4edge at stud2 base is not needed, so part author should use stud2a).
If so the stud2 can define the R 4 4 hole, and I'll move this message to stud2a and also check snap_incl usage. Thanks for the insight Philo.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#33
Quote:Thanks do you mind if I change the License to the non commercial one if I use these files for the default shadow. The auhor line will be preserved of course.
No problem!
Quote:I'll check to see if it impacts many non plate parts and add it.
stud3 is used mainly in 1xN plates, tiles and bricks (the latter often Y-scaled).
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#39
Roland Melkert Wrote:Hope you like the new major version, any feedback / questions / suggestions are welcome.
I'm starting new "subthread" because this is not about snap data/editor Smile

1.
I try to learn Trackball view rotation mode and I must say it's powerful and saves time when one can use it. However, it needs a free space (background visible) at the direction I want to turn to/from. This is not always possible, esp. if I need to zoom in for some detail editing. How do you handle that? Or can you reserve some modifier (like Alt) for this, instead of needing a background visible?

2.
LDCad crashed sometimes for me but very rarely and at random moments. What's the best way to provide you a useful information? Is a core file good for anything for you, for example? Or any debug mode I should turn on?

3.
"Save file" operation is still silent, even in cases the save operation was not successful (trying to 'save' into the zip fie etc.). Can you add a notice to the status bar?
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#40
1. Using the right mouse button instead of left one works even if you are not over background.
2. There is a log file (+ 2 older ones) in %appdata%\ldcad\logs
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#41
Philippe Hurbain Wrote:1. Using the right mouse button instead of left one works even if you are not over background.
I try to do all my view rotation with the right mouse button, because Roland has hinted at a future version implementing rectangle-select of parts, which makes most sense to use left mouse button.

Owen.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#43
Thanks, Philippe, for the tip about RMB. That's exactly what I was looking for.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#46
Milan Vančura Wrote:I try to learn Trackball view rotation mode and I must say it's powerful and saves time when one can use it. However, it needs a free space (background visible) at the direction I want to turn to/from. This is not always possible, esp. if I need to zoom in for some detail editing. How do you handle that? Or can you reserve some modifier (like Alt) for this, instead of needing a background visible?
Like Philo and Owen wrote, the right mouse can be used for that, even during part dragging etc. And owen is right I might drop the left mouse behavior at some point in favor for multi selection.

Milan Vančura Wrote:LDCad crashed sometimes for me but very rarely and at random moments. What's the best way to provide you a useful information? Is a core file good for anything for you, for example? Or any debug mode I should turn on?
Was this during closing or when you clicked on a source window line as those are currently known issues. A core file is probably not usefull as I compile the releases with all possible stripping and GCC optimize level 2, resulting in virtually no debug info left. As for reporting the most important thing for me is a replication scheme, as it will be very difficult to find a bug other wise. But any pointers are welcome.

Milan Vančura Wrote:"Save file" operation is still silent, even in cases the save operation was not successful (trying to 'save' into the zip fie etc.). Can you add a notice to the status bar?
I did this on purpose thinking you have been warned when starting editing the part, it will display a normal fail message if the writable part can't be saved. But I suppose I can add a 'nag' message so you at least retain the option to disable it again.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#47
Roland Melkert Wrote:
Milan Vančura Wrote:LDCad crashed sometimes for me but very rarely and at random moments.
...
...As for reporting the most important thing for me is a replication scheme, as it will be very difficult to find a bug other wise. But any pointers are welcome.
I have left the basic message only to emphasize the problem: so far I was not able to reproduce any such crash. Only I know is that it is neither the case of those well-known you mentioned in the last comment. For example, LDCad crashed once when I edited the pneumatic hose path and put both endpoints at the same point in the space. Looks as a good example but it is not: I have not been able to reproduce that since that time. And other crashes are even harder to describe.
That's why I asked how to help you with that. Is there any cmdline option or config option to turn logging to be verbose enough it helps you? Or do you want to build a non-stripped binary for me? I'm ready to test it if you tell me what&how to turn the testing/debugging mode on.

Roland Melkert Wrote:
Milan Vančura Wrote:"Save file" operation is still silent, even in cases the save operation was not successful (trying to 'save' into the zip fie etc.). Can you add a notice to the status bar?
I did this on purpose thinking you have been warned when starting editing the part, it will display a normal fail message if the writable part can't be saved. But I suppose I can add a 'nag' message so you at least retain the option to disable it again.
I'm sorry I'm not sure I parsed your answer correctly: I know about the warning popup window appearing when one starts to edit a part of a zip file. But I'm talking about a generic problem handling/reporting when the model is about to be saved. That's the problem. Another example, without any zip archive, to be more clear:

1. open/create some model, let's call it modeltest.mpd and save its first version containing one brick at 0,0,0 only
2. in your OS shell or file manager, make the file modeltest.mpd read-only (i.e. simulate a problem with file writing later)k
3. go back to LDCad and add another brick to the model
4. press ctrl-S - nothing visible happens (so the user expects the model is saved but that's not true)
5. press ctrl-W - a popup about non-saved modifications appears. Surprising for the user, he just "saved" the model - but "no problem" - he presses the "Yes" button and believes now the is saved for sure. No error message appears and the model window is closed!
7. load the model back - the first version without the second brick is what you can see, there is no way to see the second version, the one you believed (twice!) it is saved.

Same problem is with the file inside zip archive, only the problem description was more confusing. I hope it is clear now.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#48
Milan Vančura Wrote:I have left the basic message only to emphasize the problem: so far I was not able to reproduce any such crash. Only I know is that it is neither the case of those well-known you mentioned in the last comment. For example, LDCad crashed once when I edited the pneumatic hose path and put both endpoints at the same point in the space. Looks as a good example but it is not: I have not been able to reproduce that since that time. And other crashes are even harder to describe.
That's why I asked how to help you with that. Is there any cmdline option or config option to turn logging to be verbose enough it helps you? Or do you want to build a non-stripped binary for me? I'm ready to test it if you tell me what&how to turn the testing/debugging mode on.
I strip the exe to keep the filesize down, but using the full debug version is also kinda useless for these kinds of 'random' errors as they often are related to speed or heap corruption. Both of which seem to occur less or none at all when running inside a debug session. Logging is currently forced to the max level (debug) as a result of some extra messages to help find the close down bug.

Milan Vančura Wrote:1. open/create some model, let's call it modeltest.mpd and save its first version containing one brick at 0,0,0 only
2. in your OS shell or file manager, make the file modeltest.mpd read-only (i.e. simulate a problem with file writing later)k
3. go back to LDCad and add another brick to the model
4. press ctrl-S - nothing visible happens (so the user expects the model is saved but that's not true)
5. press ctrl-W - a popup about non-saved modifications appears. Surprising for the user, he just "saved" the model - but "no problem" - he presses the "Yes" button and believes now the is saved for sure. No error message appears and the model window is closed!
7. load the model back - the first version without the second brick is what you can see, there is no way to see the second version, the one you believed (twice!) it is saved.
This is not supposed to go that way indeed, I'll fix / improve it for the next version.

Milan Vančura Wrote:Same problem is with the file inside zip archive, only the problem description was more confusing. I hope it is clear now.
This was the one I was talking about, it is mentioned in the log though Smile I'll add a nag message for it.
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#49
Attached is a new shadow library file (rename it to .csl), it includes most changed/additions made by people other than me.

Thanks to all.

I do have some general notes on the donated files though.
  • 6126: I'm not sure about the hole in the 'flame', shoudn't it be a clip and if so doesn't it need one on the other side too? I also moved this info to the subfile.
  • All the traffic signs can be done by only adding the clip in the used primitive, so I've added that instead.
  • I redid both flower parts as the perfectionist in me couldn't help be bothered by the tiny offsets. There are some tricks you can use in the editor to obtain orientations from primitive usage (4-4cyli.dat in this case), maybe I'll should make a tutorial for this.
  • I noticed some of you used multiple meta's to describe the same shape (e.g. a bar with an axle section)., please use multiple sections in the same SNAP_CYL for this. I think I corrected them all but I might have missed some.
  • Alias, color, moved to, etc parts should never have a shadow file, instead edit the real .dat it references. (Warning: a direct shadow for such an alias can even crash the application when rendered in the bin, as it is a situation I did not account for. Will fix it though).
  • 2850a 2850b seem to be missing even with the 1501 update in place.
  • Anti stud in between e.g. the 2x4 plain antistuds should currently not be included (i commented them out in 2717)

Don't feel bad/discouraged about the above notes, all info was still quite usable and is very much appreciated.

fun fact: You can use the 1501 library update zip without merging it with complete.zip by just adding it in front of the search paths using the same shadow as the off lib.


Attached Files
.zip   offLibShadow.zip (Size: 641.27 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#51
Roland Melkert Wrote:6126: I'm not sure about the hole in the 'flame', shoudn't it be a clip and if so doesn't it need one on the other side too? I also moved this info to the subfile.
Ah, I missed there is a subfile, sorry for that. I need better glasses Smile
The hole should be a hole, not a clip. I tried it with the real part and it's near to impossible to use that as a clip - you can break the part this way. And about the other side (of the flame shape, you mean, right?): the shape is too open there so it cannot handle the pin. The only place working as "a snap point" is the one I marked.

BTW: While working on this I've found that holes in caps and hair parts fit to flower stem and vice versa: hair/helmet decoration pins fit to the hole in the middle of flower, and sausage ends fit there as well. Interesting. Maybe I use that fact in my next models Smile

Roland Melkert Wrote:I redid both flower parts as the perfectionist in me couldn't help be bothered by the tiny offsets. There are some tricks you can use in the editor to obtain orientations from primitive usage (4-4cyli.dat in this case), maybe I'll should make a tutorial for this.

Thanks for your empathy Smile You can imagine what I was crying for while working on stem parts... At least some words of hint, if you do not have time to make a video, would be helpful. LDCad always tells me "The selection must have editable positional information for this kind of action." when I try to select 4-4cyli.dat line in the source window and then press 'o' key in the edit window.

And can you also add a possibility to create a grid with step lesser than 1?
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#52
Quote:Ah, I missed there is a subfile, sorry for that. I need better glasses Smile
Mikeheide's LDStructure can be a great help to navigate the tree of part dependancies.
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#55
Milan Vančura Wrote:Ah, I missed there is a subfile, sorry for that. I need better glasses Smile
The hole should be a hole, not a clip. I tried it with the real part and it's near to impossible to use that as a clip - you can break the part this way. And about the other side (of the flame shape, you mean, right?): the shape is too open there so it cannot handle the pin. The only place working as "a snap point" is the one I marked.
I'll leave it the way it is then. You can use the new 'all dependencies' overview group to see all subparts/primitives used by a part currently being edited.

Milan Vančura Wrote:BTW: While working on this I've found that holes in caps and hair parts fit to flower stem and vice versa: hair/helmet decoration pins fit to the hole in the middle of flower, and sausage ends fit there as well. Interesting. Maybe I use that fact in my next models Smile
Yes all it needs to snap is the same diameter, this is why I usually define all even weird ones you never know what might stick to it later on Smile

Milan Vančura Wrote:Thanks for your empathy Smile You can imagine what I was crying for while working on stem parts... At least some words of hint, if you do not have time to make a video, would be helpful. LDCad always tells me "The selection must have editable positional information for this kind of action." when I try to select 4-4cyli.dat line in the source window and then press 'o' key in the edit window.
Primitives etc are blocked for normal pin / seleciton editing during part editing because the main editing matrix handling code doesn't play nice with scaled and or mirrored references. As I was asuming the part edting was mainly for myself I opted for the easy way and blocked it all Smile But when you click a reference in the source window it will change the working orientation. This is done by optionally removing the scaling and mirroring (flips the X-axis if I remember correctly). So if you know which reference has the correct orientation click it in the source window and then click the cyl meta in the part bin and press ins. It will insert the new meta using the working orientation. The position can be obtained/applied through copy / paste using the property dialog. This is the main trick I used, but you are right using 'o' would make more sense, I add that to the next version.

Milan Vančura Wrote:And can you also add a possibility to create a grid with step lesser than 1?
Grid and rotation stepping are currently integers internally but it shouldn't be hard to change that, I'll look into it.
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#57
Quote:You can use the new 'all dependencies' overview group to see all subparts/primitives used by a part currently being edited.
Where is it located? couldn't find it...
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#58
It's in the overview group (where the mpd file content etc is located).
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#95
Milan Vančura Wrote:And can you also add a possibility to create a grid with step lesser than 1?
Sorry this is a bit late to the party, but I just had a bit of an idea how you can place elements with <1LDU precision. Kind-of.
If you add a helper part like the marker meta somewhere close to the element you're placing, you can select the two of them and rotate them one degree at a time, which will result in a translation of <1LDU.

Of course, the technique is not fool-proof: the element you're trying to move will be rotated as well, so you may have to rotate it back (after deselecting the helper part, of course), and the movement is in two dimensions instead of one - you may need to manually clean up the position in one axis manually.

Owen.
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#96
you can also use the move tool / rotate tool (shortcuts Ctrl+M / Ctrl+R) to enter any value, even non-integer
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#53
Roland Melkert Wrote:Don't feel bad/discouraged about the above notes, all info was still quite usable and is very much appreciated.

Not discouraged at all, this information is much appreciated!

Roland Melkert Wrote:
  • All the traffic signs can be done by only adding the clip in the used primitive, so I've added that instead.

And to think of the time I could have saved had I known that (not blaming anyone but myself, I've really only known about LDraw for a couple weeks)! ;-) I keep meaning to dig into the file formats a little more to better understand them, I had thought that this might be possible on other parts but the thought didn't cross my mind with these signs. I'll be diving into that a little more before I edit some more parts.

Philippe Hurbain Wrote:
Quote:Ah, I missed there is a subfile, sorry for that. I need better glasses Smile
Mikeheide's LDStructure can be a great help to navigate the tree of part dependancies.

Thanks Philippe! I'm still learning about the files and how they work/relate to each other. This looks like it will help a lot.

Roland Melkert Wrote:
  • I redid both flower parts as the perfectionist in me couldn't help be bothered by the tiny offsets. There are some tricks you can use in the editor to obtain orientations from primitive usage (4-4cyli.dat in this case), maybe I'll should make a tutorial for this.

I realize a tutorial might be a bit time consuming, but I think it would probably be well worth the time. Those that are editing parts would be able to benefit from it and the returns for you would be worth the effort. Keep up the great work!
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#56
Jason McReynolds Wrote:I realize a tutorial might be a bit time consuming, but I think it would probably be well worth the time. Those that are editing parts would be able to benefit from it and the returns for you would be worth the effort. Keep up the great work!
I'll try to do a youtube clip of adding snap info to a medium sized part this weekend. Any part preference?

In the mean time I described my main orientation trick in the post above.
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#59
Roland Melkert Wrote:I'll try to do a youtube clip of adding snap info to a medium sized part this weekend. Any part preference?

In the mean time I described my main orientation trick in the post above.

Thanks, Roland. The trick works and it makes possible to fix snap info of parts of nonregular shape not only easier but more precise. Yes: 'o' key working would be very nice improvement but I can live with this trick, meanwhile.

About the part for a video tutorial: round plate 1x1. Because this part snap info contains near to all tricks:
1. it shows an inherited snap info (stud.dat)
2. you can show simple antistud snap info creation
3. then you can mention SNAP_CLR and reasoning for that
4. and as the last point show the way to specify SNAP_CYL with more segments
Appendix: 3741a.dat with your trick Smile
Reply
Re: LDCad 1.5 Beta 1 (shadow update)
#60
Milan Vančura Wrote:
Roland Melkert Wrote:I'll try to do a youtube clip of adding snap info to a medium sized part this weekend. Any part preference?

In the mean time I described my main orientation trick in the post above.

Thanks, Roland. The trick works and it makes possible to fix snap info of parts of nonregular shape not only easier but more precise. Yes: 'o' key working would be very nice improvement but I can live with this trick, meanwhile.

About the part for a video tutorial: round plate 1x1. Because this part snap info contains near to all tricks:
1. it shows an inherited snap info (stud.dat)
2. you can show simple antistud snap info creation
3. then you can mention SNAP_CLR and reasoning for that
4. and as the last point show the way to specify SNAP_CYL with more segments
Appendix: 3741a.dat with your trick Smile

Great suggestion Milan! I wasn't really sure what a good part would be. The only thing that I might suggest is to add in something with grids. If there's a piece that can do what Milan suggests and grids as well I think that would be perfect (maybe 2x2 round?). Two videos might not be a bad idea either. Smile
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#66
Something that would be useful: in the stepping menu, add a "goto step where this part appears". Useful when you forgot to insert a part at some step: click on a nearby part (hopefully appearing at more or less the same step), use the new goto function and add the missing part.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#67
This reminds me I want to thank for a feature "locate the selection" in part bin. I have found it couple of days ago and I do not know how long it is there but it is very useful. For example if one needs a similar part and it's not clear in which (sub)category this part is.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#68
I discover this function too... I hoped it could locate a part in the sub bins, but it seems it is not able to do this? My usage scenario would be to search for a part (with search tool), then use the locate function (starting from functional sorting bin, or from category sorting bin) to find the part in one of the sub-bin. This way I could 1- find similar parts 2- learn where this kind of part is stored.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#69
The find selection in part bin option is not new, it has been a bit buggy though (should be ok now). It locates the selection in the last used / clicked part bin but I will test that to be sure.

It looks for a part like so:

1 Current view's group.
2 Current view's children (exclude ones searched before)
3 Change current view to one level up.
4 Goto 1

Go to selection step shouldn't be hard to add, I'll try to add it to Beta 1a. You could also use the source window for this though as it follows the selection by default.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#70
Quote: You could also use the source window for this though as it follows the selection by default.
Yes, but how do I know the step number to move the timeline there and add parts at this step?
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#71
You double click the step meta line to make it the current step.

But I just relized the thing you're asking for is already available in the step menu. It's the 'selected' item.

I don't know my own program anymore Smile
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#72
So many possibilities I have yet to discover! Thanks Wink
Reply
Re: LDCad 1.5 Beta 1 (shadow update 2)
#73
Attached is a new shadow library file (rename it to .csl), it includes files donated by Philo and Milan.

I had to make less corrections for this one, I'm impressed Smile

Some mistakes I noticed:

Wrong caps.
Cylinders not covering the whole hole / pin.
SNAP_CYL instead of SNAP_CLP usage.
Not using the grid property when it could.

I did not include the files for unofficial parts as I'm not sure if they should be included or not, I kept them separate so I might add them later of start a second csl for it.

Thanks to all.


Attached Files
.zip   offLibShadow.zip (Size: 654.07 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (shadow update 2)
#74
Thanks, Roland.
I checked all your fixes of my parts and I understand them all but one: Plant Sea Grass. Can you explain why did you set caps to "two" or "B" there, if the intention (as I understand it) is to create one big sliding stick?
Reply
Re: LDCad 1.5 Beta 1 (shadow update 2)
#76
Milan Vančura Wrote:Can you explain why did you set caps to "two" or "B" there, if the intention (as I understand it) is to create one big sliding stick?
You are right the bottom one should use the 'b' cap. I forgot to rotate it Smile

This part also uncovered a (minor) snapping bug. A length 8 clip shouldn't snap to <8 length cyl sections while using the 'two' cap.
Reply
Re: LDCad 1.5 Beta 1 (shadow update 2)
#78
Roland Melkert Wrote:
Milan Vančura Wrote:Can you explain why did you set caps to "two" or "B" there, if the intention (as I understand it) is to create one big sliding stick?
You are right the bottom one should use the 'b' cap. I forgot to rotate it Smile
Hehe. If I was right about anything there it's just a matter of luck. I more asked for an explanation, to understand caps better. Because, as I understand them, if I want to put several snap_cyl metas in a (curved) row, the correct caps value is None with Slide=True. To simulate one long rod without any interruption. And now, I expect I'm not correct with this understanding as you changed all caps parameters to "both" value. ??

Originally, I wanted to check my new files (Animals) for caps, with this new understanding (your answer) but, in the end, I was too impatient and sent the set of shadow files, already Smile I may confirm I tested those caps values in the editor and they work as intended. Including cases where they come from subparts. So I hope they are OK - please let me know if I still understand anything incorrectly from your POV.
Reply
Re: LDCad 1.5 Beta 1 (shadow update 2)
#79
Milan Vančura Wrote:I more asked for an explanation, to understand caps better.
The caps parameter is about limiting the range of the cylinder. This is done by indicating what side(s) of the cylinder is/are block(ed). Meaning something sliding/snapping on it should never have overlap into outer space on that side.

The 'a' value means the origin side is blocked. (e.g. stud underside)
The 'b' value mean the outer end is blocked. (e.g. anti stud ceiling)
The 'two' value means both ends are blocked (e.g. the curve blocks both sides in your example).
The 'one' value auto selects 'a' or 'b' depended on the gender. For male it's the origin (A) and for female it's the end (B).

Hope this clears it up some more.

Milan Vančura Wrote:I may confirm I tested those caps values in the editor and they work as intended.
If clips snap to 'two' capped of a lesser length this is the result of the bug I mentioned above. If 'none' is selected you will be able to slide from the outer rims but the clip will be intersecting the mesh of the plant curve.

In the end it is just a helper value as you can still end up moving stuff inside parts as they might use a different snap point or are using very complicated shapes (e.g. a pin inside a larger hole).
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#75
commit b199c357cdb409cf24235684815699e05819ad59
Author: Milan Vancura <mvancura@suse.cz>
Date: Wed Oct 21 17:17:34 2015 +0200

mod04.zip - Animals category

http://forums.ldraw.org/showthread.php?t...1#pid17781

Everything but dinosaur parts (I do not have any)

Open issues:

43744 - rod with hole on top of the head
30478 - antistuds does not fit at the bottom - anybody who knows the
real part? Does it fit at 2x2 studs?


Attached Files
.zip   mod04.zip (Size: 28.33 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#81
As I finished Animals category, I continue with "Containers" one.

More snap info: containers, first part.
I've found barrel and crate containers need their own snap and I had to define all matching "female" parts/positions. That's why these two containers "generated" so big commit:

commit 611a22911ef5aec2092cb9157afa5a10231eb7b0
Author: Milan Vancura <mvancura@suse.cz>
Date: Fri Oct 23 00:04:17 2015 +0200

Barrel and Crate containers plus matching parts

Two new snap objects introduced: R 16 and S 16.
They are used in situations where there are no studs but the part
periphery matches 2x2 studs. Barrel and Crate container tops are good
examples. Important point: not all 2x2 antistuds match S 16 or R 16.
Usually, tubes on the part bottom collide with barrel periphery shape.
So I marked all mathing ("female") parts/places with female R 16 and/or
S 16.

Sent as: mod05.zip
http://forums.ldraw.org/showthread.php?t...0#pid17800


Attached Files
.zip   mod05.zip (Size: 17 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#87
Milan Vančura Wrote:Barrel and Crate containers plus matching parts

Two new snap objects introduced: R 16 and S 16.
They are used in situations where there are no studs but the part
periphery matches 2x2 studs. Barrel and Crate container tops are good
examples. Important point: not all 2x2 antistuds match S 16 or R 16.
Usually, tubes on the part bottom collide with barrel periphery shape.
So I marked all mathing ("female") parts/places with female R 16 and/or
S 16.
Thanks

I did not realize those should fit 2x2 plate undersides. I willl add these and mod4 to the next beta's shadow.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#88
Thanks for the two zips

15279.dat seems to be a git diff file or something, i used the lines I thought were best.
59228s02 seems to contain garbage for the id property. Do you know when this happened?

You seemed to mistook the ID property for the group one in many files, I corrected them though.

The ID property is meant to uniquely id a (collection) of snap points so you can clear them in a higher part in order to redo shapes they were part of.
The group property is used to limit matches.

I also make quite some changes to the horse, cow and dragon parts it should snap more natural this way.

But overall nice work, thanks your files will be part of the new beta I'm hoping to release this weekend.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#89
Thanks for checking my files, Roland.

You are right about 15279.dat - this is my mistake, it shows how your version differs to the previous one of mine. So no change in this file since your last update.

The garbage in 59228s02.dat surprises me as well because I did not edit this file in any external editor. LDCad is what saved this. But why? And was it my mistake? How can I even put so much of garbage to the edit field? I do not know. Please: for the file itself, ignore that garbage. Only it may be interesting about is to check LDCad if it might be caused by any bug. (What I suggest to spent time on only if/after it happens again...)

Also thank you for your explanation about ID vs. Group fields. I'm not 100% sure I understand that but that's the advantage of a written form: I may read it again and again until I start to understand. Meanwhile, I take it as a simple rule: Milan, do not use ID field! Smile
Reply
Re: LDCad 1.5 Beta 1 (Snap edit tutorial)
#77
I've made a quick simple demo/tutorial clip.

https://youtu.be/4xJvdWNgPyw

Hope it clears some of the secrets up Smile
Reply
Re: LDCad 1.5 Beta 1 crashes
#80
Hello Roland.

I hope I just found at least some hint about occasional crashes, finally: LDCad crashed two times today and it was, both cases, when I clicked on the "up" arrow in the part bin. Last log contains at least one line about that so I attach the whole log file.
Additional detail: I had "show snap points" turned on in both cases.

I hope this report helps at least somehow.

EDIT: new version of the archive, without the relative path of the file inside.


Attached Files
.zip   log.zip (Size: 265.68 KB / Downloads: 0)
Reply
Re: LDCad 1.5 Beta 1 crashes
#82
Your file is not empty, but I can't find anything inside... might be on my side, but I think your zip file is somehow corrupted.
Reply
Re: LDCad 1.5 Beta 1 crashes
#83
The file is okay, but it's been zipped with the file inside using a ..\..\ relative path, so some extractors might throw a fit.
Reply
Re: LDCad 1.5 Beta 1 crashes
#85
Ah indeed. 7zip goes through it but I lost reference (and patience) after clicking 3 times on .. ! Window XP file manager sees nothing. Anyway Milan updated file Wink
Reply
Re: LDCad 1.5 Beta 1 crashes
#84
Thanks for a note. I re-zipped the archive so it does not make any problems for you, regardless of the unzip program.
Reply
Re: LDCad 1.5 Beta 1 crashes
#86
Milan Vančura Wrote:LDCad crashed two times today and it was, both cases, when I clicked on the "up" arrow in the part bin. Last log contains at least one line about that so I attach the whole log file.
Additional detail: I had "show snap points" turned on in both cases.
Thanks Milan, this is probably the same bug I fixed a couple of days ago.

It tries to render a part bin cell (the mascot one) using a recently reloaded LDraw file. Problem being it tries to (re)use the old data which has been freed due to the reloading, it even says in the log 'should never happen' Smile.

This might also be the reason for (some) of the closing bugs, A new beta is due this weekend, hope you didn't loose work.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#90
Hi Roland.

Is there a way to selectively unhide parts? As far as I can tell, your options are limited to the last part hidden, or all hidden parts.

Owen.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#91
Owen Dive Wrote:Is there a way to selectively unhide parts? As far as I can tell, your options are limited to the last part hidden, or all hidden parts.
No you can indeed only unhide in reverse (like undo) or show all again. I have plans for more grouping options though and as the hidden parts are internally also groups. This is something for version 1.6 or maybe even 1.7 though.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#92
Ah, that is a shame. At least I wasn't missing something.

I did find a strange behaviour this evening. I had many parts hidden, and when I tried to insert a new copy of a submodel, one of the parts of that submodel (but not the whole submodel) got hidden. As I drag it from the part bin, it's fine, but as soon as it was placed in the workspace the part disappeared (and its line in the source window is greyed out). I was not using nested mode. Can you think of any reason why that would happen?
Unfortunately I haven't been able to reproduce this behaviour.

Owen.
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#93
Owen Dive Wrote:I did find a strange behaviour this evening. I had many parts hidden, and when I tried to insert a new copy of a submodel, one of the parts of that submodel (but not the whole submodel) got hidden.
Might just be a rendering glitch resulting of a wrong tag number, does e.g. a next part insertion make it visible again?
Reply
Re: LDCad 1.5 Beta 1 (win+linux)
#94
Roland Melkert Wrote:Might just be a rendering glitch resulting of a wrong tag number, does e.g. a next part insertion make it visible again?
To be honest I didn't try. After unhiding everything, it worked as normal, even after re-hiding parts (though admittedly not exactly the same parts), and as I said, I couldn't get it to do it again. I probably shouldn't even have mentioned it.
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 2 Guest(s)