Have you got any plans to support upgrades/techs, Roy?

Yes, I have plans for it. Farty's even given me great suggestions on how to represent some DAT stuff in the UI.

Oh I see! I was using the Unit ID instead of the Index ID !!! Thanks to you Roy, my problems have vanished.

I'm completely redesigning the backend and UI for this program, which is going to take more time than I originally estimated (i.e., I'm basically starting from scratch). I'm actually going to be working with the MVVM pattern over the course of the next three months, which is also the pattern I'm going to use for the UI modules of the project. UI aside, however, I have mostly constructed the design of the backend and will begin tying things together over the course of this week.

But you guys probably don't care about the technical details, so I'm going to offer a little dummy preview of the UI design. Keep in mind most of this demo does not actually work, but it's meant to show the direction I want to move towards.

Download Demo

Let me know what you like, hate, or want to see changed in regards to the UI, as this would be the best time to mention it.

I rather like it-- certainly makes the whole process very intuitive. If there weren't a computer monitor in my way I'd hug you.

It crashed when I went to Display Text.

Hopefully the crash(es) aren't significant at this point.

No, the crashes aren't significant. A lot of the code was commented out because I was in the middle of refactoring it, so I'm not surprised that it is unstable (because the UI is too tightly coupled with the backend, which is another reason why I'm redoing the project). The purpose was to show the UI layout, and from what I can tell, it does that properly.

Just found this. Very cool Roy! Was it made with Visual Basic? Or C#?

Quote from CecilSunkure

Just found this. Very cool Roy! Was it made with Visual Basic? Or C#?

Nice find! This was made with (and is currently being developed in) C#.

Here's a status update for anyone who cares enough to wonder: I had some issues with my source control and lost a lot of work I had put into the project, but I have a decent memory and have been piecing it back together (I've probably caught most of the way back up over this weekend). I'm only a few steps away from completing the backend, after which I'll start working on the UI (which I have a general plan for, but less experience in). The UI is going to follow the same structure as the UI demo a few posts above unless anyone has any objections.

Here's the current rundown for the next release features:

• Support creating and managing multiple EUD triggers
  
• Support multiple EUD conditions and actions for a single* trigger
  
• Support exporting trigger data into an existing map

* May actually be more than one trigger (e.g., display text detection requires 11 triggers)

Unless anyone has suggestions for any other important features, that will be it.

Don't bug me about adding new types of EUDs to the program yet (believe me, that list is long enough already). Once I push out this next release, I'll start on upgrade/tech EUDs, more unit EUDs, more text-related EUDs, key press EUDs, etc.

Wonderful MUAHAHAHA!

Soon I'll be able to complete my death ray :3

Well, hello there, I'm pretty new to the forum, in fact this is my very fist message, so I apologize for any newb'ness I might have.
I just wanted to report that the download link in the first post is broken; It downloads, alright, but the file itself is damaged. I suggest you re-upload it.

Thanks for your attention, xKanade.

The host I was using has issues with zip files and doesn't allow executable files. I put the program on Sen (I'll make a DLDB entry in a second) and a mirror link on Opendrive.

Also, welcome to Sen, xKanade! Think about making a new Introduction topic, because we love welcoming new members to the community.