pjanssen / outliner Goto Github PK

What steps will reproduce the problem?

1. Open the Outliner
2. Open the Trackview
3. Select an object with keys (through the Outliner?)
4. Try deleting one or more keys.

What is the expected output? What do you see instead?
The keys should be deleted, but they aren't.

What version of the product are you using? On what operating system?
2.0.96

Installer might fail if kbd and cuifiles are located in programfiles and cannot be written to.
Should use getFileSecurityInfo function to check, and possibly save a copy to the userdir.

What steps will reproduce the problem?

1. Enter isolate selection mode with the Outliner opened
2. Close isolate selection mode.

What is the expected output? What do you see instead?
Should not affect Outliner. Instead, it crashes.

What version of the product are you using? On what operating system?
2.0.96

Please provide any additional information below.
See crash report #20110907_533, #20110929_556, etc.

What steps will reproduce the problem?

1. Create one or more objects.
2. Select one or more objects.
3. Right-click on empty space.

What is the expected output? What do you see instead?
The selection is cleared. It might be nicer for a workflow in the layer mode to keep the selection when right-clicking.

When creating a new layer in the Outliner it should be set to be active automatically (optional?)

What steps will reproduce the problem?

1. Open the Outliner.
2. Create a teapot.
3. Add it to a new layer.
4. Detach an element from the teapot object.

What is the expected output? What do you see instead?
The detached object initially appears on the active layer (0). When the Outliner is reopened, it appears on the newly created layer.

What version of the product are you using?
2.0.96

What steps will reproduce the problem?

1. Create an object
2. In the material mode, select its material (unassigned by default).
3. Right click and click "select childnodes".
4. Go to layer mode
5. Right click to create a new layer, nothing happens (it deselect objects if selected) (which is wrong!)
6. Right click again and "create a new layer"

What is the expected output? What do you see instead?
A single new layer should be created and the name should be editable. Instead two layers are created, and a seemingly random layer's name is edited.

Colors were reintroduced to the dark UI color scheme in 3dsmax 2012. The Outliner should try to conform to that.

What steps will reproduce the problem?

1. Create a new scene with two layers called 'A' and 'B'.
2. Nest layer B under A.
3. Save the scene as step3.max.
4. Create an object in layer B.
5. Save the scene as step5.max.
6. Load step3.max.
7. Merge the object created in step 4 in step5.max.

What is the expected output? What do you see instead?
Merging should work fine, instead 3dsmax crashes.

Please use labels and text to provide additional information.
Thanks to duke2 @ scriptspot for finding the steps to reproduce the issue.

Some users report the auto update not working, so it might be worthwhile to go through the code and check it.

Runtime error: dotNet runtime exception: The process cannot access the file 'C:\Users.....\2012 - 64bit\enu\UI\ame-dark.kbd' because it is being used by another process.

What steps will reproduce the problem?

1. Create a scene with a single object.
2. Save the scene.
3. Create a new scene.
4. Use xref-scene to xref the scene created at step 1.
5. Open the Outliner and switch to layer and material mode.

What is the expected output? What do you see instead?
The objects from the xref-ed scene should not be visible in the Outliner.

What steps will reproduce the problem?

1. Open the Outliner.
2. Close it.
3. Open it again.

What is the expected output? What do you see instead?
Window should be opened in the same position. Instead, it seems to shift 5pixels down, and 5 pixels to the right.

Please use labels and text to provide additional information.
Possibly only in win7?
The shift itself seems to occur after cui.unregisterDialogBar when closing? Perhaps storing the position after this command causes the issue?

Add a filter option that filters out group heads and members.

What steps will reproduce the problem?

1. Create a new layer.
2. Select the default layer (0).
3. Click the + button next to the newly created layer.

What is the expected output? What do you see instead?
The button should be disabled, or at least the operation should not be carried out when clicked. Instead, the default layer is nested under the new layer and cannot be removed from it.

What steps will reproduce the problem?

1. Create a scene with 3 teapots.
2. Put tp1 on layer1, tp2 on layer 2, tp3 stays on layer0.
3. Nest layer 2 inside layer1.
4. Xref tp1 and 2 in a new scene.

What is the expected output? What do you see instead?
Xref should work without problems. Instead, you get a cyclic redundancy error.

What version of the product are you using? On what operating system?
2.0.96

Please provide any additional information below.
If the error does not occur, just change something in the xref'd scene and reload in the master file and then the error applies.

Add a feature allowing the user to tag/mark an object or layer with a color to easily identify it. Like color tagging of files in mac osx.
Idea: use selection sets (e.g. outliner_red, outliner_green)

Create option checkbox for edit new layer name.

What steps will reproduce the problem?

1. Select a layer.
2. Right-click it and choose "Create new layer" in the context-menu.

What is the expected output? What do you see instead?
It would be more intuitive if the created layer was automatically nested under the right-clicked layer. Instead it is created as a 'root layer'.

What steps will reproduce the problem?

1. Create a CAT rig.
2. Select a bone.
3. Add to selection by holding ctrl shift and clicking another bone.

What is the expected output? What do you see instead?
Second bone should be added to selection. But it crashes.

What version of the product are you using? On what operating system?
2.0.96

Please provide any additional information below.
See crash report #20110922_544

From polycount forum post by Noors:
http://www.polycount.com/forum/showpost.php?p=1480085&postcount=277

http://dl.dropbox.com/u/13762052/polycount/outliner/noors_outliner_01.png

not wanted :
In the first example, parenting box to cone expend the sphere hierarchy.
In the second, duplicate the sphere expend the sphere hierarchy.

Version 2.1

1. Create two geometry objects
2. Attach one to the other

Result: Outliner crashes (caused by nodeLayerChanged nodeevent).

What steps will reproduce the problem?

1. Create 2 boxes.
2. Link box 2 to box 1.
3. Convert box 2 to editable poly.
4. Attach box 1 to box 2.

What is the expected output? What do you see instead?
Only box 2 should be visible in the Outliner. Instead, both disappear.

What steps will reproduce the problem?

1. Create a CAT RIG
2. Shift-drag to duplicate it. (or Ctrl+V)

What is the expected output? What do you see instead?
Outliner crashes.

What version of the product are you using? On what operating system?
2.0.95

Please provide any additional information below.
Crash report #20110126_354

What steps will reproduce the problem?

1. Install a version of the Outliner that is not the latest version.
2. Uncheck "skip trial versions"
3. Check for updates

What is the expected output? What do you see instead?
The changelog includes beta version changes. It should ideally only include changes from the currently installed version up to the version to be installed.

What steps will reproduce the problem?

1. Create a vray material.
2. Open the Outliner
3. Switch to material mode.
4. Select the created material.

What is the expected output? What do you see instead?
Expected to select the material as every other. Instead, Outliner crashes.

What version of the product are you using? On what operating system?
2.0.96

Please provide any additional information below.
See crash report #20110624_488

Version 2.1.1:

1. Open the Outliner in material mode.
2. Create a geometry object.
3. Assign it to a new material.
4. Rename the material in the material editor.

In the installer dialog, "install" should be replaced by "update", or better, the installation should be started automatically when updating from the Outliner.

Include an option/feature to sync the turning off of lights with hiding/unhiding layers.

1. Create an object
2. Switch to layer mode
3. Turn filter on, don't show hidden objects
4. Hide the layer.

From comment on scriptspot:

1. when hide layer by clicking on its icon - everything is fine - all the object's icons are dimmed. but when click on layer's icon again to unhide - only one object in layer is indicating as visible
2. when click to unhide layer - object list (plus in rectangle) displays only after Outliner restart

both issues ONLY when hidden objects are disabled in filter

-Run 2 instances with the Outliner started
-Install an update in one of the instances, this will prompt you to restart only this instance.
-Run the Outliner again in the other instance. This still has the old script loaded, and doesn't know about having to restart. So it is going to look for files which are no longer there, causing a crash.

Todo: adjust restart message.

What steps will reproduce the problem?

1. Open the Outliner
2. In the option's dialog, hide the search bar.
3. Close and reopen the outliner.
4. Try to select the first layer or object.

What is the expected output? What do you see instead?
Should work without problems. Instead, the tree doesn't seem to get focus.

What steps will reproduce the problem?

1. Create a target camera or light.
2. Open the Outliner.
3. Enable the filters with all types being shown.
4. Toggle the geometry filter.
5. Toggle the helper filter.

What is the expected output? What do you see instead?
Changing the geometry filter setting should not affect the target object, but it does. Changing the helper filter does not affect it, while it should.

Cause:
The target objects are actually GeometryClass objects for some reason.

Investigate whether it's possible to make the sortmode and filter toolbars dockable.

What steps will reproduce the problem?

1. Install the Outliner.
2. Install the Workflow Tools.
3. Install the Outliner again.

What is the expected output? What do you see instead?
The Workflow Tools should not be affected. Instead, they are uninstalled.

What version of the product are you using? On what operating system?
2.0.96

What steps will reproduce the problem?

1. Search for "bone", doesn't return objects that begin with the word "bone".
2. Search for "Bone*Hip", doesn't return an object named "Bone L Hip" or "Bone R Hip".

What steps will reproduce the problem?

1. Start 3dsmax 2012.
2. Open the Outliner.
3. Dock the window to the left or right.
4. Try undocking it by dragging.

What is the expected output? What do you see instead?
The Outliner window should be undocked, but it doesn't work.

What steps will reproduce the problem?

1. Open the Outliner
2. Open the options dialog
3. Set both the search bar and menu buttons location to "Top"

What is the expected output? What do you see instead?
Result: Buttons overlap.

What version of the product are you using? On what operating system?
2.1 beta3

What steps will reproduce the problem?

1. Create an object.
2. Clear its name outside the Outliner.

What is the expected output? What do you see instead?
The object is difficult to select, and looks weird. Suggest using a constant "-unnamed object-" as DisplayName.

What steps will reproduce the problem?

1. Create a scene with some materials.
2. Open the Outliner.
3. Switch to material mode.

What is the expected output? What do you see instead?
Only "unassigned" shows up.

What steps will reproduce the problem?

1. Somehow end up in the situation where there is a node in the Outliner that has no scene representation.
2. Delete it through the Outliner.

What is the expected output? What do you see instead?
Node should be deleted from the Outliner. Instead it crashes.

What version of the product are you using? On what operating system?
2.0.96

Please provide any additional information below.
See crash reports #20110902_529, #20110814_520, #20110810_518, etc.

What steps will reproduce the problem?

1. Create an object.
2. In material mode, expand the "unassigned" material.
3. Switch to layer or hierarchy mode.
4. Switch back to material mode.

What is the expected output? What do you see instead?
Expected to see the unassigned material still expanded; it is collapsed.

What steps will reproduce the problem?

1. Start 3dsmax 2011 or above
2. Open the Outliner
3. Dock it on the left or right

What is the expected output? What do you see instead?
In 3dsmax 2008-2010 the window is resized to the maximum height. In 2011+ it stays the same height as the floating window.

What steps will reproduce the problem?

1. Create an object.
2. Double-click in the outliner to begin renaming/labeledit.
3. Remove the text and press enter.
4. Repeat 3 a couple of times.

What is the expected output? What do you see instead?
The edit function should never accept the empty input. A dotnet exception is thrown and not caught.

Selected item background box smaller than text when not using Visual Styles.

In 3dsmax2012 the main UI buttons appear to use the images for the light color scheme even though the dark (default) color scheme is applied.

http://forums.cgsociety.org/showpost.php?p=7158747&postcount=337

"When I use joe gunns script called "Cache & Bake", during the bake process, the outliner swipes clean and don't list anything anymore, I have not inspected what really makes it do that, but it's a heads up."

What steps will reproduce the problem?

1. Create a pfsource object.
2. Move the time slider to ~15frames so the particles are spawned.
3. In the outliner, use the context-menu to 'Add selection to new layer'.
4. Hide the newly created layer.
5. Hide the original layer.

What is the expected output? What do you see instead?
Step 4 should hide the pfsource AND the spawned particles. Step 5 should have no effect on the particles. Instead, step 4 hides only the pfsource, not the particles. Step 5 hides the particles.

Please use labels and text to provide additional information.
Also works when 'manually' creating a new layer and dragging/dropping the pfsource into it.

To avoid issues with people accidentally unpacking the mzp and trying to install the Outliner from there, a readme text file should be added to the root of the package.

The sortmode and filter toolbar are positioned too high when the main buttons are set to be at the top of the screen.