IntelliDoor Garage - Revision history

NelsonJenkins at 23:57, 16 September 2019

2019-09-16T23:57:59Z

NelsonJenkins at 23:43, 16 September 2019

2019-09-16T23:43:13Z

NelsonJenkins: /* Known Issues */

2019-09-16T23:39:06Z

‎Known Issues

NelsonJenkins at 23:38, 16 September 2019

2019-09-16T23:38:28Z

imported>NelsonJenkins at 21:29, 10 February 2015

2015-02-10T21:29:49Z

imported>NelsonJenkins at 20:44, 10 February 2015

2015-02-10T20:44:00Z

imported>NelsonJenkins at 06:39, 6 June 2014

2014-06-06T06:39:59Z

imported>NelsonJenkins at 19:03, 16 April 2014

2014-04-16T19:03:15Z

imported>NelsonJenkins at 05:47, 24 March 2013

2013-03-24T05:47:23Z

imported>NelsonJenkins at 05:03, 24 March 2013

2013-03-24T05:03:04Z

@@ Line 64: / Line 64: @@
 ==Known Issues==
-As of September 2019, a change to the physics engine broke the method the IntelliDoor Garage uses to hide itself. The door will retain its physics shape above where it has raised into until manually edited. [https://jira.secondlife.com/browse/BUG-227636 This has been reported on the JIRA.] A workaround is pending for this issue.
+As of September 2019, a change to the physics engine broke the method the IntelliDoor Garage uses to hide itself. The door will retain its physics shape above where it has raised into until manually edited. [https://jira.secondlife.com/browse/BUG-227636 This has been reported on the JIRA.] A workaround is available in v3.1.2.
 ==Updates & Release Notes==
 You can update your IntelliDoor Garage by rezzing the update box.
 * v3.1
 ** New button model

@@ Line 64: / Line 64: @@
 ==Known Issues==
-As of September 2019, a change to the physics engine broke the method the IntelliDoor Garage uses to hide itself. The door will retain its physics shape above where it has raised into until manually edited. [https://jira.secondlife.com/browse/BUG-227636 This has been reported on the JIRA.] There is nothing we can do to fix this bug in the meantime.
+As of September 2019, a change to the physics engine broke the method the IntelliDoor Garage uses to hide itself. The door will retain its physics shape above where it has raised into until manually edited. [https://jira.secondlife.com/browse/BUG-227636 This has been reported on the JIRA.] A workaround is pending for this issue.
 ==Updates & Release Notes==

@@ Line 64: / Line 64: @@
 ==Known Issues==
-As of September 2019, a change to the physics engine broke the method the IntelliDoor Garage uses to hide itself. [https://jira.secondlife.com/browse/BUG-227636 This has been reported on the JIRA.] There is nothing we can do to fix this bug in the meantime.
+As of September 2019, a change to the physics engine broke the method the IntelliDoor Garage uses to hide itself. The door will retain its physics shape above where it has raised into until manually edited. [https://jira.secondlife.com/browse/BUG-227636 This has been reported on the JIRA.] There is nothing we can do to fix this bug in the meantime.
 ==Updates & Release Notes==

@@ Line 62: / Line 62: @@
 * '''[BBID][DoorID]&&stop''' - Stops the door, if it is moving.
 The IntelliDoor Garage ''does not'' accept the &&lock and &&unlock commands, and it is the only component which accepts the &&stop command.
 ==Updates & Release Notes==

@@ Line 33: / Line 33: @@
 * WHITELIST: The list of people that will always be able to click the door to operate it. This does not affect buttons and controllers. Separate with commas. '''NOTE: Whitelist names are ''usernames'' (nelson.jenkins, newbie), not ''legacy names'' (Nelson Jenkins, Newbie Resident).''' If you have more than 10 names, please read "Extended Whitelist" below.
 * GSS: If you are using a Global Security Server, enter its name in this field. The IntelliDoor GSS provides a "master" whitelist and blacklist for doors that subscribe to it (for example, if you have a group of doors that you want a list of people to control).
 ===Extended Whitelist===
@@ Line 63: / Line 65: @@
 ==Updates & Release Notes==
 You can update your IntelliDoor Garage by rezzing the update box.
 * v3.0
 ** Implemented Buildbox integration

@@ Line 44: / Line 44: @@
 * WHITELIST: This is the same as the door's whitelist, but again, only affects the button.
 * GSS: This is the same as the door's GSS name, but only affects the button.
 ==API==
@@ Line 103: / Line 108: @@
 * v1.0
 ** Primary public release.
 ==History==

@@ Line 31: / Line 31: @@
 * ACCESS: This is the base access setting. If the door is locked (which it is by default), this group of people can always access it anyway by clicking on it. Can be "Everyone", "Group", or "Owner". (If you put "Group" here, the door's group will be able to click the door to use it, but they won't be able to use any buttons or controllers unless you also set them to "Group".)
 * AUTOCLOSE: If you don't want autoclose, leave this as 0. Otherwise, it is the number of seconds the door waits until closing automatically. For more info, read "AUTOCLOSE" above.
-* WHITELIST: The list of people that will always be able to click the door to operate it. This does not affect buttons and controllers. Separate with commas.
+* WHITELIST: The list of people that will always be able to click the door to operate it. This does not affect buttons and controllers. Separate with commas. '''NOTE: Whitelist names are ''usernames'' (nelson.jenkins, newbie), not ''legacy names'' (Nelson Jenkins, Newbie Resident).''' If you have more than 10 names, please read "Extended Whitelist" below.
 * GSS: If you are using a Global Security Server, enter its name in this field. The IntelliDoor GSS provides a "master" whitelist and blacklist for doors that subscribe to it (for example, if you have a group of doors that you want a list of people to control).
-NOTE ON NAMES: The IntelliDoor system v2.1 and above uses usernames (e.g. "nelson.jenkins" or "newusername") - NOT old-style names ("Nelson Jenkins" or "newusername Resident") and NOT display names ("Nelson the Magnificent" or "New User"). Separate values with commas (nelson.jenkins, newusername, etc.). Entries here are not case-sensitive.
 ==Button Config Values==

@@ Line 14: / Line 14: @@
 ==Setup==
 # Rez the door and resize it to the frame. Try not to change the thickness of the door.
-# Rez a Button if you want one and position it. It can be retextured and resized if necessary, but we recommend leaving it as it is. You don't need a Button; clicking the door itself will operate it as well.
+# Rez a Button if you want one and position it. It can be resized if necessary, but we recommend leaving it as it is. You don't need a Button; clicking the door itself will operate it as well.
 # Open the _config notecard in the door, sensor, and button. For more information on the _config values, read the sections labeled "CONFIG VALUES". For now, change the door ID and make sure it is the same in all notecards.
 # Test the door by clicking the up button (or if you don't have a controller, just the door itself). If you have autoclose enabled, stand under the door and see if it closes (it shouldn't).

@@ Line 20: / Line 20: @@
 ==Textures==
-The door textures are now included in the package; simply drag them onto each side of the door to set the door's texture. The textures are prefixed with "Tex-IDGarage".
+The door textures are now included in the package; simply drag them onto each side of the door to set the door's texture. The textures are prefixed with "Tex-IDGarage". You can also use your own textures.
 ==Autoclose==