[Community Theme Creator]

1 hour ago, Magno said:

Hi, Everyone. I hope you guys going well!

Its my first time using this and when I tried starting the community theme creator and I get an error:

 

 at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
   at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
   at System.Windows.Application.DoStartup()
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run()
   at COMMUNITY_Theme_Creator_for_BigBox.Application.Main()
Initialization of 'COMMUNITY_Theme_Creator_for_BigBox.MainWindow' threw an exception.

someone can help me plz

 

read this thread for the explanation and solution.

 

[TV Series Scraper]

11 hours ago, Whatscheiser said:

You are my hero right now, man. This is great! I just got done scraping two shows and this does all of the heavy lifting perfectly.

One side note and I apologize if you covered it, but I do have autohotkey on this machine already. Issue was I'm running AHK V2 which didn't want to play friendly with your script. I grabbed AHK V1 to run it and it all worked flawlessly. Only mentioning it in case anyone else has a minute or two of head scratching there.

I love this though. Thanks!

Doesn't look like I specifically mentioned AHK version compatibility. I can add more info in the post on that to clarify for future users, along with instructions for users to link an AHK exe to the .ahk file extension. (someone asked about it in the Third Party App & Plugin thread) I made an assumption here due to the community has been sharing V1 scripts for years and LaunchBox itself includes a V1 executable. So, yes, this is indeed written in V1 syntax and glad you realized the V2 vs V1 thing. (I'm sure V2 threw an error right away) Also really appreciate the confirmation it's running well without issues otherwise!

[Autoplay Attract Mode]

34 minutes ago, izzishor said:

Great additions ❤️ love it, haven't tried it yet, but looked trough the code, seems great.

It would be nice if theese settings were integrated in Bigbox's attract mode...

Right now I'm using a modified version of my code in which I've changed the "close retroarch" action, with plain "send input alt-f4", so it now works for other emulators that get closed by alt-f4 too, even windows games.

it's neat idea you had here! just wanted to polish it up!

You have the right idea with using a universal closing command, but that is still not an ideal situation as it would close some programs in an inappropriate way. Alt+F4 is akin to Process Close which is akin to opening up Task Manager and killing/ending the process. This is a less than ideal way to close programs since some will not be able to execute code that the would otherwise at a normal shutdown. If for example they alter save settings on exit, those saves would not get done and worst case scenario means associated game or emulator files end up wrong, blank, or corrupted.  So in the end, the adjustment you're making is a lateral adjustment in my opinion. Might work with more emulators, but I wouldn't recommend doing it like that out of fear of making issues for yourself and others. I wouldn't recommend anyone use that with native windows games, native games have native exiting means that should be utilized whenever possible. WinClose is still a superior option to use since that is the equivalent of clicking the "X" button in the top right corner of a window. Games/programs will shutdown as intended that way and would execute any code triggered by an exit. With that said I recommend altering your script a bit further by avoiding "Process, Close" and sending Alt+F4, but instead make use of WinClose or some other equally safe method.

In order to get it to work with other emulators without the need to edit the specific emulator we need a way to detect which process (emulator/game) is running. Haven't got a good idea on this yet that isn't a bit....well, silly lol. I could make a long if/else ladder that basically goes "if emulator A exists then EmulatorEXE = emulatorA.exe else if emulator B exists then EmulatorEXE = emulatorB.exe......etc etc and so on". This would work, but every emulator would need to specifically spelled out. I know of ways to detect new processes, but it would be impossible to detect if one is an emulator or if one is some random additional app or game launcher etc. I may get creative and find a way to see if I can pass what the emulator is being used or even parse through the platform's XML file to find out what emulator is being used for that specific game and then either pass it as an argument or if needed store into an ini file and read it from there. I think I can get it to into different platforms/playlists too, that would just take a more involved if/else ladder diverting randomly using the random number, or maybe a different random number. Something like after say X games were played in the same platform/playlist, back out one extra step to get to platform/playlist like and then start the loop over after randomly selecting a new platform/playlist. It would be another step like what was configured for considering if game detail view were enabled/disabled