0 of 0
File information
Created by
registrator2000Uploaded by
registrator2000Virus scan
Some manually verified files
videogame_asset My games
Install hundreds of mods with the click of a button.
Notifications
-
Give Feedback
HUDFramework API Suggestions (18 comments)
like scrap,ammo,weapon,money. i hope if you will add the ability to cancel it since at least for it really annoy me so i would love to just read the original name
maybe put a logo next to it
i would love it if you change at least this
and thx for the great mod
For hooking into VATSMenu and other menus, this is possible today with F4SE but I'm not certain if it should be in HUDFramework's scope to do so! (See Vertibird Jump F4SE plugin source for an example on hooking VertibirdMenu and adding a new native function to BGSCodeObj.)
RegisterWidget::asSWF
"The path to your widget's SWF file. The root directory is Data\Interface. This is the widget identifier. Use this value in future LoadWidget and SendMessage calls."
The `SendMessage` function works with the same WidgetID used for `RegisterWidget`. For some reason the `SendMessageString` function must omit the file extension from the WidgetID. Below is similar to what Ive used for the WidgetID of `SendMessageString`.
HUD.RegisterWidget(self, "MyWidget.swf", 10, 70)
HUD.SendMessage("MyWidget.swf", UpdateNumber, 99)
HUD.SendMessageString("MyWidget", "UpdateString", "Hello World")
I may be misunderstanding something or its just an inconsistency in the framework. Much appreciated if you could shed some light on this.
opps wrong thread
I have now fixed this inconsistency in 1.0d.
If you would like some context: In the beginning, widgets were to 'subscribe' to and register their own widget IDs at runtime by calling hud.subscribe("<WidgetName that the widget wanted to register>"). However, I eventually decided against this because two widgets could register for the same name and then encounter issues, so I used the widget path as a unique identifier for each widget and auto-registered that name with HUDFramework. This registration was for the 'friendly-name' of the widget (without the extension) instead of with the extension and this was left over for SendMessageString.
Very impressive work you have done here.
For instance, you can evaluate a script that moves a UI element relative to its current position with the += operator. You can also have if and else conditional statements to make sure elements don't get moved off-screen, for example.
Usage is as follows:
hud.Eval("data.myWidgetData = 5;")later...
hud.Eval("myWidget.x = data.myWidgetData")For more complex AS3 manipulation, I agree that it will be useful and likely easier to create a widget, sending widget commands to make these changes natively in Scaleform rather than rely on just the Eval function.