Game Development Community

GUI save issue

by elvince · in Torque 3D Professional · 06/22/2009 (11:25 pm) · 8 replies

When you build a new gui and you want to save they are 2 issues:

1/When you save your file, by default its name is guiYOURGUINAME and your are 1 folder up of the current gui folder. I'm pretty sure that the add of gui to your name is in fact the default folder name to save gui. More, when you try to save after, you have another "name" issue as this time you will be in another folder with addtional characters before your gui name

2/ CTRL S is not working in all the area of the editor.

#1
06/23/2009 (12:36 am)
For your first problem, even after executing it in somewhere like exec("./ui/...gui");, does it give you same problem?
#2
06/23/2009 (10:29 am)
Once load, it seems to work well, so it's mainly during creation of a new gui.
#3
06/24/2009 (5:16 am)

Save/load issues confirmed. Fixed for B4.

Can you say where in particular the save hotkey does not work. I've tried and it reliably triggered a save.
#4
06/24/2009 (12:10 pm)
When you are editing a value and then ctrl+S to save the change in the gui. The save screen is not triggered.
#5
06/24/2009 (12:19 pm)

Ok, not on Mac. Have to check Windows. Could be that a control is swallowing the keypress when it sees the control modifier which would explain it doesn't happen with the command key on the Mac.

Thanks for the follow-up, elvince.
#6
06/24/2009 (3:19 pm)

Good news: except for the possible hotkey capturing in edit controls, the GUI editor save/load issues should already be fixed in B3. Please test.
#7
06/25/2009 (12:52 am)
Sorry the bugs is still there.

Way to reproduce:
Create a new gui, save it in Art/gui and not in the default folder.
Create a new gui and save it... bang you have the bug.



#8
06/25/2009 (4:37 am)

Ok, the relevant changes possibly did occur after the cutoff line and not before. This beta packaging and my checkins for these changes happened basically simultaneously. Have to check.

But anyways, this is fixed in the repo and thus for anything forthcoming.

Thanks, elvince, for testing and sorry for the inconvenience.