Changeset - a6af85c37419
[Not reviewed]
default
0 1 0
Tess Snider (Malkyne) - 9 years ago 2015-10-13 06:24:58
this@malkyne.org
README.md edited online with Bitbucket
1 file changed with 4 insertions and 0 deletions:
0 comments (0 inline, 0 general)
README.md
Show inline comments
...
 
@@ -46,15 +46,19 @@ You can solve this by doing a three-way 
 
In many cases, it may be easiest to go back and do these three-way tests after you have finished all of your other testing.
 

 
### Finishing Up
 

 
When you're done testing your reactions, you can either use the built-in Pigment Lab simulator (`Window > Run Simulator`) to experiment with recipes, without dipping into your precious ingredient stocks.  Alternatively, you can export your reactions in PracticalPaint format.
 

 
## Known Issues
 

 
### Slowness
 

 
If you are running on a multi-screen system, or a very high-resolution screen, you may find that Desert Paint Lab is rather slow in determining paint reactions.  That's because you have a lot of screen real-estate to scan, to look for the Pigment Lab dialog.  You can speed up the scanning process by ensuring that your Pigment Lab Dialog is as far to the upper-left of the screen as possible.
 

 
### Retina / High-Density Screens
 

 
High DPI screens may be displaying the game at something other than a 1:1 game-pixel to screen-pixel ratio.  These screens didn't exist, back when Desert Paint Lab was created.  A fix for this will be coming, soon.
 

 
## For Developers
 

 
This application was developed using [MonoDevelop](http://www.monodevelop.com/), using the [Stetic GTK UI designer](http://www.monodevelop.com/documentation/stetic-gui-designer/).
...
 
\ No newline at end of file
0 comments (0 inline, 0 general)