Reply to Re: New *WORKING* cross-platform editor
If you don't have an account, just leave the password field blank.
September 21st 2011, 10:04 AM
shevek
Sparrowhawk: No, that probably doesn't work for you. I'll quote my original post to explain:
I started writing a tool to fix this problem. That would be a DinkC preprocessor. I'm writing something that resembles normal C (no whitespace problems; for and while; no goto (I know C accepts it, but it shouldn't), real expression with operators that do what they seem to do (a *= b / 3 + 2)
There's more in that script which doesn't work in DinkC. Some things you can see there:
- "Normal" expressions (see above)
- No & before variable names
- No whitespace problems
- Sequence names ("item-w" is really a number, I don't want to know which; it's the sequence with weapon item images)
- Global variables don't need to be declared separately, if you define something without declaring it local, it is a global (not sure if I keep that one; I may add a "global" statement to mean this)
This script preprocessor is actually the reason I started this. The gui editor is just "extra".
I started writing a tool to fix this problem. That would be a DinkC preprocessor. I'm writing something that resembles normal C (no whitespace problems; for and while; no goto (I know C accepts it, but it shouldn't), real expression with operators that do what they seem to do (a *= b / 3 + 2)
There's more in that script which doesn't work in DinkC. Some things you can see there:
- "Normal" expressions (see above)
- No & before variable names
- No whitespace problems
- Sequence names ("item-w" is really a number, I don't want to know which; it's the sequence with weapon item images)
- Global variables don't need to be declared separately, if you define something without declaring it local, it is a global (not sure if I keep that one; I may add a "global" statement to mean this)
This script preprocessor is actually the reason I started this. The gui editor is just "extra".