[T2Di 1.3 - Resolved] Missing gui cc / h files in on OSX

#1 @Marc - That's odd. Compiling worked for me and so did my dialogs. Let me pull down the build from the website, clean, and try it out.

#2 Which solution are you compiling (file path please)?

#3

Quote:Without these files, compiling TGB is not possible

Just delete the references in the XCode project. It was purposefully removed, and is not needed.

Also, why are you building TGB? The engine/compilers folder is meant to be replaced by per project project files. Making sure this is corrected asap as well. For now the fix in that project is up

#4 Fixed in the repo

New build going up tomorrow morning.

#5 Sven: I'm building TGB because Play Game is still not working along build project and basically any of the new buttons here on OSX 10.6. So the build is to rule out potentially build errors (as back with 1.2)
I'm not talking about the TGBGame build but the actual editor.

Removing this files: I don't think thats possible, given the editor is meant to work at all any longer (without a large collection of red lines in the log window. At least unless the editor scripts provided are not totally outdated.
These dialogs are currently in use by the openFileDlg.ed.gui and saveFile.ed.gui in TGB and executed as part of guiDialogs.ed.cs from main.cs directly in the Tools package


PER PROJECT buildFiles: They only cover Xcode_iPhone.
I'm trying to get the T2Di Editor working nicely on OSX. With the target of having all things working naturally :)
Sorry for not beeing 100% specific about the project in question.


I'm currently still hunting down the problems behind the following buttons:
- Open XCode Project / Build Project: They don't do anything. Log mentions that the batchfile was run.

No direct idea what might be causing it other than the spaces in the path potentially although OSX shouldn't be that stupid.

Here the corresponding log lines

Quote:Doing : /Users/dreamora/GayaSoft/Torque2D iPhone/T2D iPhone 1.3/tgb/tools/levelEditor/scripts/openXcode.sh; /Users/dreamora/GayaSoft/Torque2D iPhone/T2D iPhone 1.3/tgb/../MyProjects/test/buildFiles/XCode_iPhone/iTorque2D.xcodeproj
Finished running batchfile

Will create an own bug thread for that as soon as I have more of an idea what it is and given I don't find an already existing solution for it.


Michael: The project in question is XCode (not XCode iPhone)

#6 Have you tried without spaces ? Thats weird it works great on my Snow Leopard as well. Testing shortly as well (though, i tested this last and i know that it works, as Michael tested as well). Build Project Button -> this will just open the project in XCode, you can open it from the buildFiles/XCode_iPhone manually, but i will look into that.

Per project build files for XCode -> This was missing in the build. They should be in the new build tomorrow morning vegas time.

#7 Just tested it without spaces, no change here.

OSX 10.6.2 here (Upgraded from 10.5), XCode 3.2.1 64bit (iPhone SDK for 3.1.2)


If all that build does is open the project file them I'm fine with it as it is, no problem then for me as I'm having it open normally anyway.


Thanks for the fast response on the two reports.
Was really looking forward to 1.3 and so far aside of this two issues it seems to work just as good as expected.
Will really be looking forward to see how it performs on my old prototype especially once its upgraded to the srcRects

#8 No problem,

Link to follow the fixes

Not all bugs will be listed there, but this will hopefully help us keep track (things like play game, i had no idea even after scouring the forums to death).

#9 Window version is crashing after opening a project in Windows 7. Anyone experiencing this problem?

#10 Same. On Vista 64bit crashing after open project

#11 Me too, will not run windows 7 home premium. Tried running on two different PC's Works fine on the mac however I hate working on the mac...

#12 I run everything on windows 7. Can you check the console log please?

#13 T2D 1.3 crashing when you open project.

#14 Hey Sven, on my Windows 7 (64-bit) computer, i tried opening the iPhoneExample project and it crashed. Here are the last lines of the console.log. Hope that helps.

Torque Game Builder (v1.7.4) initialized...
Torque2D for iPhone | v1.3 is active...
% Opening Project C:/Users/phuong/Desktop/itgb 1.3 official/T2D_iPhone_Windows_v1.3/T2D_iPhone/MyProjects/iPhoneExample/projectFiles/project.t2dProj ...
Executed C:/Users/phuong/Desktop/itgb 1.3 official/T2D_iPhone_Windows_v1.3/T2D_iPhone/MyProjects/iPhoneExample/projectFiles/game/managed/datablocks.cs. Took 15 ms
Executed C:/Users/phuong/Desktop/itgb 1.3 official/T2D_iPhone_Windows_v1.3/T2D_iPhone/MyProjects/iPhoneExample/projectFiles/game/managed/brushes.cs. Took -1 ms
Executed C:/Users/phuong/Desktop/itgb 1.3 official/T2D_iPhone_Windows_v1.3/T2D_iPhone/MyProjects/iPhoneExample/projectFiles/game/data/levels/emptyLevel.t2d. Took 16 ms

#15 My console log looks exactly the same.

#16 Regarding crashes on Windows

I am unable to replicate this on Vista 64 or XP. When I get to the office I will try on a Windows 7 as well.

I'm wondering if this has something to do with previous builds being installed. Do you have a previous version of iTGB installed? (1.2 or T2Di 1.3 Beta)

If so, delete those. If you have already deleted them, make sure you have cleared out the config files installed by previous builds. These are typically found in:

C:Documents and SettingsUSER_NAMEApplication DataGarageGames (That's an XP OS). I'll check Vista when I get to work to see if it saves config files to another directory. This was an issue with previous builds being released, and older versions' config files messing with the system.

This could very well come down to how Windows manages files being written/read from HD. Vista and 7 tend to want all dynamic files to be stored in the user's documents folder, and does not like things being written to desktop and root C: directories. Again, it's difficult for me to test this since I cannot reproduce this bug.

Has anyone actually tried debugging from a compiler?

#17 According to Serhiy, the above worked for him:

Link to confirmation. Please let us know if this fixes your issues.