2004-02-25 05:16 PM - last edited on 2023-05-23 05:29 PM by Rubia Torres
2004-02-25 07:00 PM
2004-02-25 07:46 PM
if GLOB_SCALE<=50 then !Large Scale: if deta goto 4000 !Draws detail if mark goto 3000 !Draws marker goto 2000 !Draws patch endifNote non-parameterized (Bad developer!) GLOB_SCALE, which just misses the 1:48 (not large, IMHO) scale of the 1/4" section where I'm having the problem. I'm not going to take the time to trace the gotos any further. Showing all fragments and moving on...
2004-02-25 08:08 PM
2004-04-07 11:50 PM
James wrote:James,
OK I got it better now.
It's not the fragments. It's the way BGArchiCAD handles the cache library.
I think.
When the patch is created, the server library gets the new part. When I edit the patch and save it, BGArchiCAD's cache library doesn't get updated, even though the project was resaved and reopened in BGArchiCAD. I have tried force quitting and reopening BGAC, it doesn't seem to help.
It seems the only time the BGAC cache LIB is updated is at the first BGAC launch of a PM session. In other words, you have to quit PM and relaunch it, then update the views in order for the LIB to update.
It's very hard to get a handle on what's actually happening. We need access to BGAC's library manager within PM. (Or at least a reload button.)
2004-04-08 01:59 AM
2004-04-08 06:25 PM
~/archiben wrote:
it's not a fix...
~/archiben wrote:Thanks for that Ben! I did learn a lot from your posts on the matter.
i've written numerous posts about using library caches, etc. to help library load times across a network for both archiCAD and BGarchiCAD
~/archiben wrote:I absolutely agree...
On a general note, I do think that the whole library process needs a complete overhaul:
2004-04-08 06:28 PM
~/archiben wrote:Sure. But it don't think most people think of themselves as two users, one using AC, one using BGAC. The idea is, I make a change in AC, save, then update and the changes appear. While they were developing this method, they clearly didn't consider that changes to the project often take the form of changes to libraries. Patches are an excellent example of this.
isn't this the same as any normal archiCAD session: if a teammate creates a library part, you wouldn't see or have access to it unless you manually reload your libraries?
Richard wrote:It's bad design (and marketing) to say something is automatic, and then add that you need to watch it like hawk to be on the safe side. Since PM is going to remain separate, the connection to AC needs to be rock solid.
It is a matter that will cause other manufacturers concern if seeking an ArchiCAD solution. BGArchiCAD has to be absolutely accurate, reliable and updatable....without workarounds
Richard wrote:20 minutes to spare! Could have had dessert. I had a great time with you guys. See you next time.
Did you make it to the airport on time after the ScoreBoard?