Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Tony

Pages: 1 2 [3] 4 5 ... 40
31
Help and Support / Re: Excel Crash
« on: April 18, 2017, 11:51:25 AM »
Hi,

has this problem started after upgrading to 3.2.2?

Please can you try un-installing PyXLL by removing it from the list of addins in Excel, then closing Excel, re-opening and re-adding PyXLL?

It's important that you close all instances of Excel after removing pyxll from the list of addins before re-opening to try again.

You can also try using this script to completely uninstall pyxll before re-installing it:
https://github.com/pyxll/pyxll-examples/tree/master/scripts

Kind regards,
Tony

32
Hi Alfredo,

I've just released 3.2.2, including the fix for the problems you were seeing with async_call and automatic array resizing.

I also fixed that last issue you were having when exiting Excel would sometimes crash because of the background Python thread not being shutdown cleanly.

I hope this has resolved all your issues now (except the one where Excel is sometimes busy when you try to call into it from a background thread, for which hopefully your workaround is satisfactory). If you do have any more problems when testing with your users please let me know.

Kind regards,
Tony

33
Help and Support / Re: Error opening COM addin
« on: April 12, 2017, 11:20:29 AM »
Great! That's for letting me know :)

34
Hi Alfredo,

yes that first problem is quite common. When calling into Excel if it's busy it will give you an error like that. In your cases, as you're calling back into Excel potentially while other calculations are going on you will probably see it quite often. You should add a small sleep (e.g. "time.sleep(10)") into your solution so whatever thread is causing Excel to be busy is able to continue.

I had an idea to change async_call to invoke the user function from inside an Excel macro, ensuring that your call would never be called until Excel was ready. This is a bigger change than the previous bug fix, but I will try it out and if it looks like a good solution I will include it in a future version.

That second problem is more concerning... I suspect that some background thread is not being shutdown correctly when Excel is closing, and then later tries to destroy the Python thread state after Python has been shutdown. I will investigate that and get it fixed.

Best regards,
Tony

35
Hi Alfredo,

that's great :) I have to do a release today or tomorrow anyway. I'm confident the changes I ended up making to fix this issue are an improvement and haven't introduced new problems, so I will include them in that release. If you find with your testing that there are still problems I can do another patch release soon after, it's not a problem.

Best regards,
Tony

36
Help and Support / Re: Error opening COM addin
« on: April 10, 2017, 10:50:12 AM »
Hi,

one thing that might cause this error was if for some reason Excel had disabled the PyXLL COM Addin (PyXLL is actually two addins in one - the plain xll that does all the worksheet functions and menus, and a COM addin that does the ribbon and RTD).

Please can you check your disabled addins by going to Options -> Add-Ins -> Manage Disabled Items (in the "Manage" drop down at the bottom of the addins panel). If PyXLL is in there try enabling it and see if that resolves this error.

Best regards,
Tony

37
Help and Support / Re: Error opening COM addin
« on: April 10, 2017, 09:53:42 AM »
Hi,

when you start Excel, those are not errors - they are just debug messages. They are normal. The Excel COM API isn't available when Excel first starts, so PyXLL keeps retrying periodically until it becomes available.

The error code you're getting when reloading corresponds to the error "E_ABORT". This is usually returned because some operation has been cancelled (e.g. by the user pressing Esc in the middle of some calculation, or Excel is busy doing something else). How are you reloading PyxLL (i.e. using the Python reload function, or via the ribbon etc)? Is there anything else going on at the same time? (e.g. do you have anything using the Excel COM API or any VBA code running that could be causing a conflict?).

Do you get this error every time you reload PyXLL, or just sometimes?

Best regards,
Tony

38
Hi Alfredo,

I'm pretty sure I've got to the bottom of this now. I've uploaded another build to the beta site

https://beta.pyxll.com/download.html
username: pyxll
password: pyxll

This build should fix the issues you've been having both with async_call and with auto resizing array functions.

Apologies it's taken a while to get you a fix for this. It was a pretty subtle problem that proved to be very hard to track down.

Please let me know once you've had a chance to try this, and if it's all good I'll get the next (non-beta) release prepared.

Best regards,
Tony

39
Hi Alfredo,

hold off testing this for now... I'm looking into it some more...

thanks,
Tony

40
I just uploaded another build to the beta site - I found an issue with the changes I made and the pop-up that appears if the license key is invalid. It shouldn't affect you, but thought I'd let you know anyway.

Best regards,
Tony

41
Hi Alfredo,

I've uploaded a new beta build:

https://beta.pyxll.com/download.html
username: pyxll
password: pyxll

I wasn't able to recreate exactly the problem you described, but I did find a potential cause for it - and this build fixes that. This should fix any problems with switching windows while auto-resizing arrays are being processed, and although I couldn't verify it, I hope it will also fix your problem with using async_call.

Please could you try it out and let me know?

Kind regards,
Tony


42
Hi Alfredo,

I've had a bit of a breakthough and think I now know what's causing the problem.

I should have new build for you to test either later today or tomorrow.

Best regards,
Tony

43
Hi Alfredo,

I'll try to reproduce the issue with Excel 2010 and 2013 too. Hopefully I will have more luck with those and will be able to find a work around.

Best regards,
Tony

44
Hi Alfredo,

I've been trying to reproduce this problem with your latest spreadsheet, but so far I've not been able to I'm afraid :(

I tried modifying your sheet so that the calculations were chained, as before, but that worked fine for me too. To try and make it fail I did a lot of clicking around and modifying cells (including the input cell A6) while it was still calculating, but I couldn't make it crash or freeze.

I've attached my worksheet and the function used, but neither this nor your original sheet failed for me :(

I wonder if it's something that's been fixed in an update to Excel, and I'm using a more recent version? I've been testing using Excel 2016 version 1609, build 7369.2120. You can check your version under 'product information' on the right hand side of the account screen in Excel. If your version is older, try getting the latest version and see if that makes any difference.

Best regards,
Tony


45
Ok thanks - I will continue to investigate

Pages: 1 2 [3] 4 5 ... 40