Dynamic Interface Library

by KingCold999
Dynamically create and control windows and controls at runtime.
ID:1472060
 
Resolved
Removed redundant proc.
BYOND Version:503
Operating System:Windows XP Pro
Web Browser:Chrome 32.0.1700.76
Applies to:Dream Seeker
Status: Resolved (b0.4.0)

This issue has been resolved.
Descriptive Problem Summary:

Numbered Steps to Reproduce Problem:

Code Snippet (if applicable) to Reproduce Problem:
//Other controls
Label
parent_type = /Control/
ctype="label"
var
text=""
align="center"
text_wrap="false"
image=""
image_mode="stretch"
keep_aspect="false"
GetParams()
var/list/params = GetDefaultParams()
params["text"]=text
params["align"]=align
params["text-wrap"]=text_wrap
params["image"]=image
params["image-mode"]=image_mode
params["keep-aspect"]=keep_aspect
return params
Update()
var/list/params = GetParams()
winset(usr, "[parent].[name]", list2params(params))


Expected Results:
For the label to be created

Actual Results:
Some bug claiming wrong client



Workarounds:
//Other controls
Label
parent_type = /Control/
ctype="label"
var
text=""
align="center"
text_wrap="false"
image=""
image_mode="stretch"
keep_aspect="false"
GetParams()
var/list/params = GetDefaultParams()
params["text"]=text
params["align"]=align
params["text-wrap"]=text_wrap
params["image"]=image
params["image-mode"]=image_mode
params["keep-aspect"]=keep_aspect
return params
Update()
var/list/params = GetParams()
winset(user, "[parent].[name]", list2params(params))


changing usr to user, as per the rest of the lib
Well I dun goofed haha. I'll fix that when I upload the next version sometime in the next week hopefully.

Been putting it off trying to figure out a way to deal with anchors not being settable at run time for an existing element, but might just release the updates before then if I can't find a workaround (other than deleting the element and remaking it from scratch, depending how often this is used would use a lot of resources after a while.. probably..)

Edit: Removed in next version, proc was redundant as the parent has the same proc that did the same thing.
KingCold999 resolved issue with message:
Removed redundant proc.