2016-12-05, 7:18
(2016-12-05, 0:32)Trevor Sandy Wrote: [ -> ]For LPub3D 2.1 and beyond, there are already quite a few interesting new features coming from the Porsche GTS instructions book, I'll add this one also.
OH nice
(2016-12-05, 0:32)Trevor Sandy Wrote: [ -> ]For LPub3D 2.1 and beyond, there are already quite a few interesting new features coming from the Porsche GTS instructions book, I'll add this one also.
(2016-12-09, 9:26)Merlijn Wissink Wrote: [ -> ]...callout in a callout doesn't look very well :
I don't know what's happening here, but it sure isn't what it's supposed to do. Any ideas?
// This is what's supposed to happen when a callout [begin] meta is encountered.
case CalloutBeginRc:
if (callout) {
parseError("Nested CALLOUT not allowed within the same file",current);
} else {
callout = new Callout(curMeta,view);
callout->setTopOfCallout(current);
}
break;
(2016-12-09, 10:01)Trevor Sandy Wrote: [ -> ](2016-12-09, 9:26)Merlijn Wissink Wrote: [ -> ]...callout in a callout doesn't look very well :
I don't know what's happening here, but it sure isn't what it's supposed to do. Any ideas?
I didn't know nested callouts were possible in LPub3D or LPub for that matter
I certainly haven't released any functionality of the sort; furthermore, the legacy LPub code suggest this behaviour is explicitly forbidden.
Code:// This is what's supposed to happen when a callout [begin] meta is encountered.
case CalloutBeginRc:
if (callout) {
parseError("Nested CALLOUT not allowed within the same file",current);
} else {
callout = new Callout(curMeta,view);
callout->setTopOfCallout(current);
}
break;
Did the behaviour you expected exist on any earlier version of the software?
It would be interesting to see an example of the LPub meta pattern you used in the model file to produce nested callouts.
Cheers,
(2016-12-09, 12:24)Milan Vančura Wrote: [ -> ]Did you have time for a research why LPub3D stopped being compilable on Linux, too?
(2016-12-09, 12:24)Milan Vančura Wrote: [ -> ]Can I still help you with that in any way?
(2016-12-09, 19:49)Trevor Sandy Wrote: [ -> ]If you are ok to run the currently available distributions of LPub3D - WINE is your friend
(2016-12-09, 19:49)Trevor Sandy Wrote: [ -> ]Sure, the LPub3D source should be cross-platform compile compatible because I develop exclusively with the QtCreator/MinGW tool chain.Thanks, Trevor!
If you care to share any content on compiling on and packaging for Linux, I'll be pleased to incorporate and validate the build and release.
(2016-12-13, 7:41)Milan Vančura Wrote: [ -> ]...tell me if you need anything more about Linux, I hope LPub3D stays multiplatform since now and I'll be able to prepare Linux binary package every time you release new version.
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]If had the read access to your development git branch I could prepare commits based on the current code - that saves time of both me (some fixes already done) and you (every merge easier for you). I can continue sending commits via forum or e-mail so I do not need any write access to you tree. What do you think about that?
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]Also, it would be great if you can have a virtual machine with Linux so you can test your builds there. Installation of Debian or Ubuntu is easy, same about openSuse or Fedora.
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]I'd be very glad if you can tell me more: what makes sense to spend time with, what you have already solved in your development branch, what looks like a Linux-specific problem etc.
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]First run - the creation of the first user configuration:
* LPub3D creates new directory tree on its own ($HOME/.local/share/LPub3D Software/LPub3D/) but it forgets to create some files there and complains to me instead: "extras/titleAnnotations.lst", "extras/fadeStepColorParts.lst", "extras/pliSubstituteParts.lst".
* to make it more annoying, it cries later about missing titleAnnotations.lst file before rendering each and every step
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]* Preferences: after typing the ldglite path manually the roller "preferred renderer" does not get any value and "Required settings are missing..." warning pops up after hitting "OK" button. The workaround is to click on "Browse", even I do not need to change the path. Then, everything works.
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]* LPub3D asks me for both complete.zip and ldraw directory - why??
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]* LPub3D tries to get some archive of unofficial parts - how can I point it to my "Unofficial" subdirectory of my ldraw tree instead? Same as what I use and/or used with LDCad, LPub4, SR3D Builder...
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]* ctrl-O does not work
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]* ctrl-S tries to "save the project" even when nothing is open
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]* I do not understand how to "synchronize" the angle of current step and the angle in that 3D window. A different angle is shown there and if I rotate with that 3D view and press "insert rotstep" button, I get completely different view in the rotstep than it is shown in the 3D sidebar.
(2016-12-14, 22:57)Milan Vančura Wrote: [ -> ]The program crashes with segmentation fault in several cases, I try to map them and solve what I can.
(2016-12-15, 12:05)Milan Vančura Wrote: [ -> ]I found a link to the git tree on sf.net but to that old one (2.0.6) only, I did not understand why.
git clone git://git.code.sf.net/p/lpub3d/code lpub3d-code
(2016-12-15, 12:05)Milan Vančura Wrote: [ -> ]Unfortunately, we did not have time to fix some dependencies issues of ldglite at RedHat systems (Fedora, CentOS). I might try to fix them if you need CentOS.
(2016-12-15, 12:05)Milan Vančura Wrote: [ -> ]What I still don't understand is your way of ldraw library management.
(2016-12-14, 23:06)Milan Vančura Wrote: [ -> ]A bug I cannot reproduce now but it happened twice: after first run and all those configuration questions, program set the LDraw path to $HOME/.local/share/LPub3D Software/LPub3D/ldraw directory which it created but left empty. Then it was a surprise why LPub3D looks working somehow but I see empty pages, only a box with numbers of each part amount was there, no pictures. After long debugging I found it was just a matter of this misconfiguration.
But, as I wrote above, I'm not able to reproduce this behavior now, I forgot that combination of my options which caused this.
(2016-12-15, 9:34)Trevor Sandy Wrote: [ -> ]You should have read access. Read permissions are enabled for anonymous users by default. If you care to set up and forward your sourceforge user id, I'll be pleased to add you to the repository with read/write access. Or, we can continue to exchange via mail/posts. You can see my email in the help/about dialogue.Just a quick update, I will have more time during the weekend: I can see both master and x11 branch and it's the same tree I made the clone before - I see you added big commits forwarding the code to 2.0.19 at once. That's good, I can work with more current code now. But it would be even better if you can give me the access to the real development branch where I can see separate commits with features and fixes - this would help me a lot to understand the code.
[STEP 1]
1 4 0 -101.461 390.329 -1 0 0 0 0.966 0.259 0 0.259 -0.966 submodel-94.ldr
0 BUFEXCHG C STORE
1 4 15 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
1 0 -50 -62.821 400.689 0 0 1 -0.966 0.259 0 -0.259 -0.966 0 HashL2.dat
0 ROTSTEP 20 165 0 ABS
[STEP 2]
0 BUFEXCHG C RETRIEVE
1 4 -70 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
0 BUFEXCHG D STORE
1 4 -15 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
1 0 50 -62.821 400.689 0 0 -1 0.966 0.259 0 0.259 -0.966 0 HashL2.dat
0 ROTSTEP 20 -165 0 ABS
[STEP 3]
0 BUFEXCHG D RETRIEVE
1 4 70 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
(2016-12-27, 10:05)Merlijn Wissink Wrote: [ -> ]I haven't used buffer-exchange in quite a while, but I need it again now. But, it looks like LPub3D doesn't handle it correctly (anymore). Or I'm just not using buffer-exchange correctly, that's also a possibility
This is an excerpt from my file (I added some extra step numbers for clarity, they are not in the actual file):
Code:[STEP 1]
1 4 0 -101.461 390.329 -1 0 0 0 0.966 0.259 0 0.259 -0.966 submodel-94.ldr
0 BUFEXCHG C STORE
1 4 15 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
1 0 -50 -62.821 400.689 0 0 1 -0.966 0.259 0 -0.259 -0.966 0 HashL2.dat
0 ROTSTEP 20 165 0 ABS
[STEP 2]
0 BUFEXCHG C RETRIEVE
1 4 -70 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
0 BUFEXCHG D STORE
1 4 -15 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
1 0 50 -62.821 400.689 0 0 -1 0.966 0.259 0 0.259 -0.966 0 HashL2.dat
0 ROTSTEP 20 -165 0 ABS
[STEP 3]
0 BUFEXCHG D RETRIEVE
1 4 70 -62.824 400.681 1 0 0 0 0.966 -0.259 0 0.259 0.966 32062.dat
So, let's go through this step by step when viewing this in LPub3D:I have added 2 buffer exchanges so far and both show this behavior.
- Step 1, everything seems fine. It shows the submodel, the buffered part and the arrow (which for whatever reason is not in the parts list, but that's good obviously )
- Step 2, here things get a bit wrong. LPub3D correctly removes the buffered 32062 and the arrow from the assembly view and it correctly shows the new buffered 32062 and arrow. BUT, it hows 2x 32062 in the parts list. That should be 1x.
- Step 3, the same as step 2. It correctly removes the buffered parts from the view, but it still lists 1x 32062 again in the parts list...
So, am I doing something wrong or is LPub3D doing something wrong?
(2016-12-27, 23:49)Trevor Sandy Wrote: [ -> ]Merlijn - take a look at this post on a good pattern for using the BUFEXCHG meta in LPub3D.
Let me know if after you adjust your BUFEXCHG procedure accordingly, the unexpected behaviour continue ?
The post presents a detail use case with supporting LPub3D and LPub assets comparing and explaining how the BUFEXCHG meta should be used. I believe an anomaly in the way LPub managed its cache files, and the difference in the way MLCAD treats the meta, have led to incorrect expectations about the way the meta can be used with LPub3D.
Cheers,
[other parts in the step]
0 !LPUB BUFFER A STORE BEGIN
[parts and arrows to store here]
0 !LPUB BUFFER A STORE END
[other parts in the step]
0 STEP
[other parts in the step]
0 !LPUB BUFFER A RETRIEVE BEGIN
[final position parts]
0 !LPUB BUFFER A RETRIEVE END
[other parts in the step]
(2016-12-28, 14:55)Trevor Sandy Wrote: [ -> ]Very well. Your write up looks interesting.
On the post I linked, I hadn't really looked at Johann's update so If his scenario is different from Artius' then I will certainly update LPub3D if it is determined to be in regression. On the other hand, I clearly demonstrated that Artius' expectation was actually not the way either LPub3D or even LPub actually behaved. This position is demonstrated in the post I shared.
So. I am open to evolving the BUFEXCHG behaviour (while keeping backward compatibility of course) to make it more efficient because some users seem to be confused by the current behaviour (I get lots of request on the good pattern to implement). Moreover, the feature is quite valuable to producing hi-fidelity instructions.
Im wrapping up my x11 ports (Linux and OSX) so I should be in a position to take a look at putting this on the stack after that. Do not hesitate if you have any additional ideas on how we could improve this feature.
Cheers,
Failed to open C:/Users/XXXX/Desktop/README.txt
No such file or directory
SetOutPath "$INSTDIR"
File "..\docs\README.txt"
(2017-01-09, 15:46)Willy Tschager Wrote: [ -> ]in your installer script. I therefore wonder why you would store a change log file on the Desktop and where I do change the search path?
SetOutPath "$INSTDIR"
File "..\docs\README.txt"
lpub3dPath = cwd.absolutePath();
QString readme = tr("%1/%2").arg(Preferences::lpub3dPath,"README.txt");
QString readmeFile = QString("%1/%2").arg(Preferences::lpub3dPath).arg("README.txt");
(2017-01-16, 19:06)Walt White Wrote: [ -> ]Using the POV-Ray rendering in version 2.0.19 is _very_ slow generating the image for a Panel 1 x 2 x 2 - Hollow Studs — BrickLink part 4864b in color 47 trans clear.
(2017-02-03, 14:14)Merlijn Wissink Wrote: [ -> ]Today I fired up LPub3D and it said there was a new version available (2.0.20 I believe).
...
But I can't find any (in fact, the sourceforge page doesn't even show 2.0.20).
(2017-02-09, 4:15)Trevor Sandy Wrote: [ -> ]Greetings,
LPub3D 2.0.20 is released.
This release introduces 4 new platform distributions for Mac OSX, Arch Linux, Debian/Ubuntu Linux, and SUSE/Fedora/Red Hat Linux.
You can download this release from sourceforge.net or check for updates in your existing installation.
Available binary downloads:
Mac OSX: DMG Package 64bit
(2017-02-12, 11:18)Jaco van der Molen Wrote: [ -> ]Perhaps something is wrong on my machine but do you have any idea what can be done?
(2017-02-13, 16:53)Jaco van der Molen Wrote: [ -> ]There were no files titleAnnotations.lst and pliSubstituteParts.lst in the LPub3D package, so I copied them from my Windows installation.
I also missed the freeformAnnotations.lst.
(2017-02-13, 16:53)Jaco van der Molen Wrote: [ -> ]Now for the settings: they are not kept.
Rendering a model works fine now. But every time I have to look for LDView...
~/Library/Preferences/
/Applications/LPub3D.app/Contents/Resources
(2017-02-13, 21:41)Jaco van der Molen Wrote: [ -> ]This is the LPub3D package content:
I cannot seem to find any reference to LPub3D preferences.
(2016-12-05, 0:32)Trevor Sandy Wrote: [ -> ](2016-12-03, 8:50)Merlijn Wissink Wrote: [ -> ]So, is it possible to implement something like that in LPub3D?
Indeed, it's possible and somewhat straightforward to do too. Instead of automatically resetting the step number at every new submodel (or callout), I can add a preference setting to optionally reset or not.
For LPub3D 2.1 and beyond, there are already quite a few interesting new features coming from the Porsche GTS instructions book, I'll add this one also.
Cheers,
(2017-02-16, 3:37)Trevor Sandy Wrote: [ -> ]The Mac OSX dmg package is fixed. All parameter files are present.
Cheers,