This project is read-only.

Is Elemental not working?

Topics: Rawr.Elemental
Dec 9, 2010 at 3:10 PM

Whenever I try to change my class to elemental I get this error.

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See

   at Rawr.Elemental.CharacterCalculationsElemental.GetCharacterDisplayCalculationValues()
   at Rawr.UI.MainPage.character_CalculationsInvalidated(Object sender, EventArgs e)
   at Rawr.UI.MainPage.set_Character(Character value)
   at Rawr.UI.MainPage.Calculations_ModelChanged(Object sender, EventArgs e)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at Rawr.Calculations.OnModelChanged()
   at Rawr.Calculations.LoadModel(CalculationsBase model)
   at Rawr.UI.MainPage.ModelCombo_SelectionChanged(Object sender, SelectionChangedEventArgs e)
   at System.Windows.Controls.Primitives.Selector.OnSelectionChanged(SelectionChangedEventArgs e)
   at System.Windows.Controls.Primitives.Selector.InvokeSelectionChanged(List`1 unselectedItems, List`1 selectedItems)
   at System.Windows.Controls.Primitives.Selector.SelectionChanger.End()
   at System.Windows.Controls.Primitives.Selector.SelectionChanger.SelectJustThisItem(Object o)
   at System.Windows.Controls.Primitives.Selector.OnSelectedItemChanged(Object oldValue, Object newValue)
   at System.Windows.Controls.Primitives.Selector.OnSelectedItemChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
   at System.Windows.DependencyObject.RaisePropertyChangeNotifications(DependencyProperty dp, Object oldValue, Object newValue)
   at System.Windows.DependencyObject.UpdateEffectiveValue(DependencyProperty property, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, ValueOperation operation)
   at System.Windows.DependencyObject.SetValueInternal(DependencyProperty dp, Object value, Boolean allowReadOnlySet)
   at Rawr.UI.ClassModelPicker.SetCurrentModel()
   at Rawr.UI.ClassModelPicker.Grid_MouseLeftButtonUp(Object sender, MouseButtonEventArgs e)
   at MS.Internal.CoreInvokeHandler.InvokeEventHandler(Int32 typeIndex, Delegate handlerDelegate, Object sender, Object args)
   at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName)

Dec 9, 2010 at 6:51 PM

Correct; Rawr.Elemental is non-functional right now.

Dec 9, 2010 at 7:12 PM

Ah, well at least I know for sure now and can stop pulling my hair out :D Do you know when it will be fixed? Keep up the great work!

Dec 9, 2010 at 9:41 PM

Probably a good idea to catch some of those known exceptions and instead give a friendly message like "This model is currently non-functional, please check back later for updates!" (or something of that nature).


Otherwise you will surely get more people asking about it :)

Dec 10, 2010 at 11:39 PM

Right, a noble goal, but 99% of the time, just fixing the problem is faster than making a friendly error message for it.

Dec 12, 2010 at 2:26 AM

In other words: We absolutely agree with you that making a pretty frame would be nice (it would be!), but the time investment on making that box would cost more time than it's worth.

That said, is it possible to create a generic error catcher, that we could then manually define errors that crop up?  Or, would there be a way that we could hook in errors with relevant issue tracker tickets?  I'm not very experienced with code development, so this is me throwing ideas out there willy-nilly.

Dec 12, 2010 at 2:36 AM
Edited Dec 12, 2010 at 4:11 AM

Commit 56087

New Error Window Box

Dec 13, 2010 at 8:07 AM