The model editor is the secondary part of QuArK. A model can represent a number of things depending on the game it is being created for. It can be an object like a prop, a table or chair. It can be a structure such as a door or an entire building. It can even be the terrain in a map. But typically a model is a character used to play in the game itself. The model editor lets you view, change and manipulate these kind of game models for the formats that QuArK's Model Editor supports.

Basically, a model is made out of a mathematical mesh consisting of individual triangular faces in 3D space. Each face of a model has three vertexes which can be moved, in 3D space, to form the shape of the models mesh. The entire mesh is then "Skinned" using a texture image file such as a .pcx, .jpg, .tga or some other format that the editor will support. The "Skin-view" page of the editor is used for this skinning process, where there is another set of vertexes of the "unwrapped" model mesh and their vertex handles that are used to move this flat mesh of the model over the texture image changing the projected image position of the texture on the model's 3D mesh and giving the model its final appearance.

The Skin-view page works a bit differently then the editor's views do, based on the fact that it has no actual triangles. Only what is known as view.handles, view being the view displayed on the Skin-view page itself. Another big difference, at this time, is that unlike all of the other views of the editor which are in a list of its editor.layout.view, the Skin-view page view is never actually added (appended) to that list, on a permanent bases, making it pretty much isolated from the rest of the views of the editor. Because of this I needed to create a global in the quarkpy\mdlhandles.py file called SkinView1 that can be used, when needed, to call that view when the Skin-view page is open. It does seem to be added periodically when the mouse cursor is actually somewhere within the Skin-view page view.