http://bugs.winehq.org/show_bug.cgi?id=14830
Summary: Autocad 2005 : many OLE/Activex problems Product: Wine Version: CVS/GIT Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 AssignedTo: wine-bugs@winehq.org ReportedBy: max@veneto.com
Well, I don't know if that's really a bug or many bugs at once... if somebody can be more precise, please correct me.
1) Lisp command (vl-vbaload "vba-project-name") don't work. It tells "Automation Error. Problem in loading DVB file" Manual (non autolisp) command line "-vbaload" works as expected. Notice that on windows machine both works. No error/messages shown on console upon command launch.
2) VBA has problem on autocad objects declarations/usage. For example, if I use : Dim myDoc as Object it does work (but of course you can't inspect object easily) If I use Dim myDoc as AcadDocument it DOESN'T work, it tells something like "not yet supported". Notice that on a windows machine both works ok.
3) Upon using some command that invokes OLE automation, CPU usage for autocad (and wineserver) rises to about 50% for each of them (total about 98%). I've got a 2 core machine, so it's still usable, but slows down everything. Stopping the command don't help; closing ALL of active drawings does help, CPU goes to 2%, but on new drawing/open drawing CPU still raise to 100%, even with no further OLE commands.
I guess all 3 above are related to each one, so I put on a single bug report. Well, first 3 are by sure OLE related. Next one I don't know...
4) Opening Visual Lisp Ide from inside autocad don't allow to switch back to autocad again without closing it. Well, you can select Autocad window, but it's irresponsive. Upon closing ide, autocad becomes responsive again. More, if you open visual lisp ide, then help system from it, then close visual lisp ide, if you try to close help system autocad crashes. That don't happens if you close help BEFORE closing visual lisp ide.
Max
http://bugs.winehq.org/show_bug.cgi?id=14830
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from James Hawkins truiken@gmail.com 2008-08-11 10:46:37 --- Invalid. One bug per bug report.
http://bugs.winehq.org/show_bug.cgi?id=14830
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from James Hawkins truiken@gmail.com 2008-08-11 10:46:47 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=14830
--- Comment #3 from max@veneto.com 2008-08-11 10:50:40 --- (In reply to comment #1)
Invalid. One bug per bug report.
IMHO, besides (MAYBE) point 4, that's ONE bug in many forms. If you prefere that I clobber bugzilla with 5 apparently different bug reports, you're wellcome.....
Max
http://bugs.winehq.org/show_bug.cgi?id=14830
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|CVS/GIT |unspecified
http://bugs.winehq.org/show_bug.cgi?id=14830
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |Other
--- Comment #4 from Austin English austinenglish@gmail.com 2012-02-23 15:23:01 CST --- Removing deprecated 'All' Platform.