Topic: How to run a lisp when close file ?

[kruuger]

What is to prevent the user from opening the drawing, and doing nothing for several hours and saving the drawing (effectively producing nothing). Won't their time still be logged?

Perhaps it would be prudent to incorporate a Sysvar Reactor that monitors Cmdactive, and when commands are not active, the timer is prgramatically stopped. Just a thought, as this thread somewhat reminds me an AUGI thread about CadTempo.

program is not used for monitoring work. purpose is to easy track person who modify the drawing.
we can get him and point out that something was wrong in drawing.
kruuger

[BlackBox]

program is not used for monitoring work. purpose is to easy track person who modify the drawing.
kruuger

I would argue that one is dependent on the other.

Without the context of knowing what modification(s) have occurred, one cannot possibly know which user(s) is(are) responsible.

Again, were a user to open a drawing, draw a line, delete the line just drawn, then save the drawing (effectively doing nothing)... That user would be logged.

[dgorsman]

A long time ago, I was in the same boat.  The piping lead asked me to print off a stack of drawings.  A few days later he comes back and asks "Why was this changed?"  "This shouldn't look like this" and so on, pointing to my name on an automated datestamp on the prints.  I had to repeated point out to him that the log (datestamp on drawing in this case) was only changed when the drawing was printed and I had *never* worked on the drawings.

The moral of the story: tracking logs don't always say what you think they are saying.

[kruuger]

program is not used for monitoring work. purpose is to easy track person who modify the drawing.
kruuger

I would argue that one is dependent on the other.

Without the context of knowing what modification(s) have occurred, one cannot possibly know which user(s) is(are) responsible.

Again, were a user to open a drawing, draw a line, delete the line just drawn, then save the drawing (effectively doing nothing)... That user would be logged.

A long time ago, I was in the same boat.  The piping lead asked me to print off a stack of drawings.  A few days later he comes back and asks "Why was this changed?"  "This shouldn't look like this" and so on, pointing to my name on an automated datestamp on the prints.  I had to repeated point out to him that the log (datestamp on drawing in this case) was only changed when the drawing was printed and I had *never* worked on the drawings.

The moral of the story: tracking logs don't always say what you think they are saying.

it's a better have more people on log list rather then none.
in my case log per day is good enough to find someone who made a bad mistake.
if someone is working in company where every move are tracked, then my compassion.
kruuger

[irneb]

Again, were a user to open a drawing, draw a line, delete the line just drawn, then save the drawing (effectively doing nothing)... That user would be logged.

I can't remember, does the SysVar reactor catch changes in the CmdActive sysvar? If so perhaps just save a running total of how many commands the user's used during his/her editing time. E.g. if they've had the DWG open for several hours, but only 10 commands were issued, they probably only had it open as a reference to another drawing (i.e. for something like Copy-n-Paste).

Another alternative could be to count the number of objects inside the drawing at open, and then save the difference at Save. That way you can see how much extra work / erases were made.

There's no perfect answer, especially since any user could have multiple DWGs open at the same time. But it's near impossible to work on more than 1 at any one instant. Also what about those using RefEdit? They're inside one DWG, but actually modifying another.

[BlackBox]

There's no perfect answer

This is the most accurate phrase yet. 

I can't remember, does the SysVar reactor catch changes in the CmdActive sysvar?

I'd have to experiment myself, now that you mention it.

Another alternative could be to count the number of objects inside the drawing at open, and then save the difference at Save. That way you can see how much extra work / erases were made.

There's no perfect answer, especially since any user could have multiple DWGs open at the same time. But it's near impossible to work on more than 1 at any one instant. Also what about those using RefEdit? They're inside one DWG, but actually modifying another.

Giving this a bit more thought, perhaps to simplify the who-dun-it concept _and_ to provide clear identification of what modifications have been made, a programmatic file copy at Save would prove useful. Then modify the dialog to present the user with the log list, and upon selection (or checkbox, etc.) the associated drawing (the one logged to that event/date/user) is programmatically referenced into the active drawing for 'review'.

While I do not keep track of who-dun-what, I do keep what I term 'void' copies of our drawings, which are made via LISP routine using a command (aptly named c:VOID ) to programmatically copy the drawing to a predetermined folder within our project's directory structure, adding the date to the file name. This can then be referenced to easily identify what changes were made, etc.

Admittedly, this can cause storage issues for those without the benefit of having massive amounts of available server space, etc.. This is just my workflow, and is certainly not perfect, nor would it apply to all. Just thought I'd share.

[HasanCAD]

How to reset the LOG?
In some cased ( specially in details drawings) we copy and rename an old file to use in a new projects.
So we need to reset the file history.

[HasanCAD]

The monitoring of the user activity is the response of the senior/team leader as well.
for monitoring the user activity we can use LEE's lisplog routine

[kruuger]

How to reset the LOG?
In some cased ( specially in details drawings) we copy and rename an old file to use in a new projects.
So we need to reset the file history.

Code - Auto/Visual Lisp: [Select]

(defun c:DLOG ()
  (if (cd:DCT_GetDict (namedobjdict) "ADS_HISTORY")
    (progn
      (cd:DCT_RemoveDict (namedobjdict) "ADS_HISTORY")
      (princ "\nLog history was deleted")
    )
    (princ "\nNo log history in drawing")
  )
  (princ)
)
; =========================================================================================== ;
; Pobiera slownik / Gets a dictionary                                                         ;
;  Root [ENAME/nil] - ENAME = slownik "rodzic" / "parent" dictionary                          ;
;                     nil   = (namedobjdict) jako "rodzic" / (namedobjdict) as "parent"       ;
;  Name [STR]       - nazwa slownika / name of the dictionary                                 ;
; ------------------------------------------------------------------------------------------- ;
; (cd:DCT_GetDict (namedobjdict) "NAZWA")                                                     ;
; =========================================================================================== ;
(defun cd:DCT_GetDict (Root Name)
  (cdr (assoc -1 (dictsearch (if (not Root) (namedobjdict) Root) Name)))
)
; =========================================================================================== ;
; Usuwa slownik / Removes the dictionary                                                      ;
;  Root [ENAME/nil] - ENAME = slownik "rodzic" / "parent" dictionary                          ;
;                     nil   = (namedobjdict) jako "rodzic" / (namedobjdict) as "parent"       ;
;  Name [STR]       - nazwa slownika / name of the dictionary                                 ;
; ------------------------------------------------------------------------------------------- ;
; (cd:DCT_RemoveDict (namedobjdict) "NAZWA")                                                  ;
; =========================================================================================== ;
(defun cd:DCT_RemoveDict (Root Name)
  (dictremove (if (not Root) (namedobjdict) Root) Name)
)
(princ "\n>> Type DLOG to invoke <<")
(princ)

?
k.

[HasanCAD]

Thanks Kruuger for the awesome lisp I'll study to learn from.

[HasanCAD]

...
rewritten AUTOR.LSP to LOG.LSP (new shortcut LOG)
...
kruuger

How did you do the yellow circle which moved with the mouse?

[Coder]

...
rewritten AUTOR.LSP to LOG.LSP (new shortcut LOG)
...
kruuger

How did you do the yellow circle which moved with the mouse?

It is an option in the video recorder , nothing is related to lisp .

[jbuzbee]

This needs an OpenDCL interface: just sayen . . .