#AUTOCAD 2010 64BIT CODE#
I have tried all sorts of things to solve this with no success other than refactoring the code to eliminate the particular line the causes the problem. This is not a solution, but you can at least get through a process using this method. This means having the command button disable itself on its first press so that the user does not inadvertently refire the process either with a heavy finger or just not realizing that their might be a delay.Īs for the rejected by callee error, when this happens you can always press the debug button followed by an F5 button press to ride through the error. Also, in some extreme instances you may need to debounce a command button. This was possible pre-64 and resulted in an enhanced user interface because the user could change things on the form during the pick/selection process. Disabling is another. What you are trying to do here is to make sure the user does not operate anything on the form during the time the task focus is supposed to be an AuotCAD picking/selecting task. When you do operate in modeless and a screen pick/selection is part of the taskflow then change the code so that none of the modeless form is active during that screen pick/selection. For example a form might have five command buttons and only one really requires a modeless operation. This might require in some instances for a form to change from modal to modeless and back again when the form task workflow needs to change to a modeless mode. Then make sure all form buttons can take on focus. Add the acFocusCntl to all forms regardless as to whether or not they are used in modeless mode. Often the necessary change sacrifices usability for function. In general you can minimize most of the problems by changing the user interface structure. As for the other items I can relate experience from porting over many pre-64 VBA projects. I am looking at your post hoping to find a solution to the call rejected error which I cannot help you with. But it is very awkward.ĭoes any one have any solutions or good work-arounds for these problems? So, I added the following line:Īfter the initial form is hidden and before requesting the user input, and it seems to fix the problem. If you switch to another program then back to AutoCAD, it continues some of the time. At the user input, the crosshairs freeze. At one point, it shows a form then gets user input from the screen. I have some code that was written by someone else, so I am not very familiar with it. I get very strange results: some of the buttons on the form do not function and many times the crosshairs on the AutoCAD screen freeze.ģ. For a couple of commands, I use modeless forms.
![autocad 2010 64bit autocad 2010 64bit](https://i.gr-assets.com/images/S/compressed.photo.goodreads.com/hostedimages/1589519564i/29478702._SX540_.png)
However, if you click debug then press F5 to continue, it fails.Ģ. When it fails, if you click on debug, then step through that one line using F8, the code works fine. The sample code runs when the form loads and anytime you move the form. My real code is part of a much larger project and it fails no matter how you launch it. However, if you run it using F5 from the VBA editor, it fails most of the time.
![autocad 2010 64bit autocad 2010 64bit](https://thepcgo.com/wp-content/uploads/2019/10/Autodesk-AutoCAD-2010-free-download-thepcgo.jpg)
If you load the file then run the "TEST" function from the AutoCAD macros list, it seems to work most of the time. I have a DVB file that illustrates the problem, but this system won't let me attach a DVB file.
![autocad 2010 64bit autocad 2010 64bit](https://fasrnote722.weebly.com/uploads/1/2/4/0/124067221/761370199.png)
In WinXP32 the code works 100% of the time. The problem is not the "i =" part and it doesn't matter what AutoCAD variable you try to get. Very often (but not always), I get an error "Automation error, Call was rejected by callee." when it hits this line: The three main issues that are causing problems right now are:ġ.
![autocad 2010 64bit autocad 2010 64bit](http://img.youtube.com/vi/YGEHgWK0EBc/0.jpg)
I have several problems with code that works perfectly well in AutoCAD 2010 running on WinXP32.
#AUTOCAD 2010 64BIT WINDOWS#
I have been running AutoCAD 2010 with the VBA enabler, in order to continue to use our AutoCAD 2007 code which I recently updated to run in AutoCAD 2010.Īpparently, WinXP64 does some things differently from Windows XP 32-bit. Our office is moving to Windows XP 64-bit machines.