-
|
PKHeX.Drawing is basically a small set of functions which is then consumed by PKHeX.Drawing.PokeSprite which is then further consumed by PKHeX.Drawing.Misc and then all three are consumed by PKHeX.WinForms. But if they are all consumed the main application why even have them like this instead of a single project in the solution? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
If you want to build it to a single file use the portion of the guide labeled "Building as a Single File" located towards the bottom. I have included the link below. |
Beta Was this translation helpful? Give feedback.
-
|
It is not that I was looking for a single file but more I was trying to understand the design decision. |
Beta Was this translation helpful? Give feedback.
-
|
If I had to guess I would say the misc.all file is possibly for items. Sprite.dll deals with the Pokémon images. Core.dll keeps track of Pokemon event data. I'm pretty sure these files all exist separately for cleanliness and organization. |
Beta Was this translation helpful? Give feedback.
-
|
Some reasoning was provided in the commit that split the project up in the first place: bc809af Some projects, like PoGoEncTool, don't depend on all of the PKHeX.Drawing projects. |
Beta Was this translation helpful? Give feedback.
Some reasoning was provided in the commit that split the project up in the first place: bc809af
Some projects, like PoGoEncTool, don't depend on all of the PKHeX.Drawing projects.
pkNX was also eventually changed to depend on PKHeX.Drawing.PokeSprite, since some sprites included in PKHeX.Drawing.Misc, like the box wallpapers and ribbon sprites, are not necessary for the tool.