just an idea, you could detour the CreateFile() call and set the FILE_SHARE_WRITE flag
I could help here and there if I was more familiar with Git. Does CodeBlocks has any kind of integration with Git?
Do you work with Visual Studio? you could create a solution that compiles it ... =D
@Frizi:
DONE, took me some time but I completely updated the address.asm table
I successfully compiled Phyngal and got it to run and recognize the actual sc2editor version, but the editor just keep crashing and I couldn't yet be able to really debug where is the problem because Blizzard putted some kind of global exception handler so I can not catch where the error is occurring
But I think that will eventually get Phyngal to work, so what is your plan if Phyngal just works and you got to make just the same tool again?
It is almost impossible to google for an old version of SC2Editor.exe, so just get it here plz (v0.19.0.15976)
I haven't done too much modding with the Galaxy editor as I did in wc3, so I dont know what kind of tool makes sense to integrate directly in the editor for scripting, I mean, maybe doing another TESH wouldn't be reliable.
What kind of editor you want to embed? Will it need to read the actual trigger data in memory? I think that Galaxy editor is much more complex than WE in how the triggers in the Trigger Editor can be organized, there can be many levels of categorys and many types of itens it the trigger tree, finding this data in memory is just too much work, anything requiring some kind of integration in the actual UI of the editor will be very hard to accomplish
My idea would be to make an application that runs apart from the editor, that would detect when the editor is running and inject whatever is necessary.
-It would feature an separated trigger editor. Triggers created here have no relation with triggers created in the editor, they would be just contained in an XML of the map, like an import.
-API for allowing to have parsers like Andromeda
-It would integrate with Galaxy editor by knowing what map is currently opened, and automatically showing those triggers that are contained in the XML import
-Would need to monitor events that occur in Galaxy editor like: saving the map to also save the triggers to the XML; user closes/opens another map so we refresh the triggers tree, and so on ...
I have already disassembled Galaxy to get the list of maps currently opened, and could detect many events related to opening/closing/switching the active map. This events plus those that we can grab from phyngal, is about all we need to create this idea of application
Maybe this weekend I will take a look and get those updated address. If you want, I have a copy of an old version of SC2Editor.exe in which you can view what those address are.
@Frizi: Go
just an idea, you could detour the CreateFile() call and set the FILE_SHARE_WRITE flag
I could help here and there if I was more familiar with Git. Does CodeBlocks has any kind of integration with Git? Do you work with Visual Studio? you could create a solution that compiles it ... =D
@Frizi: Go
It is almost impossible to google for an old version of SC2Editor.exe, so just get it here plz (v0.19.0.15976)
I haven't done too much modding with the Galaxy editor as I did in wc3, so I dont know what kind of tool makes sense to integrate directly in the editor for scripting, I mean, maybe doing another TESH wouldn't be reliable.
What kind of editor you want to embed? Will it need to read the actual trigger data in memory? I think that Galaxy editor is much more complex than WE in how the triggers in the Trigger Editor can be organized, there can be many levels of categorys and many types of itens it the trigger tree, finding this data in memory is just too much work, anything requiring some kind of integration in the actual UI of the editor will be very hard to accomplish
My idea would be to make an application that runs apart from the editor, that would detect when the editor is running and inject whatever is necessary.
-It would feature an separated trigger editor. Triggers created here have no relation with triggers created in the editor, they would be just contained in an XML of the map, like an import.
-API for allowing to have parsers like Andromeda
-It would integrate with Galaxy editor by knowing what map is currently opened, and automatically showing those triggers that are contained in the XML import
-Would need to monitor events that occur in Galaxy editor like: saving the map to also save the triggers to the XML; user closes/opens another map so we refresh the triggers tree, and so on ...
I have already disassembled Galaxy to get the list of maps currently opened, and could detect many events related to opening/closing/switching the active map. This events plus those that we can grab from phyngal, is about all we need to create this idea of application
@Frizi: Go
Maybe this weekend I will take a look and get those updated address. If you want, I have a copy of an old version of SC2Editor.exe in which you can view what those address are.
What tool you used to compile the phyngal source?
I know how to do it, but we would also need someone that knows how to compile the ASM source