Download ETScript 4 beta!


(Flippy) #41

The bookmarks storing issue is now gone. There is no longer any need for the ‘the script has been modified outside of ETScript’ message as it no longer applies. The bookmarks are now stored separately in a “.bms” file alongside the script, and that file no longer contains the script text. So, another issue fixed.

I have also added a Date filter to the AutoBackup Manager (and planning to add it to the Revert to Backup window too) which allows you to select a date to filter on:

(The calendar is in dutch because my operating system is in dutch :wink: it will adept to your OS settings)

I’m progressing steadily, and expecting a beta2 release soon!


(Flippy) #42

I think I have fixed all bugs that were reported. I hope I didn’t miss any!

I believe I have fixed the outlining bug. It now works properly in the "class name { " format, with the opening brace on the same line as the class / event name.

During first startup, it is still impossible to select any other folder than ‘etmain\maps’, and you should still use this folder. However, if you have your scripts somewhere else, you can select a secondary ‘scripts’ folder in the Options. The Open / Save dialogs will initiate in this directory.

When you open a script file, the corresponding BSP file (based on its name) is searched in the same directory. If it is not found, a search for the same BSP file is done in the ‘etmain\maps’ directory you selected, as it is likely that your BSP file is there. If the BSP file is found in the etmain\maps directory, a message in the Message List informs you about that.
This is why it is important that you still use the correct etmain\maps directory.

Additionally, you can now also use the Select BSP button to manually select a BSP file to import.

The File Browser Task Pane will, by default, carry two directories: the etmain\maps directory, and your chosen scripts directory (if it is different than etmain\maps). You can now add or remove directories from the File Browser. Only directories carrying script files will be added.

The only ‘bug’ left is the weird contextmenu bug, where a different contextmenu was used for some reason. I have only seen this once and have not been able to reproduce it, so I’m hoping it was a one-off quirk…

I am still working on the readme, it’s a long write!

I will release a beta2 version very soon, probably tomorrow, containing a list of bug fixes and changes. I doubt the readme will be included (although I could always include a partially finished document? We’ll see…)


(Flippy) #43

ETScript 4 Beta 2 has now been released!

Here is a short changelog (I’m not sure if it’s 100% complete, you’ll find out lol):

Bugs fixed:
- Outlining is now reloaded after Splitting the document.
- Outlining now works properly for different brace syntax (opening brace on the same line as the class/event name).
- Map Select dropdown now positioned properly in the Auto-Backup Manager window.
- Apply button in options screen now applies changes correctly.
- Draw Line Modifications option now works.
- Entities are now coloured properly after changing BSP file.


New features:
- 'Script Directory' allows you to choose a script directory other than etmain\maps.
- File Browser now supports adding/removing directories.
- Select BSP file allows you to select a different BSP file manually to import entities from.
- Added a Date Filter calendar to the Auto-Backup Manager and Revert to Backup windows.

Download on the first post have been updated. So I need new mirrors, thanks in advance!!


(Nail) #44

mirror
http://ftp.freenet.de/pub/4players/hosted/et/tools/ETScript4_beta2_setup.zip

earlier post with mirror updated


(Flippy) #45

Thanks for your quick response :stuck_out_tongue:


(Nail) #46

no problem


(Diego) #47

This error pops up all over the place:


(Diego) #48

I rebooted my computer and had a whole bunch of computer errors. Et script will now load up without those .net Framework errors. However, it does not load in any data from the bsp file so the entity list does not work neither does the entity syntax highlighting.

I think I’ll reinstall the first beta and see if it still works. It was before I uninstalled it.

EDIT

Yes, the syntax highlighting and the entity list still work fine in beta 1.


(Flippy) #49

I think I might know the problem lol, I think I something went wrong while packing the installer and it forgot a DLL file. When I get home I can upload it so you can manually place it in the correct folder, and then it should work. I will also upload a new version this afternoon… Sorry!


(Flippy) #50

Ok, I have updated the link in the first post. It now contains the correct DLL files and should work.

Here’s the link again:
http://rapidshare.com/files/237446956/ETScript4_beta2_setup.zip

That also means your mirror (Nail) is now obsolete again, sorry!


(shagileo) #51

Well if you don’t mind, I also got a little mirror for you (the latest version with correct DLL files):

Download


(Flippy) #52

Thanks.
(10char)


(Nail) #53

file updated, link should be good again


(Flippy) #54

Here’s a sneak preview of what the next update will hold…

Yep, a fully functional Office 2007 Ribbon bar, including start menu, titlebar menu items and Vista Aero glass support.

Don’t mind the icons on the ribbon buttons in the screenshot, they are simple 16x16 icons stretched out to fill the larger buttons. I am making new icons as we speak, I’m just trying to get them to look consistent with the smaller ones.

Of course, if you don’t like it, you get the option to turn it off and switch back to the old classic menu + toolstrips.


(Diego) #55

Sorry, but this latest version still does not read the BSP file so I don’t get any entities. Downloaded it from both sites. Old one still works.


(Flippy) #56

Can you be more specific? The BSP importing seems to work just fine with me??
Did you check the Message List, maybe the BSP couldn’t be found? In which location is your script, and in which location is your BSP, and what path is your “etmain\maps” path option set to?

When I open a script, let’s say battery.script, it imports the entities and shows them in the Entity List. It also shows them in the “All” part of the List Members (Intellisense) window. It also colours them blue in the script.

When I then use the Select BSP button to select a different BSP, I can select goldrush.bsp for example, and I can then use all the entities from goldrush. They appear in the Entity List, the List Members window and they are coloured.

Only one bug remains: after importing a different BSP (using Select BSP button), the old entities that are already coloured are still coloured. I’ll have to take a look at that, but it doesn’t seem to be the same bug you mean??


(unf4z3d) #57

:\

i install, run it and:

only info i get from the windows report error thing…

EventType : clr20r3 P1 : etscript4.exe P2 : 0.2.0.0 P3 : 4a1ac9c2
P4 : etscript4 P5 : 0.2.0.0 P6 : 4a1ac9c2 P7 : 1b P8 : c6
P9 : system.invalidoperationexception


(Flippy) #58

Did you install .NET Framework 3.5?


(unf4z3d) #59

to my knowledge yes, as i did it with ati catalyst, ill try to installl again… :slight_smile:


(Diego) #60

I must have missed the meeting about the “Select BSP” Button. I thought it would load automatically like before.

I FAIL