Here are my few things I just have in my mind:
1) You can get used to it! It's OK as any other way to control the programs functions! (My opinion!)
2) Yes, it does what I thought it should do!
3) The light-map-thing is very nice!
4) Actually I have no idea, maybe the remaining (unfound) bugs?
5) 1. If someone chooses a large viewdistance (for example: 1.000.000) (at startup of a new map, there was somewhere a dialog that ask for "mapsize" or something), and then enables the "GRID"-option from the menue, the performance gets very (s)low! (Cause the lines are drawn very far away!) Maybe somekind of a distance-clip for the lines might help here! (Or limiting the viewdistance!)
2. I tried a "test-map" where I set up some of your examples and then positioned some lights, then calculated the light-maps! After a while the progressbar was full and the light-maps were there too, BUT the dialog-window with the progressbar was still there and I couldn't close it!
3. The lights/entities that are selected should have the position-attibutes on the "object-tab" activated, so that a fast and easy placement is possible! (Without translating on the axis with the different translation-buttons!)
6) All named options are very interesting!
(first thing named = higher rating):
b) Dark-Physics implementation would be fine, with something to enter data for objects etc. like named before in this thread!
a) Sparkys-Collision is very nice (I used it in the DP-Sw-Mode-Comp to bypass the Demo-Limits) and would be cool to see it implemented into your editor!
This would allow the use of "triggers" (objects invisible (hidden), but reacting to collisions with other SC_col-objects), which you can give attributes (for example what action should be performed when a collision occurs (play a sound etc.) and what kind of collision-check (all objects, groups, etc.))!
7) I would rate it actually a "7" (cause I had not tested it too long, but in that time I had some complications as mentioned above, although the first thing mentioned was a result of my behaviour to make "crazy" inputs when dialogs appear!
BUT it is a programm with a very high potential!!!)
Sorry for the many brackets, it's a habit of me to put "sub-info" into my sentences!
Keep up the good work!
Hoozer
AMD 64X2 4800+ (939); 2GB; GF 6800LE (@12PS, 6VS; 380 MHz, RAM: 434 MHz)
DP-Sw-Mode-Comp-Entry (updated to V. 1.2):
http://rapidshare.com/files/3326313/PhysiX-Brick-Breakout---V--1-2.zip