Creating first ever screen : NullReferenceException

[kherron]

What happens if you click one of the select buttons?

Also, this still looks like the old screen.

What version OSA are you running?

[tommysharp]

This is the file I downloaded to install... Can I see the version number anywhere? OSA website also says I'm running 0.4.3 if I go to the settings page.

OSA_Server_v0.4.3_x86_x64.exe

What happens if you click one of the select buttons?

If I click a select button then it brings up all the images and I get to pick one.

[kherron]

OK, you are definitely running 0.4.3.

Forgive me if I'm wrong, but isn't the screenshot Automate posted from 0.4.4??

Even mine looks like Automates not

Will the latest OSAE.UI.Controls.dll work under 0.4.3?

[Automate]

My screen shot is from 0.4.3 but with the OSAE.UI.Controls.dll attached.

Can someone else test and post what they get?

[Vaughn]

File size was capped at 100k which gave me a problem loading backgrounds. So them my screen was pointing to an image that did not exist and it gave me null errors. I trapped the main screen's error with an invalid background image, but I still need to fix the "Change Screen" selection, as an invalid image is still causing a null error there.

I am doing a lot of tweaks to the gui this release, so hopefully will catch much of this...


Vaughn

[kherron]

Can someone else test and post what they get?

Just tried it and it works fine here.

I can add a state image, and a weather object with no issues.

Also, the State Image Add screen does look like your screenshot, not like tommysharp's

[tommysharp]

Mine is a fresh install about a week old so should match everyone else's.... Very strange.

Any other screenshots I can do to look for differences?

Sent from my Nexus 5 using Tapatalk

[Vaughn]

As far as I can tell, the only thing generating these errors are image issues. For example, you can go rename the Background Image on your screens, and it will blow up the GUI when those images can't be found. So if you have a control crashing the app, try deleteing the image names, or using a known good image name to test it.


In the current version, I have been breaking the names on purpose just to trap these errors. I think it will help alot. Version 044 not only fixes some of these errors, but it allows you to edit any of the controls right from the screens application too. I think everyone will be much happier with the latest version of Screens.


Vaughn

[tommysharp]

Okay cool, thanks Vaughn... Will give that a try...

You knew this question was coming..... How are you feeling on time frames for an 044 release? Weeks, Months, Years?

[Automate]

Brian W may have to answer about 0.4.4

What is the file date/time on C:\Program Files\OSA\OSAE.UI.Controls.dll