DATHeader 3.0.19.0


DATHeader 3.0.19.0
#1
There are some new features build in now and also (as always) bugfixes and changes.

New
1) Command line option /r changed to ui less version for scanning of files only and write the report to a file in "<userdocuments>\MPDCenter""
2) Command line option /c (correct) in conjunction with /r will correct the file and write it to "<userdocuments>\MPDCenter\corrected".
3) Command line option /l (library) works with both options on the library with report and correction (library will not be touched). (auf Recifier postprocessor achten-erl.)
3) If a conditional line and a line have the same values, the conditional line will be deleted.
Changes
1) Message for wrong comment lines changed.
2) Message for not corrected triangle because of colinear vertices changed.
3) If you "Save as" then the new name is written to the "Name:"-tag of the new file.
4) the application has now a new icon
5) There is no test for flat files scaled in the flat direction.
Bugfix
1) Correct colinear quad sometimes bring wrong lines.
2) Check on file name ending ...s01 or ..p01 could generate an error.
3) using of rectifier postprocessing gave wrong messages.
4) parsing of the author line improved.
5) If a subfile could not be found the boundingbox is set to all zero.
6) If the entire file will be flushed, also the picture will be flushed and the new header

You can download the tool as always from http://ldraw.heidemann.org/index.php?page=datheader
Reply
Re: DATHeader 3.0.19.0
#2
Hi Mike,

I was the original initiator behind the Check for scaled flat primitives. It started with a question from me.

Would it be possible to still have this as a feature in DH? Maybe turned on/off by a checkbox somewere?
The scaled primitive is now allowed, but IMO, it is still good practice to not have them scaled.
I want to have my files checked and corrected.
Reply
Re: DATHeader 3.0.19.0
#3
+1
Reply
Re: DATHeader 3.0.19.0
#4
+1 too. While I thought it was useless to make this mandatory, it's not a bad thing to detect and "correct it".
Reply
Re: DATHeader 3.0.19.0
#5
It seems to be very difficult to follow each wish.
If it will be shown in DATHeader again I fear that this will cause some people again to hold for this reason. This was never the attempt of DATHeader.
So I need now some idea how to avoid that.

Hmmm.. Maybe I just change the notice and add ".. NOT A HOLD VOTE!"

Just my idea. To bring the function back I just have to delete one line of code :-). But I want to have it right for the future now.

I am looking forward to your input.

cu
Mike
Reply
Re: DATHeader 3.0.19.0
#6
What I suggest (if it is possible), is that if you do a "correct all" then DH automatically unscale flat primitives. If you only do a validation check, then do nothing (no warning at all). Now, as you say... "Just my idea"!
Reply
Re: DATHeader 3.0.19.0
#7
Yes, and the correction can be stopped (initially it is checked) by unchecking a new checkbox in the properties.

This sounds good to me.

Any other idea, or agreement to this ideas ?

cu
Mike
Reply
Re: DATHeader 3.0.19.0
#8
I agree, it sound good to me too.
Reply
DATHeader 3.0.19.1
#9
New version 3.0.19.1 is out now with the changes for fixing the scaled flat files in flat direction.

You can download the tool as always from http://ldraw.heidemann.org/index.php?page=datheader

I hope there is still no bug Smile

cu
Mike
Reply
RE: DATHeader 3.0.19.1
#10
(2015-12-23, 10:14)Michael Heidemann Wrote: New version 3.0.19.1 is out now with the changes for fixing the scaled flat files in flat direction.

You can download the tool as always from http://ldraw.heidemann.org/index.php?page=datheader

I hope there is still no bug Smile

cu
Mike

I am suddenly getting the error:
Conversion of string 311/227 to type Integer is invalid. Microsoft.Visualbasic

Have this on two computers now, no clue how to fix this. Deleted the program and downloaded it again, still no luck. This happened on one computer during a hang of the program, I had to  forcefully close it.
Reply
RE: DATHeader 3.0.19.1
#11
Does this appen to you with all files, or just with a specific one? In this case it would be nice to send the file to help debugging...
Reply
RE: DATHeader 3.0.19.1
#12
(2017-01-23, 15:51)Philippe Hurbain Wrote: Does this appen to you with all files, or just with a specific one? In this case it would be nice to send the file to help debugging...

The error appears during startup of the program, last file I checked was part 18601.dat as it is on the part tracker now.
Reply
RE: DATHeader 3.0.19.1
#13
Annoying - especially on two different machines! I pinged Mike...
Reply
RE: DATHeader 3.0.19.1
#19
(2017-01-24, 16:16)Philippe Hurbain Wrote: Annoying - especially on two different machines! I pinged Mike...

Forget this post, i just saw that Magnus already had the same idea.

You say this happens during start of the application (DATHeader). There is a file on your system called DATHeaderini.xml.
Please rename this file and start DATHeader again.
If the error does not occur, then the DATHeaderini.xml file is corrupted. Delete it and start DATHeader again. You will be asked several questions for the setup of the application.
I hope this will fix your problems. (I guess you are working on Windows).
Reply
RE: DATHeader 3.0.19.1
#14
You could try and rename (or delete) the file "datheaderini.xml" in C:\user\username\documents
You'll loose all your settings in the program, but it should give you a fresh restart.
Reply
RE: DATHeader 3.0.19.1
#15
(2017-01-24, 16:39)Magnus Forsberg Wrote: You could try and rename (or delete) the file "datheaderini.xml" in C:\user\username\documents
You'll loose all your settings in the program, but it should give you a fresh restart.

There is an issue with the downloaded ldconfig.ldr file, for example lines with LEGOID 311/227 and LEGOID 179/296/131/315 are generating the errors in my case.
When removing the double LEGOID number entries in the file I could use DATHeader again.
Reply
RE: DATHeader 3.0.19.1
#16
(2017-01-24, 18:55)Evert-Jan Boer Wrote: There is an issue with the downloaded ldconfig.ldr file, for example lines with LEGOID 311/227 and LEGOID 179/296/131/315 are generating the errors in my case.
When removing the double LEGOID number entries in the file I could use DATHeader again.

I see.
Why do DatHeader read those lines? I'm sure Mike will find a solution. I use the alternative colour config file.
Reply
RE: DATHeader 3.0.19.1
#17
(2017-01-24, 19:25)Magnus Forsberg Wrote:
(2017-01-24, 18:55)Evert-Jan Boer Wrote: There is an issue with the downloaded ldconfig.ldr file, for example lines with LEGOID 311/227 and LEGOID 179/296/131/315 are generating the errors in my case.
When removing the double LEGOID number entries in the file I could use DATHeader again.

I see.
Why do DatHeader read those lines? I'm sure Mike will find a solution. I use the alternative colour config file.
Adding space char around / also solves the issue (// LEGOID 179 / 296 / 131 / 315 - Silver Flip-flop/Cool Silver/Silver/Silver Metallic). Maybe ldconfig should be updated to avoid the issue? Clearly the problem is with DH, but...
Reply
RE: DATHeader 3.0.19.0
#18
Datheader does not green lit parts with direct color:

2359p04.dat
Filesize: 187.850 byte - Errors found: 885

------------------------------------------------------------------------------------------------------------------------------------------------------
BODY TESTS
------------------------------------------------------------------------------------------------------------------------------------------------------
Line 632: Not all used colors in LDConfig.ldr. 4 0x29D8563 -125.81 0 -304.21 -126.68 0 -307.86 -129.19 0 -308.08 -131.56 0 -306.83
Line 633: Not all used colors in LDConfig.ldr. 4 0x29D8563 -125.81 0 -304.21 -131.56 0 -306.83 -131.44 0 -302.83 -130.81 0 -298.33
...
Line 1225: Not all used colors in LDConfig.ldr. 4 0x2927E62 -299.229 0 -36.8115 -290.481 0 -35.0555 -290.18 0 -37.4055 -299.229 0 -39.3115
Line 1226: Not all used colors in LDConfig.ldr. 4 0x2927E62 -309.586 0 -38.0159 -299.229 0 -36.8115 -299.229 0 -39.3115 -309.586 0 -40.4659
...
Line 1484: Not all used colors in LDConfig.ldr. 4 0x263564B 10.7 0 -158 11.375 0 -163.5 8.85 0 -162.7 7.8 0 -158.7
Line 1485: Not all used colors in LDConfig.ldr. 4 0x263564B 6.74275 0 -142.796 10.7 0 -158 7.8 0 -158.7 3.84274 0 -143.496

Report generated on 2017-02-11 with DATHeader version 3.0.19.1

Scantime: 40:52:279 minConfusedec:ms
LEGO ergo sum
Reply
RE: DATHeader 3.0.19.0
#20
(2017-02-11, 17:04)Willy Tschager Wrote: Datheader does not green lit parts with direct color:

2359p04.dat
Filesize: 187.850 byte - Errors found: 885

------------------------------------------------------------------------------------------------------------------------------------------------------
BODY TESTS
------------------------------------------------------------------------------------------------------------------------------------------------------
Line 632: Not all used colors in LDConfig.ldr. 4 0x29D8563 -125.81 0 -304.21 -126.68 0 -307.86 -129.19 0 -308.08 -131.56 0 -306.83
Line 633: Not all used colors in LDConfig.ldr. 4 0x29D8563 -125.81 0 -304.21 -131.56 0 -306.83 -131.44 0 -302.83 -130.81 0 -298.33
...
Line 1225: Not all used colors in LDConfig.ldr. 4 0x2927E62 -299.229 0 -36.8115 -290.481 0 -35.0555 -290.18 0 -37.4055 -299.229 0 -39.3115
Line 1226: Not all used colors in LDConfig.ldr. 4 0x2927E62 -309.586 0 -38.0159 -299.229 0 -36.8115 -299.229 0 -39.3115 -309.586 0 -40.4659
...
Line 1484: Not all used colors in LDConfig.ldr. 4 0x263564B 10.7 0 -158 11.375 0 -163.5 8.85 0 -162.7 7.8 0 -158.7
Line 1485: Not all used colors in LDConfig.ldr. 4 0x263564B 6.74275 0 -142.796 10.7 0 -158 7.8 0 -158.7 3.84274 0 -143.496

Report generated on 2017-02-11 with DATHeader version 3.0.19.1

Scantime: 40:52:279 minConfusedec:ms
I can confirm that the current version of DATHeader works this way. After inspection of the current specification I resume this to be a failure in DATHeader. So I am going to eliminate the test.
I hope this is what you want me to do - you did not wrote it :-)
Reply
RE: DATHeader 3.0.19.0
#21
Quote:So I am going to eliminate the test.

Actually it should look if the color is a direct color OR code is in LDConfig...
Reply
RE: DATHeader 3.0.19.0
#22
(2017-03-11, 7:22)Philippe Hurbain Wrote:
Quote:So I am going to eliminate the test.

Actually it should look if the color is a direct color OR code is in LDConfig...

Yes, this is done but in the other way. If the color is in LDConfig all is fine
If it is not in LDConfig it needs to be a direct colour with a special formatting.
If that is not ok an error is generated - "RGB value is not correct."

Thank you very much for this clear advice. :-)
Reply
DATHeader 3.0.19.3
#23
This is a bugfix version.

You can download the tool as always from http://ldraw.heidemann.org/index.php?page=datheader

cu
Mike
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)
Forum Jump:


Users browsing this thread: 1 Guest(s)