Typ viewer

**sherco40** · 13th August 2015, 09:59 AM

Hi Mappperoni
Have you changed anything in your system? (new program install or Windows updates...)

Have you verified if you have COMDLG32.OCX in your systemfolder?
What is your OS? W8.1?

Mapperoni · 13th August 2015, 12:00 PM

I have W8.1 x64 with the last updates from tuesday.
No new programs I think.
COMDLG32.OCX is present in the Windows\SysWOW64 folder.

**sherco40** · 13th August 2015, 01:13 PM

Ok
Maybe, for an unknown reason it is no longer registered....? (maybe a problem with this Patch Tuesday?)
Please, try this version (the unique change is the registering of COMDLG32.OCX: I had forgotten to register this ocx in previous versions.... so if your COMDLG32.OCX is no longer registered, re-installing the previous versions of TYPViewer will not fix it...)

Spoiler:

**Ellinas** · 19th August 2015, 09:05 AM

New Greek language file:

[Only registered and activated users can see links. ]

**mullerh** · 28th August 2015, 08:30 PM

I am new to TYPviewer and modification of TYP files so I am probably missing something. I used a program IMG2Typ and I got the following Polygons identified in a TXT file as the draw order
[_drawOrder]
Type=0x0100,2
Type=0x0400,2
Type=0x0500,2
Type=0x0700,2
Type=0x0A00,2
Type=0x0B00,2
Type=0x0C00,2
Type=0x0E00,2
Type=0x1300,2
Type=0x1800,2
Type=0x1900,2
Type=0x1A00,2
Type=0x2000,1
Type=0x3C00,1
Type=0x4600,1
Type=0x4B00,0
Type=0x4C00,2
Type=0x4D00,2
Type=0x4E00,2
Type=0x5100,2
[End]
These types make sense to me. But when I open up the test file in TYPviewer I get the following:
[_drawOrder]
Type=0xb0000,0
Type=0x000,1
Type=0x60000,1
Type=0xc0000,1
Type=0x10000,2
Type=0x10000,2
Type=0x30000,2
Type=0x40000,2
Type=0x50000,2
Type=0x70000,2
Type=0x80000,2
Type=0x90000,2
Type=0xa0000,2
Type=0xa0000,2
Type=0xb0000,2
Type=0xc0000,2
Type=0xc0000,2
Type=0xd0000,2
Type=0xe0000,2
Type=0xe0000,2
[End]
I don't understand what is going on here, some even appear to be the same same polygon type.
Thanks for any help or clarification you can provide.

**sherco40** · 28th August 2015, 11:30 PM

Hi mullerh

The polygons with a type less than 0x100 do not have a subtype, so they are often coded 0x4B for example (only 2 digits because it is less than 0x100).
The polygones with a type equal or more than 0x100 have a subtype so they are often coded 10f04 for example (5 digits).

So in TYPViewer, the 2 forms are accepted: 0x4B or 0x04B00 (i.e. the form without subtype and so there are only 2 digits and the form with subtype and so with 5 digits)
But IMG2typ uses another convention : 0x4B00 i.e. 4 digits and TYPViewer does not correctly interpret this...

In a first time , you can add a "0" after the "0x" in your txt file in order to have 5 digits: the draworder will be correctly interpreted by TYPViewer.

Then I'll take a look in the code to see if it is possible to make TYPViewer compatible with the 4 digits notation.

Edit: you can try this new version :

Spoiler:

**mullerh** · 29th August 2015, 12:24 AM

Thanks for the explanation. I have a better idea of what is going on here with the TXT files I from IMG2Typ.
The results I was getting were totally baffling me.
I will try you new version and let you know.
Thanks again for your quick response

Hello Sherco40:
The Type interpretations in the _Draworder list now appear to be correct.
The Type interpretation in each Polyline/Polygon/POI specification contained in the TYP file still has the old error in it.

**sherco40** · 29th August 2015, 07:44 AM

The Type interpretation in each Polyline/Polygon/POI specification contained in the TYP file still has the old error in it.

Please , send me your txt file, you have just paste the draworder in your previous message, so I cannot look at the other sections of the file ([_polygon] etc...)