A quick look for you guys, what's there is done but the interface designer is still in the early stages. Just post any bugs and preferably what you did to cause it.

I'll post a translation file for who ever wants to translate it in a few days!

Download the setup

Any suggestions also appreciated




*NOTE*

• You must pick a plsc file to open, it will not open directories (i toyed with the idea of just directories but the options are there to open an installed version or a "working" version for a quick look at the script).
  
  
• if it doesn't open a script file it's because the XML in it is bad, nothing i can do about someone writing bad xml. (yes it's still bad even if Plus! itself still opens it)
  
• when a script is loaded, any bad xml files will generate an entry in the "interface log.txt" file. If the file was an interface file you can check here to see why it maybe wasn't parsed properly. This file is cleared once the application exits!

• First line of scriptinfo.xml should read:
  

  code:

  ---

  <?xml version="1.0" encoding="utf-8"?>
  <ScriptInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:msgpluscripts">

  ---

  
  
• Not escaping characters like ">" "&" etc with their appropriate html escape codes
  
  
• First line of interface files should read:
  

  code:

  ---

  <?xml version="1.0" encoding="UTF-16"?>
  <Interfaces xmlns="urn:msgplus:interface" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsichemaLocation="urn:msgplus:interface PlusInterface.xsd">

  ---

Nice, but what about fixing this?



Looks really ugly.

clearly a bug with vista then, i'll have to make a custom one i guess. It'll do for now

I can't open a script with the next code:

xml code:

---

<?xml version="1.0" encoding="utf-8"?>
<ScriptInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:msgplus:scripts">
    <Information>
        <Name>Test</Name>
        <Description>Testing</Description>
        <Version>1.0.3</Version>
    </Information>
</ScriptInfo>

---

i created a new script, packaged it, opened it up with winrar pasted your code above in, and tried to open it again and it worked without any problems. What was the message appearing?

Try just creating a script with the "New" button/menu in the designer and try opening it just in case i've seriously overlooked something

btw, it wont run in windows 7 RC1... even with compatibilities...

Got an error when trying to pack the script (see attachemnt), then the app crashed.

Works on Windows 7. The open box is just a problem with dimensions. If you stretch it corrects it's self and reveals another button.

Had problems opening and saving files though. Looks promising so far

ah it might be because im running 64bit windows 7... i dunno.... but it just wont run for me...

quote:

---

Originally posted by NanaFreak
ah it might be because im running 64bit windows 7... i dunno.... but it just wont run for me...

---

quote:

---

Originally posted by vaccination

quote:

---

Originally posted by NanaFreak
ah it might be because im running 64bit windows 7... i dunno.... but it just wont run for me...

---

Doesn't appear to work in x64 at all.

---

It didn't work at all for me on my Windows XP machine, I just got an "application has stopped working and needs to close" error. I'll look into it later to try find out why.

On my Vista installation it worked, and it looks good so far, although I find the "are you sure you want to close this tab" message kinda annoying (especially when you have a few open tabs and then try exit, meaning you have to click through a few message boxes before it actually quits)

quote:

---

Originally posted by effection

quote:

---

Originally posted by vaccination

quote:

---

Originally posted by NanaFreak
ah it might be because im running 64bit windows 7... i dunno.... but it just wont run for me...

---

Doesn't appear to work in x64 at all.

---

Ah, odd. I thought the "Any CPU" target took care of both x64 and x86 processors. I'll see what i can do, send me your msn so i can send you some ones to test if you'd like (i've got a 64bit processor but only 32bit XP at the minute)

---

quote:

---

Originally posted by pollolibredegrasa
It didn't work at all for me on my Windows XP machine, I just got an "application has stopped working and needs to close" error. I'll look into it later to try find out why.

On my Vista installation it worked, and it looks good so far, although I find the "are you sure you want to close this tab" message kinda annoying (especially when you have a few open tabs and then try exit, meaning you have to click through a few message boxes before it actually quits)

---

quote:

---

I've had this problem a few times If your app is it's reading any Messenger Plus! registry key (and I assume it will be), you'll need to set it to x86 mode. Any CPU means that on an 64-bit version of Windows, registry calls will read from the 64-bit area in the registry, whereas Plus! always saves its settings in the x86 area.

---

Bug (see attachment). Visual Studio output window:

quote:

---

The program '[856] Messenger Plus - Development Environment.exe: Managed' has exited with code -1073741819 (0xc0000005).

---

quote:

---

Originally posted by pollolibredegrasa
It didn't work at all for me on my Windows XP machine, I just got an "application has stopped working and needs to close" error. I'll look into it later to try find out why.

---

quote:

---

Originally posted by pollolibredegrasa
On my Vista installation it worked, and it looks good so far, although I find the "are you sure you want to close this tab" message kinda annoying (especially when you have a few open tabs and then try exit, meaning you have to click through a few message boxes before it actually quits)

---

js code:

---

var hello = function () {}
hello.prototype = {
    "world" : function () { Debug.Trace ( 'hello world ' );
}

var h = new hello();
h.world();

---

Yeah it does rely (at the minute) on MP!L being installed. And yes matty that is something i have previously thought about but i wont be working on anything new until i get these current errors ironed out

Anyone with 64bit versions of XP/Vista/7 give me your email so i can give you a test version

I've (hopefully) fixed the OS problem and i've fixed a problem with some files not opening.

To Do:
Fix open scrip dialog
Fix the folding strategy for code (not a priority)

Hopefully that's all the bugs for now sorted.