Innerspace update
Moderators: Lavish Software Team, Moderators
Innerspace update
Hi all. It seems that after the 10/19/08 update, innerspace makes isxvg stop working. I've posted on that forum and now posting on this one so you all can discuss what you all did. I lost the menu ability drop down in my script. Someone did something that did something else, hehehehe. I just want my sum sum back
the post you fixed in the ISX forums Lax worked fine, the problem arrises on documentation on how the changes to the listboxes are implemented, the biggest break is this sort of line.
Anytime I run a refresh on the listbox using something like this:
just a snippet
it crashes the Innerspace itself and Vanguard all at once and pops up a crash log with the UIElement issue as the primary cause. I think I have the rest of my UI workign but kinda lost on how the new tabcontrol and listboxes work (I assume thats whast crashign this as its crashing only when I try to populate a combobox)
Anytime I run a refresh on the listbox using something like this:
just a snippet
Code: Select all
function PopulateList()
{
variable int i
/* Form */
for (i:Set[1] ; ${i} <= ${Me.Form} ; i:Inc)
{
UIElement[FormNameCombo@General@MainTabs@MainFrame@Main@AXScript@ACiDScipt]:AddItem[${Me.Form[${i}].Name}]
}
}
forgot the UI code that accompanishes this:
I dunno maybe I got somethign all fubared.. but thats supposed to be a combo box with a populated pulldown with all the forms availible to me. Now it worked proper before the patch today, and I see the controls changed but I can for the life of me figure out the issue. Any ideas or help I hope this isnt the wrong spot to see what the issue was/is with the new stuff, if I can get this working I can UL a fix to ISX but so far.. just crash after crash.
Code: Select all
/* Main GUI */
<Window Name='ACiDScript' Template='VG.Window'>
<X>75%</X>
<Y>35%</Y>
<Width>250</Width>
<Height>350</Height>
<Client Template="VG.Window.Client" />
<StorePosition>1</StorePosition>
<Title>[H:${Me.Health}] ....[${Script[VGB].Variable[PausedText]}].... [M:${Me.Energy}]</title>
<TitleBar template='VG.window.TitleBar'>
<X>0</X>
<Y>0</Y>
<Width>100%</Width>
<Height>20</Height>
<Children>
<Text Name="Title" Template="VG.Window.TitleBar.Title" />
<Button Name="Minimize" Template="VG.Window.TitleBar.Minimize">
<X>1</X>
<Width>16</Width>
<Height>16</Height>
</Button>
<CommandButton name='Custom Close Button' template='VG.Window.TitleBar.Close'>
<OnLeftClick>
Script[VGB].Variable[isRunning]:Set[FALSE]
</OnLeftClick>
</CommandButton>
</Children>
</TitleBar>
<Children>
<Tabcontrol Name='AXScript' Template='VG.Tabcontrol'>
<X>5</X>
<Y>1</Y>
<TabHeight>16</TabHeight>
<TabBorder>1</TabBorder>
<Height>90%</Height>
<Width>95%</Width>
<Tabs>
<Tab Name='Main'>
<Frame name='MainFrame'>
<Height>100%</Height>
<Width>100%</Width>
<BackgroundColor>FF000000</BackgroundColor>
<Texture></Texture>
<Children>
<Tabcontrol Name='MainTabs' Template='VG.Tabcontrol'>
<X>0</X>
<Y>0</Y>
<TabHeight>16</TabHeight>
<TabBorder>1</TabBorder>
<Height>100%</Height>
<Width>100%</Width>
<Tabs>
<Tab name='General'>
<Checkbox name='FormNameCheckbox' Template='VG.Checkbox'>
<X>18</X>
<Y>210</Y>
<Width>15</Width>
<Height>15</Height>
<Text>Form:</Text>
<OnLoad>
if ${Script[VGB].VariableScope.doForm}
{
This:SetChecked
}
</OnLoad>
<OnLeftClick>
Script[VGB].VariableScope.doForm:Set[${This.Checked}]
</OnLeftClick>
</Checkbox>
<ComboBox Name="FormNameCombo" Template="VG.ComboBox">
<X>70</X>
<Y>210</Y>
<Width>64%</Width>
<Height>15</Height>
<OnLoad>
This:AddItem[NONE]
</OnLoad>
<AutoSort>TRUE</AutoSort>
<OnSelect>
Script[VGB].VariableScope.FormName:Set["${This.SelectedItem.Text}"]
</OnSelect>
</ComboBox>
</Tab>
</Tabs>
</TabControl>
</Children>
</Frame>
</Tab>
Err.. nothing changed related to that.I think I have the rest of my UI workign but kinda lost on how the new tabcontrol and listboxes work (I assume thats whast crashign this as its crashing only when I try to populate a combobox)
I do have other suggestions related to your UI.
1. CommandButton is deprecated by the OnLeftClick embedded script.
2. You should avoid tying your UI to a specific "skin" -- I can only assume the vG "skin" is not a proper skin, thus the quoting. With a real skin, you would not need to use the Template tag, and your UI could be used with any skin by using the -skin switch on the UI command: e.g. ui -load -skin vgskin myui. The way skinning works is to swap in a set of templates to use, for example to make vg.window.titlebar.title automatically used in place of window.titlebar.title. Then if someone wants to use a different look with your interface, they can. As it stands, I could not, for example, use the WoWSkin with your interface without a load of extra work.
3. You can actually define a set of templates in your UI file that people CAN skin, e.g.
Code: Select all
<template name='acidscript.titlebar' template='window.titlebar'>
<children>
.. stuff here
</children>
</template>
<template name='acidscript.window' template='window'>
<titlebar template='acidscript.titlebar' />
</template>
See http://www.lavishsoft.com/wiki/index.ph ... ther_Skins for a download to a properly created skin, and http://www.lavishsoft.com/wiki/index.ph ... o#Download for a download to a well-done set of UI XML files.
Okay back to the issue. Have you reported the crash to me via the reporter? If not, please do so I can see what's going on (I don't see them if you have)
I will rewrite the GUI with the info you supplied to make it less reliant and more 'skinnable' as I do like that feature to be honest. Just used and was learngin from prior scripts which all used that old style junk. I will rewrite it and see if that fixes my problems beofre I send in reports to you as to not waste you time.
Thank you very much Lax, and hope to post again soon with some success or the like.
Thank you very much Lax, and hope to post again soon with some success or the like.
Great, I am hoping that with the new samples that are well-done, more people will create their interfaces and skins based off of them and, in turn, people who make new things will base their new things off of ones that are done well 
I should have taken the time to do it long ago, tbh.
I would like to see the crash report either way!
I should have taken the time to do it long ago, tbh.I would like to see the crash report either way!
Well removed all the templates as a starter and its back to working functionality so somewhere alogn the lines of using a messed up skin code it messed up a lot of the VG stuff. While ugly at its current stage (base UI) its functional, now to get on a proper VG skin to add possibly here when I finish it as to not let WOW have its only competitor being the default
thanks again Lax, I will run an older version and send you some crash logs to show you what was happening.
thanks again Lax, I will run an older version and send you some crash logs to show you what was happening.