30.11.2007, 00:52:42
I wanted to clearly separate custom cursors from the originals this time.
There's no [MouseCursors] section and there are no names for the customs, you specify them directly on the unit/SW/whatever.
Example for a SW (nuke cursor):
The prefix varies for other things.
A unit's deploy cursor for instance might be done with DeployCursor.Frame=110, etc...
Advantages:
- no list = no hunting all over the ini, only one edit required
- overviewable due to a structured tag naming (inspired by programming languages as you might notice)
Disadvantages:
- not sure whether not having names is a disadvantage...
As for modifying the originals, it's a possibility.
WW's mouse cursor data lies in the R/W segment so it can be modified at runtime.
Maybe I should introduce a MouseCursors section after all, but rather than holding lists it holds the default mouse cursor info:
Tote.Frame=...
Tote.Count=...
etc.
Would not be a required section.
What d'you think?
There's no [MouseCursors] section and there are no names for the customs, you specify them directly on the unit/SW/whatever.
Example for a SW (nuke cursor):
Code:
Cursor.Frame=319
Cursor.Count=10
Cursor.Interval=4
Cursor.MiniFrame=513
Cursor.MiniCount=1
Cursor.HotSpot=Middle,Center ;yep, words this time... (Top/Middle/Bottom), (Left/Center/Right)
The prefix varies for other things.
A unit's deploy cursor for instance might be done with DeployCursor.Frame=110, etc...
Advantages:
- no list = no hunting all over the ini, only one edit required
- overviewable due to a structured tag naming (inspired by programming languages as you might notice)
Disadvantages:
- not sure whether not having names is a disadvantage...
As for modifying the originals, it's a possibility.
WW's mouse cursor data lies in the R/W segment so it can be modified at runtime.
Maybe I should introduce a MouseCursors section after all, but rather than holding lists it holds the default mouse cursor info:
Tote.Frame=...
Tote.Count=...
etc.
Would not be a required section.
What d'you think?