Plotting and printing from Medusa

  • Direct plotting from MedusaNG running on WIndowsNT and UNIXUpdated 18th March 99

  • Thing that I still don't like with the plotting/printing facilities

    Background and description

    Plotting from Medusa has always been a source of difficulty. The developers have tried a number of different approaches to provide quality output from this excellent drafting program. I feel that a lot of the complexity of the resulting systems has been due to the needs of the larger customers dictating the requirements. These requirements have favoured the dedicated print room where all plotting is undertaken and the resulting plots are stored as masters for printing. Most of the modern CAD systems don't work this way and here at CCL we no longer have a dedicated print room and expect users to print to local printers.

    Since the introduction of Version 12 we have tried to run the plotting system in cyclic mode rather than collecting the files into a queue and plotting in batches. This has proved to be less reliable than we hoped and the plotting process dies unexpectedly every couple of days. It can take several hours before this is spotted and action taken. Altogether too much of a faff!

    With the introduction of MedusaNG running on NT I tried to get the various PC to send their files to the UNIX plot queue using the remote plotting facilities. I never got this to work. A combination of poor manuals, over-complex software and lack of knowledge probably. This meant that I had to run a print queue on each of the PCs and the printed output was really poor quality - grey scale lines, low resolution and too time consuming to use - every PC user of medusa needed to become and expert in managing queues!

    Early in 1997 with help from Graham Snudden of CVSS and later from Alan Liddle of Root Solutions I put in place a direct plotting/printing system for both our PCs and our UNIX workstations. This system didn't replace the old Queue plotting system but it did mean that I no longer had to struggle to keep it running in cyclic mode.

    The benefits I have seen from doing this are as follows:-

    I do still have the traditional queue based plotting application available on the UNIX machines and we do use it for the times when we need to plot significant numbers of drawings or any of the other things that are only possible from the rich tool pallet of the Medusa plotting application. The following is a description of the files used and how it is setup on CCL's Medusa installation.

    Requirements

  • The macro(s) should be common for the UNIX and the WindowsNT versions
  • The files used should be centrally located and administered (i.e. no files on users machines)
  • The menus should be simple and intuative
  • Print quality should be as good or better than alternative methods
  • Description

    I added a menu to the Medusa menu bar


    medmenu1.gif

    I added a menu item into the pulldown menu. This is not quite straight forward as I needed to add the following code to the "menu_bar.uid" file located in the CCL product "/ui/med2d/main" folder.
    quick_print.class:ui_pulldown_menu
        .parent:menu_file
        .label:"print"
        .browse_text:"print the sheet"

    print_a0.class:ui_bacis1_button
       .label:"print on A0 printer"
        .parent:quick_print
        .browse_text:ccl_file$A0plot
        .activate:"macro @vmac$@vmid$epa0plot.mac"
        .icon:"a0plot"

    print_a3.class:ui_bacis1_button
        .label:"print on A3 printer"
        .parent:quick_print
        .browse_text:ccl_file$A3plot
        .activate:"macro @vmac$@vmid$epa3plot.mac"
        .icon:"a3plot"

    print_a4.class:ui_bacis1_button
        .label:"print on A4 printer"
        .parent:quick_print
        .browse_text:ccl_file$A4plot
        .activate:"macro @vmac$@vmid$epa4plot.mac"
       .icon:"a4plot"

    In fact I had to have the complete menubar.uid file copied from the medusa system into the CCL product in order to put the custom menu in the place shown. If I just had the new stuff shown above, Medusa put it at the bottom of the menu (after the quit).
    I could find no other way to control this except by having the complete uid file in the product and thus overwriting the system one on startup.

    This is the one I used in NG version 3.1
    Menu_bar.uid

    and
    This is the one I used in NG version 3.2
    Menu_bar.uid


    If you don't have a custom product set up click
    here for information on how to make direct printing work.


    The real work is done by a single macro for each of the menu items, 3 macros in total.

    Each of these macros writes a unique macro for each sheet to be plotted

    The plot is the current window for all sizes and doesn't plot the construction layers 19 to 30

    The three macros are:-
    a0plot.mac
    a3plot.mac
    a4plot.mac
    These are saved in our CCL product at "/med2d/m2d/macro/

    You can find out where this is set to on your system from Bacis1 with the following command:0
    qvar mac$
    If this is not set then it must be set to point to the macro location.
    we set this up in the medstart.mac file in the custom product


    Wouldn't it be nice if.....

    There are a number of things about the plotting and printing that could be improved:-


    I would like better control of the element colours at plot time. If I have set a layer to be a unique colour I would like that layer and all the elements on ti to be the chosen colour.

    I think that it is a waste of time having to select all the parameters like paper size and orientation each time a sheet is submitted to the WindowsNT plotting process. Could there be a setting that just uses that last selected parameters (like Word and Excel etc)?


    Setting direct printing up without a custom product

    If you don't have a custom product set up you will need to modify the "menu_bar.uid" file in the base system.
    So rename
    medusa\med2d\ui\med2d\main\menu_bar.uid
    to
    medusa\med2d\ui\med2d\main\menu_bar.ori
    copy the text in the file given here
    Version 3.2 or Version 3.1 into a new menu_bar.uid file in the same directory as the original version.
    Copy the macros into a directory where you put other bacis1 macros (if you havn't got a product it will be in your project probably in "project"\m2d\macro.
    make sure you have the variable mac$ set to point at the location of the macros.
    Restart Medusa and the facility should be available. - I can help a bit by Email if you get stuck (address below)
    - Last modified: March 18th 1999 -

    Go back to Mike Nelsons CAD Page

    This site is created and maintained by Mike Nelson for his own pleasure

    © 1997 mike.nelson@camcon.co.uk