Documentation

Misc Bugs and things that may change.

First of all, if you get an error in the MacBird card that says X hasn't been defined this is a bug in the MacBird runtime that I doubt will be fixed soon. Just wait a second and then click the button again.

Some early Q&A:

Why do you use a seperate outline for the site structure, why not just use an ODB outline?

Well this part of the suite was done long before the ODB outline was a Frontier feature (and I've been using Frontier 5 since version d3). The new ODB outlines are very cool, and I may ditch the siteStructure outine except that it still has some advantages:

• If you delete an item from the outline, RingMaster can know that you deleted it, and still get enough info about the object to delete it from the server. Similar advantages apply for moving and renaming.

• The current version is very simple and clean for those who don't want to be able to expand and object and see its properties

• You can copy and paste from the site outline view to the site structure view currently because both use the same refcon system to keep track of the objects.

• You can select multiple items from the current RingMaster outline and act on them as a selection, this would not be possible with ODB outlines unless table.getCursor is modified so that it could return a list (a cool thing that I hope might happen for 5.0)

Why are all types of filters all put in a single 'filters' resource type?

I've gone back and forth on this and am still not sure this is the best thing. I did this for two reasons, to prevent the 'edit resources' menu from being swamped with filter types, and to allow for a more flexible use of filters by custom types. This way a custom type can define an event that a filter is called, and new filters can be created without needing to create a new filter resource type.

Table of Contents -- Prev --