MouseScroll as an Excel Add-in

[don922]

For anyone interested you can make MouseScroll into an Excel Add-In. I have done it and so far it is working great. The benefits of doing this is that when Christian updates the code you only need to update the add-in and all workbooks using MouseScroll will automatically be using the new code.

You do have to make one change to MouseScroll. You need to remove or comment out the line that says 'Option Private Module'. If you don't do this then the EnableMouseScroll and DisableMouseScroll routines will not be found by your project. It took me a while to figure this out.

If anyone is interested in doing this and needs detailed steps just let me know and I'll post them.

Don

[cristianbuse]

Hi @don922 ,

Apologies you wasted time on this. I obviously tested the Add-In approach but forgot to mention to remove the Option Private Module line. I have now removed it myself from the repo in the last commit 6f3d9df

Many thanks!

[don922]

No worries. I like tracking down bugs, although this wasn’t a bug. I didn’t know that option existed so I learned something new.

Thanks
Don

[cristianbuse]

#43 also falls under this discussion. Should the MouseScroll library handle concurrent documents if each project implements the library separately?

[don922]

If each project implements the library separately, not using it as an add-in, then no. In my add-in if I make mousescroll a class the then answer is no also. As I have it now mousescroll is a bas file and not a class and I realized that while it works, it won't work if multiple projects are using it at the same time because you have some static variables defined in some procedures. If I make mousescroll a class and then call mousescrollclass.enablescroll it will work. This is why I started another discussion on the public constants you have defined. Maybe I should have just asked here but I already started it.

[cristianbuse]

Hi Don,

If each project implements the library separately, not using it as an add-in, then no.

I agree.

I would fail to see the benefit when working in Excel - using an add-in would be better and would make more sense and show clear intent.

For apps that do not allow an add-in, it's still probably better to implement the code for each document separately. Otherwise, documents would become dependant on each other.