
| Key: |
SVC-2814
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
Kagehi Kohn
|
| Votes: |
2
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Any.
|
|
Issue Links:
|
Relates
|
|
|
|
This issue is related to by:
|
|
|
SVC-468 New Permission Request "Resize only"
|
|
|
|
|
|
SVC-301 Meta-issue: New LSL Functions
|
|
|
|
|
|
|
|
Not sure which category scripting goes in, so posting this in Misc. Right now, we have an issue with people making HUDs that simply do not work in "any" resolution than the one they made them in. This is imho, a pain in the backside. One option I already posted to is more generic, and involves having an "allow resize only" type option for items. However, it has occured to me that there is another solution. An object can, in principle, resize itself, *if* it knows what resolution your client is running it. Imho, this is a much more useful idea, since someone could have a script request the client area (i.e. what the viewable section of the screen is, not including menus and the bottom bar, then translate that pixel dimension to the correct "size" for a HUD. One then simply stretches the dimensions of their own HUD, through the script system, so that it "fits" the area on the screen that the original design was "intended" to fit into in the first place. Its a simple enough fix, and one that wouldn't require people making their items modifiable in any way, since its the prims themselves that are "resizing" themselves, not the purchaser.
|
|
Description
|
Not sure which category scripting goes in, so posting this in Misc. Right now, we have an issue with people making HUDs that simply do not work in "any" resolution than the one they made them in. This is imho, a pain in the backside. One option I already posted to is more generic, and involves having an "allow resize only" type option for items. However, it has occured to me that there is another solution. An object can, in principle, resize itself, *if* it knows what resolution your client is running it. Imho, this is a much more useful idea, since someone could have a script request the client area (i.e. what the viewable section of the screen is, not including menus and the bottom bar, then translate that pixel dimension to the correct "size" for a HUD. One then simply stretches the dimensions of their own HUD, through the script system, so that it "fits" the area on the screen that the original design was "intended" to fit into in the first place. Its a simple enough fix, and one that wouldn't require people making their items modifiable in any way, since its the prims themselves that are "resizing" themselves, not the purchaser. |
Show » |
|
Takes so long to explain how to grab a HUD from off-screen to a new resident. And for many old residents too