Author Topic: Upgrade compile errors  (Read 2238 times)

SJones

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 7
    • View Profile
Upgrade compile errors
« on: May 22, 2017, 10:01:05 AM »
So I have been working on a project for many years now and have recently upgraded unity from 3.5 to 5.6 - there where a few minor issues that I resolved, however I have then started to update some packages too, ngui being one of them

so I updated to the latest ngui through the asset store and now have some errors, as I am coming back from a very old build of ngui I am not sure if there is any info related to such a large jump (think I was using ngui 1.x)

if there is some documentation to help with the transition of all the versions that would be cool, otherwise there are some stuff below that people may be able to help with

the first one is in UIGridRename.cs it cant find UIDraggablePanel - from what I understand the dragable panel stuff has recently been updated in V3, any advise how to resolve this one?

second one -UIInputValidator.cs(31,42): error CS1061: Type `UIInput' does not contain a definition for `validator' and no extension method `validator' of type `UIInput' could be found. Are you missing an assembly reference?

third - NGuiSetButtonTweenDirection.cs cant find UIButtonTween.

I got one thats not actually apart of ngui but relies upon it, I got it from the unity forums/help/docs (cant remember exactly where) some time ago that may resolve with the above or something I probably could look at fixing once the others are sorted, but will post it here in case someone can make a suggestion on the fix.
it was used in a drop down list of screen resolutions and has the error "Cannot implicitly convert type `string' to `UIPopupList.Selection' " and "`UIPopupList.Selection' does not contain a definition for `Split' and no extension method `Split' of type `UIPopupList.Selection' could be found."



SJones

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 7
    • View Profile
Re: Upgrade compile errors
« Reply #1 on: May 22, 2017, 12:45:04 PM »
So I have temporarily gone back to the backup build and found that actually it was using ngui 2.7, I had another look around here and couldn't find any upgrade notes/documentation - only thing I was able to find was a post with an upgrade tool with no instructions

Nicki

  • Global Moderator
  • Hero Member
  • *****
  • Thank You
  • -Given: 33
  • -Receive: 141
  • Posts: 1,768
    • View Profile
Re: Upgrade compile errors
« Reply #2 on: May 24, 2017, 06:59:48 AM »
Upgrading from NGUI 2.7 to the newest (3.11) is a somewhat massive undertaking, as a lot of features have change fundamentally.

Some of your errors sound like your own scripts UIGridRename and NGuiSetButtonTweenDirection have certainly never been a part of NGUI, to my knowledge.

There were some autoupgrade tools as a part of NGUI 3 for a while, but I'm not sure if they still persist. ArenMook would know better.

SJones

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 7
    • View Profile
Re: Upgrade compile errors
« Reply #3 on: May 24, 2017, 11:25:17 AM »
Hay, thanks for the quick info, your right with those 2 scripts, I knew the UIGridRename was, but I quickly looked at the directory for NGuiSetButtonTweenDirection - this was a playmaker script and I just saw ngui in the top directory and took it as part of ngui - my bad

my next question  suppose - while I wait to see if theres any help on upgrading - is it worth upgrading, the project works as is, the only thing I would be wanting is improved performance, its a RTS where I do have a lot (100+) UIFollowTarget scripts, this does have somewhat of a performance hit at that point, apart from that not much else, but I am always looking to squeeze as much as I can out of the game. so on average is there much of an increase?

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Upgrade compile errors
« Reply #4 on: May 25, 2017, 06:27:04 AM »
That's a difficult question to answer, both because of the unknown factors (complexity of your project, profiler-reported % time spent updating UI) and because 2.7 is so ancient and fundamentally different from NGUI 3 that is would be difficult to run tests (and pretty sure no one has done that). My guess -- and it's just a guess -- if your game works well as-is, focusing on optimizing the game code is going to be a much more productive undertaking in terms of boosting performance.