Bug in Prop Tool !

Rayman

I think the Prop Tool (version 1.3.2) has a problem with embedded data files...

The problem is that if the editor opens the embedded file, which it sometimes does automatically, it either crashes or messes up the main program.

I'll attach the code I'm working on now as an example.
SSD1963_Demo2 - Archive [Date 2013.01.12 Time 07.50].zip

Easy Proof: If you look at the code size of the main program with and without the embedded data file opened in the editor, you can see the Prop Tool even reports a different code size...

The embedded data file is called "VGA_HiRes_wHeader.dat".
If someone clicks on the driver "SSD1963_Driver2b" in the tree window (top-left of PropTool) this file is opened automatically and will then mess up compilation.

Is this a new problem? Or, maybe I'm the only one using the file command? Or, is there something special about this particular data file that the Prop Tool doesn't like?

kuroneko

Compile order kicks in here. Files (being part of the compilation) in a tab have preference over files on disc. The font file is treated as 4 char text file (check the DAT section size in *Driver2b). And that's exactly the difference you can see for the code size.

Rayman

kuroneko, thanks for taking a look and glad you see the same thing as me.
The Prop tool usually shows only the first 4 bytes of this 5 kB file. But, sometimes it shows nothing and sometimes it crashes...

I wish it would just not try to open it...

In any case, I don't think that just having a file open should change the output of the compiler...