AGS 3.0: Your feedback would be appreciated

[monkey0506]

Possibly, it has always just felt a bit outdated and overly stringent (I break up words in variables with underscores so it's "big_gas_tank" instead of "BigGasTank" in other languages), plus I just find it alot faster to process, but
I guess if noone else is overly bothered then I can live with it.

So long as you're always defining your own variables this way, then I don't see why it would be such a big issue other than simply having to conform when using the built-in variables.

IMHO case-sensitivity in the language actually forces users to conform to a cleaner and more standardized scripting style. Consider the following:

Code: ags

gUitYPe* myGuI = GuiTypE.getaTscReeNxY(mOUse.X, MoUSe.y); // the GUI-class would have to be renamed to prevent confusion with the gui array
iF (MygUi != NulL) mYGui.cONtRolS[5].viSIbLe = fALsE;

Code: ags

GUI* myGUI = GUI.GetAtScreenXY(mouse.x, mouse.y);
if (myGUI != null) myGUI.Controls[5].Visible = false;

The case-insensitive version is probably a bit extreme, but if we're going to do away with case-sensitivity, let's do it up right!

The case-sensitive version is more clearly legible and it also provides for reasonable collisions like the GUI type vs. the gui array or the String type vs. the string type. There are obviously occasions where collisions could cause confusion, but IMO the built-in collisions have always been very reasonable.

Furthermore, removing case-sensitivity would break virtually every AGS script ever (including built-in headers and things of that nature).

Personally I don't think that removing case-sensitivity is a good move for AGS, and I'm fairly certain CJ will side with me on this one. But of course this is just my two cents. Which unfortunately...just broke my bank. Damn.

[Khris]

I absolutely concur. E.g. I usually name my struct "Tile" and the corresponding array "tile". Very clean and convenient.
Ditching case-sensitivity is baaad! No twinkie!

[Pumaman]

Teeny possibly redundant or already implemented suggestions aside, easing out case-sensitivity might be a wise decision for the future, it would avoid alot of stupid errors and typing time, I can't think of any negative reason at the moment.

I have no plans to do this at the current time.

But in 2.72 there was an option to pop up  a GUI if the mouse was above a certain y coordinate. This should be usable for "bottom-GUIs" aswell (if I'm missing something, beat me up or something).

That's a possibility, but it's so easy to script it that so far it hasn't really been worth adding as a built-in feature.

1) I *hate* the crosshair selction for hotspots. It just was so much more convenient to have an actual "pixel square" marking the hotspot of cursors and inventory items.
2) Could we have a "remember outlay" feature? Each time I launch RC4 the tree and settings windows are reset to their default states, and I need to enlarge the tree view a good deal to have all entries visible (You may remember I'm one of those old-fashioned 800x600 users).

Does anyone else have any strong feelings about the cursor hotspot marker in 3.0?
As for remembering the window position -- it should remember the position and size of the overall editor window, and the tree defaults to a reasonable width so that you can see a reasonable amount. What's the problem here, exactly?

I think it is absolutely essential that the install wizard detects if .NET framework 2.0 is installed or not.

Is this not working at the moment? The current AGS 3.0 installer should detect this and warn you if it's not there.

also, why the fuck theres no more support of the .PCX format? it will be a pain in the ass to convert all that content...

Well since you asked so nicely, I'll get right onto it  :

[NiksterG]

2) Could we have a "remember outlay" feature? Each time I launch RC4 the tree and settings windows are reset to their default states, and I need to enlarge the tree view a good deal to have all entries visible (You may remember I'm one of those old-fashioned 800x600 users).

As for remembering the window position -- it should remember the position and size of the overall editor window, and the tree defaults to a reasonable width so that you can see a reasonable amount. What's the problem here, exactly?

I think what he means is that when opening AGS, the tree where you can find GUIs, Characters, Views, etc. goes back to the default, where everything is un-extended. I think what he would prefer (and I as well) would be if AGS could remember what was open so that we wouldn't have to click on those tiny plus signs everytime in order to see the subfolders.

[Shane 'ProgZmax' Stevens]

Does anyone else have any strong feelings about the cursor hotspot marker in 3.0?

Yes, I prefer the crosshair exceedingly to the old format, though perhaps having a missing pixel at the center (like many art programs or the old SCUMM cursor) might help precision slightly, like:



or even



Both let you better see the plotting position of the pixel.  Simply enlarging it may help with this, however, since for me the crosshair is quite small even at 1024x768 (it's resolution seems higher than the actual backgrounds)?

[Ghost]

2) Could we have a "remember outlay" feature? Each time I launch RC4 the tree and settings windows are reset to their default states, and I need to enlarge the tree view a good deal to have all entries visible (You may remember I'm one of those old-fashioned 800x600 users).

As for remembering the window position -- it should remember the position and size of the overall editor window, and the tree defaults to a reasonable width so that you can see a reasonable amount. What's the problem here, exactly?

I think what he means is that when opening AGS, the tree where you can find GUIs, Characters, Views, etc. goes back to the default, where everything is un-extended. I think what he would prefer (and I as well) would be if AGS could remember what was open so that we wouldn't have to click on those tiny plus signs everytime in order to see the subfolders.

Yes, that *and* the size of these panels, too is what I meant. Also the size of the  sprite panel, and so on. Basically, remember the position of the splitters (if that's what they are called)- the lines you move to resize parts of the editor.

[Ishmael]

I don't mind dragging the splitters around, but the window doesn't seem to remember it's size for me for some reason... Tho my computer seems messed up enough already that it might be just me there.