(2019-07-01, 22:20)Orion Pobursky Wrote: [ -> ]I disagree. If Micheal wants to release a new version of MLCad or open source his program I'll reconsider. Until then, I'm not really interested in further official support/promotion of MLCad.
It's a shame about MLCad. If it weren't for two issues I would use it 99% of the time.
Anybody else having issues with the new LDConfig.ldr in LDPartEditor, which dosen't open the color dialog when clicking on "More..."?
w.
(2019-07-27, 6:54)Willy Tschager Wrote: [ -> ]Anybody else having issues with the new LDConfig.ldr in LDPartEditor, which dosen't open the color dialog when clicking on "More..."?
Problem confirmed (ldpe
0.8.45 0.8.46). Removing the 10k colors solves the issue
(2019-07-27, 12:38)Philippe Hurbain Wrote: [ -> ]Problem confirmed (ldpe 0.8.45 0.8.46). Removing the 10k colors solves the issue
Whats the highest number you can define without a crash?
I was able to solve the problem. I am working on a release today.
The new AIOI is ready for upload. This means that the:
Colour Definitions -
https://www.ldraw.org/article/547.html
page has to be updated. I remember vagly that the talked about an automated process where the table reads in the content of the LDCOnfig.
@Philo, could you please generate a new Visual LDConfig picture?
w.
(2019-08-03, 16:30)Willy Tschager Wrote: [ -> ]@Philo, could you please generate a new Visual LDConfig picture?
Yes... But may take some time!
(2019-08-03, 16:30)Willy Tschager Wrote: [ -> ]The new AIOI is ready for upload. This means that the:
Colour Definitions - https://www.ldraw.org/article/547.html
page has to be updated. I remember vagly that the talked about an automated process where the table reads in the content of the LDCOnfig.
@Philo, could you please generate a new Visual LDConfig picture?
w.
The colour definitions pulls data from the server so it will auto update when the new ldconfig.ldr is added to the official parts directory on the server
I had a look at:
Ryan Howerter's color list
Swooshable color chart
as well as
Rebrickable
and what Owen did for us:
LDraw Wiki
trying to figure out if we could harmonize the colors in some way with other sites. A hopeless task.
Howerter's Red - B40000
Rebrickable Red - C91A09
Owen writes: "The LEGO numbers, names and LDD colours are taken directly from
LEGO Digital Designer, and are accurate as of LDD 4.3.8, Brick Version 1392. As Brickset can utilise LEGO's replacement parts system, if there is a Brickset entry available for a particular LDD colour it will be linked to via a
![[Image: Brickset_favicon.png]](https://wiki.ldraw.org/images/a/a2/Brickset_favicon.png)
logo."
So I'm inclined to go with that. Opinions?
w.
(2019-08-14, 5:44)Willy Tschager Wrote: [ -> ]So I'm inclined to go with that. Opinions?
w.
Go with what? I don't understand what you want to do.
(2019-08-14, 15:00)Magnus Forsberg Wrote: [ -> ]Go with what? I don't understand what you want to do.
Substitute all current HEX in the LDConfig with LDD colours.
w.
(2019-08-24, 22:55)Lasse Deleuran Wrote: [ -> ]A legitimate concern was raised in this Eurobricks thread: https://www.eurobricks.com/forum/index.p...nt-3141796
MLCad apparently throws errors due to ldconfig.ldr in the latest AIOI and it is not at all apparent to users what the root cause is.
This is already a known issue and we (as in LDraw.org SteerCo) have already contacted Michael about it. The cause is numbers above 512. If Michael declines to update MLCad, I’ve already made my opinion about this known in other threads.
(2019-08-24, 22:55)Lasse Deleuran Wrote: [ -> ]A legitimate concern was raised in this Eurobricks thread: https://www.eurobricks.com/forum/index.p...nt-3141796
MLCad apparently throws errors due to ldconfig.ldr in the latest AIOI and it is not at all apparent to users what the root cause is.
I don't understand your decision
to stay out of the discussion here. We cannot know our entire user base, so if through your contacts in Eurobricks you believed this was going to start a firestorm, your contribution here would have been most useful and may have changed the outcome.
(2019-08-25, 5:54)Chris Dee Wrote: [ -> ]I don't understand your decision to stay out of the discussion here. We cannot know our entire user base, so if through your contacts in Eurobricks you believed this was going to start a firestorm, your contribution here would have been most useful and may have changed the outcome.
I am not currently on my Windows machine. This is why I raised the question in this thread a while back instead of claiming anything about MLCad. Before the user report I thought the issue with MLCad was merely that these colors would show up as gray and would not be easy to use. This is what I gathered from the responses in this very thread, and given the feedback from Orion and others, I thought those arguments were valid and I stayed out of the discussion as I had no further input: My question was raised and it was answered.
It is first after I saw the post on Eurobricks that I became aware of the software breaking and refusing to start. Is this really the case? If so, then I recommend a warning to the users about this, just as suggested by the guy reporting the experience on EB.
I'm afraid to be at least partially guilty... Like Lasse said, what I tried made me think that only the rubber colors were not available, but that no other harm was done. I was wrong ?
I'm currently testing MLCad 3.51 which solves the problem.
w.
(2019-08-24, 22:55)Lasse Deleuran Wrote: [ -> ]A legitimate concern was raised in this Eurobricks thread: https://www.eurobricks.com/forum/index.p...nt-3141796
MLCad apparently throws errors due to ldconfig.ldr in the latest AIOI and it is not at all apparent to users what the root cause is.
A new
AIOI containing MLCad 3.51 which solves this problem has been published.
w.
Deleted, Willy posted over at EB