Highrez

Manual download: Yeh because the DNS version check can take up to 24 hours to replicate across the net - that's expected.

As for the delete hotkey - I'm not sure - will have a look but I'm not going to stress over it, and not now as its almost 4am ouch!

Phil,

FYI. Autoupdate happened automatically for me for beta 10. I shutdown and reboot my machine every morning. The message for beta 10 came up just after booting. I agree that I would not likely see it if I was not in front of my machine. Have it set to update every day.

Best,

Wayne

Whilst you may not always see the update notification, it will keep checking and notifying. And you have the ability to manually check from the context menu.

I think that is good enough for now

Thanks,
Phil

I just published 2.10 Beta 11.
If you already have 2.10 Beta installed then Please use the auto-update feature.
Don't forget than the update check relies on DNS and this can take up to a day to replicate/get removed from caches.

Changes since v2.10 Beta 10:

• #291 - Fixed small memory leak in application profiles.

Any problems, PM me a copy of the log file (or post a snippet in a code block here).
Will this be the final 2.10 beta? I hope so!

Thanks,
Phil

auto-update required a manual check and worked. Would of been helpful to see a progress bar or something.

Progress... I will see what I can do - something basic will be better than nothing I guess

something strange is going on here ...

I'm running xmbc in a vmware guest, .10 is running ok.

I do a restart and all my startup items startup correctly.

I do an automatic upgrade to .11

I do a restart (of guest) and suddenly several startup items DONT start (including vmware tools and xmbc). I can reproduce this every time.

If I go into taskmanger startup items and disable xmbc, restart, then all startup items start correctly.

Any ideas?

mtissington wrote:something strange is going on here ...
...
I do a restart (of guest) and suddenly several startup items DONT start (including vmware tools and xmbc). I can reproduce this every time.

If I go into taskmanger startup items and disable xmbc, restart, then all startup items start correctly.
Any ideas?

No ideas and I just tested it in my VMWare guest and its fine here - everything starts up normally on reboot, after an autoupdate and on a plain normal restart....

All the auto-update does is replace the XMBC EXE and DLL files - it does not touch any of the startup entries or registry settings, only the full install does that (to add XMBC to the startup registry group).

I just published 2.10 Beta 12.
If you already have 2.10 Beta installed then Please wait for the auto-update and use that.
Don't forget than the update check relies on DNS and this can take up to a day to replicate/get removed from caches.

Changes since v2.10 Beta 11:

• #267 - Added download progress window to the auto-update function.

NOTE: The new update progress window will not appear until you update to the next version from beta 12!

There are some new language translations - see the translation thread for details...

Any problems, PM me a copy of the log file (or post a snippet in a code block here).

Thanks,
Phil

phil wrote:Ah yes VMWare strikes again.
If you had searched the forum you would have found the answer.

Its not a bug in XMBC, its just the way VMWare works with the mouse (at a lower level) it cant respond to the redirect scroll wheel over window messages. Ive tried all sorts and no joy. The only option is the workaround described in the thread above which works nicely but VMWare does have to be the active window, ie, scroll window under cursor option will never work with VMWare.

Thanks,
Phil

I apologize for not having searched for this. Thank you very much for the information, it does the trick.

I just installed 2.10 Beta 12 on a Virtualbox Windows 7 PC.
I checked the "Delete existing setting" box during install.
After the install when I clicked on the "Settings" button in setup I got a "Enter an integer between 1 and 10." error message before the settings window opened.
Number of layers was -1
Closing without changing anything gave the same error.
Changing the the number of layer to 1 stopped the message.

Thank you for reporting that - that is a new one since the configurable layer count in beta 10 I guess.
Will fix it ASAP.

I just published 2.10 Beta 13.

If you already have 2.10 Beta installed then Please wait for the auto-update and use that.
If you have already installed beta 12 then you should see the progress window when updating to beta 13 (or later) - assuming your internet connection is not too fast

Don't forget than the update check relies on DNS and this can take up to a day to replicate/get removed from caches.

Changes since v2.10 Beta 12:

• #287: Fixed bug with uninitialised number of layers when there are not settings to load.
• #286: Fixed further issues relating to hot-keys for Next/Previous layer (when disabled).
• #276: Fixed issues with Enable/Disable icon and layer hot-keys.

There are no new language translations - see the translation thread for details...

Any problems, PM me a copy of the log file (or post a snippet in a code block here).
After ironing out lots of little bugs recently, I hope we are close to release now, and that beta 13 is not unlucky!

Thanks,
Phil

auto upgrade to .13 worked perfectly ...

mtissington wrote:auto upgrade to .13 worked perfectly ...

Yay - did you see the progress window then?
I see it but it's only there for less than 2 seconds for me - the 5-600Kb update file comes down quite quick on my 35Mbit connection. I can imagine on a slower connection or further away from the UK based server it will be more useful

Lets hope all the other little fixes in beta 13 work and there are no more significant problems - then maybe I can release 2.10 this weekend (maybe I should give it a bit longer for any bugs to fall out).

Thanks,
Phil