Timeline for Programmatically block Toolbar choosing in ArcMap 10.1
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2014 at 7:14 | vote | accept | shika-kun | ||
| Feb 10, 2014 at 18:06 | answer | added | Hornbydd | timeline score: 1 | |
| Feb 10, 2014 at 15:35 | comment | added | shika-kun | Well, it is to be modified according to login information. We have an extension which asks for login/password and choose functionality according to the users privileges. We have ArcEngine application too as an alternative but tender contract tells us to prepare this kind of staff. | |
| Feb 10, 2014 at 15:23 | comment | added | Hornbydd | Why would you want to stop users from accessing the other tool bars, seems a bit draconian? If a user is even aware they can access tool bars via that route it would suggest to me that they are a "power user" and would not want to be locked out of the other useful tools. If you want to limit what they can use then maybe you should be developing an Engine standalone application rather than reducing functionality in ArcMap? | |
| Feb 10, 2014 at 13:01 | history | edited | shika-kun | CC BY-SA 3.0 |
added 2 characters in body
|
| Feb 10, 2014 at 12:09 | history | edited | Chad Cooper | CC BY-SA 3.0 |
code formatting
|
| Feb 10, 2014 at 11:57 | review | First posts | |||
| Feb 10, 2014 at 12:09 | |||||
| Feb 10, 2014 at 11:50 | history | edited | shika-kun | CC BY-SA 3.0 |
edited body
|
| Feb 10, 2014 at 11:48 | history | edited | PolyGeo♦ |
edited tags
|
|
| Feb 10, 2014 at 11:40 | history | asked | shika-kun | CC BY-SA 3.0 |