SolarStrike Software

As you recall, modifiers were previously working not too long ago. I decided to, then, remove some code from the keyboard functions that I, at the time, thought was unnecessary and would speed things up (if only by a millisecond or two). Although this meant that modifiers still worked for some applications, RoM was not one of those. I've re-added the code to make it compatible with RoM again, as well as fixed/updated a few other things.

You can download MicroMacro 1.01b3 from the main download page. You are not required to get this update to continue using RoMBot, but it is recommended.

I downloaded that version. It's an SVN folder so I thought I'd look at "Show log". It shows that I have revision 13 installed. Revision 14 says "Fixed: Re-fixed keyboard modifiers to be more compatible". Does that mean that I don't have the revision with the fixed modifiers? Also 1 of the files has a red icon next to it, filesystemdevice.cpp int the src folder.

I committed it after packaging it (stupid me, I know). That's why you appear to have revision 13 instead of 14. Besides that, I need to fix the script that I'm using to package the releases, as it probably should not be including the .svn stuff.

As for your filesystemdevice.cpp, I have no idea. Resolve by by selecting "use theirs" to download the copy from SVN.

Administrator wrote:As for your filesystemdevice.cpp, I have no idea. Resolve by by selecting "use theirs" to download the copy from SVN.

Looks like the only difference between 13 and 14 are those changes to filesystemdevice.cpp so that would mean you packaged it after making the changes but before you committed them to SVN.

The good news, then, is that the packaged version is essentially rev 14 anyway.

Yes, that is correct. I'm confused, though. There was no changes to filesystemdevice.cpp, only keyboarddevice.cpp.

Anyways, if I recall correctly, you had the source for r13, but did not actually compile it yourself (hence, were actually using an older version of MicroMacro). Now you know you're up to date with all of the binary files, as well.

I just tested the modifiers. They work. That's great!

Just 1 question, if I wanted to fix the macro functions to use modifiers, is there a way to tell what version of micromacro is installed so I can allow or not allow modifiers?

Also do you know in which versions of micromacro the modifiers don't or do work?

The function getVersion() returns the version (obviously), but that does not include the beta number (if applicable). So, if getVersion() > 101, it should work for most people that don't have one of the few copies that had a bug or twelve with modifiers. It was fixed, broken, and re-fixed several times, so it's all very confusing.

Administrator wrote:The function getVersion() returns the version (obviously), but that does not include the beta number (if applicable). So, if getVersion() > 101, it should work for most people that don't have one of the few copies that had a bug or twelve with modifiers. It was fixed, broken, and re-fixed several times, so it's all very confusing.

So we shouldn't fix the use of modifiers until version 1.02 is out because we can't tell the difference between the 1.01 versions?

Yes, that is the case. Often, a new function would be added at about the same time as a fix, so you could check if that version were available if that function was non-nil. This time, however, no new functions were added.