Shoutbox

quote:

---

Originally posted by Nagamasa
Hey Mattike nice script! I've used CD L before, but then I reinstalled it couple days back and I must say, the interface is definitely more user-friendly.

---

Thank you! I'm happy that you like it.

quote:

---

Originally posted by Nagamasa
One suggestion though, not directly at your script, but all countdown scripts, is to be able to select to in/exclude Saturdays and/or Sundays. For example...to countdown school-related topics (i.e., exams), it would make sense to count the classes left (imo)(Mon-Fri), and for employees, maybe Mon.-Sat..

---

I see what you mean, and I agree that it's an interesting idea. (Especially since I'm also having exams myself soon!)

I might want to give it a try someday, although I have no idea where I'm going to categorize this in the preferences panel. A new tab? A new button? I guess I'm going to have to make the window higher in order to keep extensibility. I'll see if I can implement it during the current BETA session, otherwise it'll be on my to-do list for version 2.2 or something.

Congratulations for the release Matti. The new features make this script even better.

BUG!!

Concerning CDL 2.1.014:

When importing preferences from this new version, I get to see that the XML file's prefs are "out of range".

I figured out that "Globals.js"'s line should be:

var PrefVersionRange = ["2.1.009", "2.1.014"];

EDIT:: A bug in one of Matti's scripts

I know that it's not possible to directly import v2.0 preferences to v2.1, but it seems that because I forgot to update that last number, you can't even import from the latest v2.1 to the same version. Damn it, I underestimated the severity of this, I thought only beta testers would notice.

I'll add this in the next version, which will likely be released soon. I'll first wait in case more bugs are found. Anyway, thanks for reporting!

Hehe, if beta testers don't notice, I usually have a look at the code myself

And I'll be 'bugscanning' for a while

quote:

---

Originally posted by SmokingCookie
Hehe, if beta testers don't notice, I usually have a look at the code myself

---

I checked the code, but I seem to forgot to change this while changing the version numbers from the last beta (2.1.012) to the public version number (2.1.014). Maybe I should write some kind of macro to do this automatically everywhere I need to change the version number. Anyone knows how to do this in Notepad++? (that is: find and replace something in multiple files with a parameter you specify)

quote:

---

Originally posted by Mattike
I checked the code, but I seem to forgot to change this while changing the version numbers from the last beta (2.1.012) to the public version number (2.1.014).

---

Yeah, I said that in my original post..

quote:

---

Originally posted by Mattike
Maybe I should write some kind of macro to do this automatically everywhere I need to change the version number. Anyone knows how to do this in Notepad++? (that is: find and replace something in multiple files with a parameter you specify)

---

No, but perhaps you can use some XML thingy:

Create an XML (e.g. MsgPlus.ScriptFilesPath\ScriptInfo\Script.xml).

You should do something like this:

code:

---

<?xml version="1.0" encoding="Unicode"?> <!-- Save as Unicode in notepad -->
<PrefRanges>
      <PrefRange Minimum="2.1.012" Maximum="2.1.014" />
</PrefRanges>

---

Now, you can get the ranges:

code:

---

function OnEvent_Initialize(MessengerStart) {
      getScriptInfo(MsgPlus.ScriptFilesPath + "\\ScriptInfo\\Script.xml");
      (additional code)
}

var PrefVersionRange;

function getScriptInfo(XMLFile) {
     F = objDOM.load(XMLFile); // true if loaded, false if not loaded
     if(F) {
          D = objDOM.selectSingleNode("//PrefRange");
          PrefRangeMin = D.getAttribute("Minimum");
          PrefRangeMax = D.getAttribute("Maximum");
          PrefVersionRange = [PrefRangeMin,PrefRangeMax];
          return true;
     } else {
          Debug.Trace(objDOM.parseError.reason);
          return "";
     }
}

---

I use the DOM object to get script information and update the ScriptInfo.xml automatically (I always forget the ScriptInfo.xml :P )

Well, that could be a solution indeed. I'll see what I do with it, thanks anyway!


This should fix the problem.

Uhh.. I'm afraid I have another bug.. Screenshot on its way..

Screenshot:



And I have MsgPlus 4.60.326 by the way.

EDIT::

Perhaps you could use something like this:

JScript code:

---

function getPlusVersion(sMinVer) {
      if(MsgPlus.Version < sMinVer) {
            return false;
      }
      return true;
}

function getPlusBuild(sMinBld) {
      if(MsgPlus.VersionBuild < sMinBld) {
            return false;
      }
      return true;
}

function OnEvent_Initialize(MessengerStart) {
      if(!getPlusVersion(MinimumVersion) {
            [What to do if MsgPlus.Version < MinumumVersion] // Versions greater than MinimumVersion should work
      }
      if(!getPlusBuild(MinimumBuild)) {
            [What you want to do if MsgPlus.VersionBuild < MinimumBuild] // Builds greater than MinimumBuild should work
      }
      [Whatever you want to do here]
}

---

But in fact, I would only look at MsgPlus.Version...