Reply to Re: New *WORKING* cross-platform editor
If you don't have an account, just leave the password field blank.
December 29th 2011, 07:04 AM
shevek
Just a side note shevek - did you add that one file missed out of the first zip back in??
I did. However, it makes me think of something I needed to do to make things work for you.
The values that you fill in in makecache are only defaults. If the actual configuration file doesn't exist, it will write a new one with those values. If it does exist, the existing file is used.
This means that if you tried running makecache before you made those changes, it will have written a configuration file with the incorrect values. If you change them in makecache, that doesn't work, because it will not overwrite the configuration file.
So, if you want to make changes after you tried running it, make them in the configuration file instead of makecache. This means you must find out where it is.
It is in the user settings directory, called pydink\dinkconfig.py. I don't remember where the user settings directory is on Windows, though. Something like c:\users\<name>\settings\ or so. If you add a line to makecache saying
directly after
it will tell you (before the error message) when you try running makecache again.
When writing values with backslashes in it, please make sure that you have an 'r' before the opening quote, so r'c:\...', like MsDink showed.
As to Anon's question about what to change in pde.gui (.in if you use xmlgen to generate it; the .in-file is much easier to read IMO, but if you edit pde.gui it means you don't need run (or have) xmlgen, which may be worth more for some people), you should change the values for run-script and edit-hardness. They should be commands to run in order to start a text or bitmap editor respectively. In Windows, make sure you specify the complete path to the executable. If there are spaces in it, put quotes around the command (make sure to use different quotes from the ones around the entire value). Also, if your eyes hurt from the colours, this is where you can change them.
Don't touch the names, only the values. In the rest of the file, if you reorder the fields (or comment them out), the gui will show the changes that you made (after restarting pde).
I did. However, it makes me think of something I needed to do to make things work for you.
The values that you fill in in makecache are only defaults. If the actual configuration file doesn't exist, it will write a new one with those values. If it does exist, the existing file is used.
This means that if you tried running makecache before you made those changes, it will have written a configuration file with the incorrect values. If you change them in makecache, that doesn't work, because it will not overwrite the configuration file.
So, if you want to make changes after you tried running it, make them in the configuration file instead of makecache. This means you must find out where it is.
It is in the user settings directory, called pydink\dinkconfig.py. I don't remember where the user settings directory is on Windows, though. Something like c:\users\<name>\settings\ or so. If you add a line to makecache saying
print name
directly after
name = os.path.join (p, 'dinkconfig.py')
it will tell you (before the error message) when you try running makecache again.
When writing values with backslashes in it, please make sure that you have an 'r' before the opening quote, so r'c:\...', like MsDink showed.
As to Anon's question about what to change in pde.gui (.in if you use xmlgen to generate it; the .in-file is much easier to read IMO, but if you edit pde.gui it means you don't need run (or have) xmlgen, which may be worth more for some people), you should change the values for run-script and edit-hardness. They should be commands to run in order to start a text or bitmap editor respectively. In Windows, make sure you specify the complete path to the executable. If there are spaces in it, put quotes around the command (make sure to use different quotes from the ones around the entire value). Also, if your eyes hurt from the colours, this is where you can change them.
Don't touch the names, only the values. In the rest of the file, if you reorder the fields (or comment them out), the gui will show the changes that you made (after restarting pde).
