Jump to content
LaunchBox Community Forums

elborra

Members
  • Posts

    16
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

elborra's Achievements

8-Bit Processor

8-Bit Processor (3/7)

16

Reputation

  1. You can change the transition effect at BigBox->Options->Transitions . By my point of view is that the Fade transition is the best to get a nice fluid transition. Wheels are usually Strench to the parent grid so it depends of a particular resolution the outer systems from the wheel may be cut out. I like this behaviour but if you want to adjust in this particular case to a 16:9 resolution the easiest way (after some tests at 1080p) is to open with a text editor the "PlatformWheelImageDetailsThumbsFiltersView.xalm" file inside Metallic->Views folder. Search for CameraZPosition="3.0" and change for CameraZPosition="3.2". Edit: I came late and @niglurion already fix on last version.
  2. Hi! nice recently updates with the themes, @niglurion with the Metallic Theme and @Grila with the MinimalHD , both themes are awesome! Also the new Attract mode is amazing! i will spend a lot of time only looking to the tv from now Well, i shoud say that i'm not a pure theme creator as i'm not specially good doing arts and those kind of things. I really like the coding part of if trying to do new things and explore the posibilities. Having said that, this post is also a request for @Jason Carr and LaunchBox developers: On previous email we discuss about how to override some transitions over the bigbox configuration, but at the end if theme makers override those ones by code the final user would not be able to change them (if they want other tansition) without coding. I think a great solution to these would be to add inside the Bigbox transition menu a checkbox with "Use Theme Transitions". Of course Bigbox would need to override the default transitions with those from the theme. I'm not sure what would be the best way to do it, but probably as defaults transitions are saved in the launchbox.xml, @Jason Carr can do his magic and Bigbox would detect when a this is load if a "transition.xml" file exists on the theme folder and use those values to override defaults when binding, as it does now with platform Images folder.
  3. @niglurion great! I don't know if this is the solution you found, but inside TextFiltersView i got it with Path="Title" when i was trying to concatenate strings with bindings values on the same line. I took the oportunity to share (i don't know if this has been discused before): <TextBlock Visibility="{Binding TitleVisibility}" FontFamily="Calibri" FontSize="36" Foreground="White" FontWeight="Bold" TextWrapping="Wrap" DockPanel.Dock="Top"> <Run Text=" The platform name is: " /> <Run Text="{Binding Path=Title}" /> </TextBlock> You can see that with <Run Text="" /> it's possible to concatenate strings, i don't really know if there's a better way to do it.
  4. Yep, I luckily found it testing names when trying to achieve same thing. You should use the Path=PlatformTitle <TextBlock Text="{Binding Path=PlatformTitle}" Visibility="{Binding TitleVisibility}" FontFamily="Calibri" FontSize="36" Foreground="White" FontWeight="Bold" TextWrapping="Wrap" DockPanel.Dock="Top" /> Edit: This works at least on the PlatformWheels xaml files, i have not tested for other views
  5. In my case i saw a code to get the discount at emumovies on the LaunchBox email where you got the license file. End of the email on the P.S. It's a little hard to see, at least for me it was.
  6. I don't know how i miss the first post , i've read too much today. I will check tomorrow
  7. @johnugamer, background darkening and transition animation are apply to all themes. You can change those at: Background darkening: Options->Views->Background Fade: 70% Transitions: Options->Transitions It's actually possible to customize the theme to override the general transition options fixing the TransitionSelector property on the theme code for the desired transition. I made a quik guide at
  8. How to override a transition effect quick guide Transitions by default are linked to the Option->Transitions->"Choice". Themes could overrides the default effect fixing the effect to one in particular. You will need to change each property and value for each view desired. Here, we will override the Background transition on the PlatformWheelImageDetailsVideoFiltersView to use always the fade effect: Search for: <transitions:TransitionPresenter TransitionSelector="{Binding BackgroundTransitionSelector}" Content="{Binding BackgroundView}" Height="{Binding ElementName=Canvas, Path=ActualHeight}" Width="{Binding ElementName=Canvas, Path=ActualWidth}" IsContentVideo="true" /> Change to <transitions:TransitionPresenter Transition="{transitions:FadeTransition}" Content="{Binding BackgroundView}" Height="{Binding ElementName=Canvas, Path=ActualHeight}" Width="{Binding ElementName=Canvas, Path=ActualWidth}" IsContentVideo="true" /> Other Transition values i found are: Transition="{transitions:FadeTransition}" Transition="{transitions:ExplosionTransition}" Transition="{transitions:FlipTransition}" Transition="{transitions:RotateTransition}" All transition effect should have assigned a name/value and i believe than some of those can be more customizable like the ExplosionTransition but i haven't dig on it.
  9. @Jason Carr @CliveBarker, regarding the spanish translation, one of the things that shocks me is that, on Bigbox, the option "Back" is translated as "Reverso" (also on the key configuration). The correct word should be "Volver" or "Atrás". Reverso only means the back of something, sometimes we even use other synonymous that match beter with the object. The back of a card -> el "dorso" de una carta The back of a box -> la "parte posterior" de la caja The back of a sheet -> el "reverso" de un folio There are also other errors and misspells. I can make a review of the translation if you want. Only need the english and spanish strings.
  10. Hi, i don't know if you have already found the solution. If not here is how to do it: To change it's curve you can do easily with a text editor for each of these files, but as you also want to change the grid layout probably you will need to do with Visual Studio. It could be done manually too but if you don't know what you are doing it becomes confusing I recomend you to follow this tutorial to get use with some concepts Easy way - Default Theme reverse: Attached you will find the default Theme "reversed" as you want. Only for Platforms Views (Text list included). The problem I see is that some cover flows and key controls inside Bigbox were planned with the idea of having the wheel or lists always on the left side, you will notice if you try this theme. Same will happen if you try to do manually it's a code matter, nothing to do with themes. Hard way - Reverse wheel on any Theme - Steps: Each of the 4 wheel views on BigBox has its own xaml file on the Theme Views directory - PlatformWheelImageDetailsThumbsFiltersView.xalm - PlatformWheelImageDetailsVideoFiltersView.xalm - PlatformWheelImageVideoThumbsFiltersView.xalm - PlatformWheelVideoDetailsThumbsFiltersView.xalm 1. This is the "hard" part. Open Visually or with a text editor each of the views and change the grid layout to move the wheel to the right of the screen. As the layout could be different on each theme this process has no one solution. Follow the Tutorial to learn how to do. 2. On each view change on the coverFlowControl the property CurveAmount to a negative value to "orient" the wheel : For example: <coverFlow:FlowControl x:Name="FlowControl" HorizontalAlignment="Stretch" VerticalAlignment="Stretch" Grid.Column="0" CoverFactory="{Binding CoverFactory}" ImageType="ClearLogo" CurveAmount="4.5" VisibleCount="14" PageSize="6" /> to <coverFlow:FlowControl x:Name="FlowControl" HorizontalAlignment="Stretch" VerticalAlignment="Stretch" Grid.Column="0" CoverFactory="{Binding CoverFactory}" ImageType="ClearLogo" CurveAmount="-4.5" VisibleCount="14" PageSize="6" /> DefaultReverse.zip
  11. Yes, that's true, but even so usually there would be people who prefered "Sega Mega Drive" in favour to "Sega Genesis" for example. Only to clarify when i said " If it doesn't exists probably it is not worth to do the job." on the last post i meant the job to code it on launchbox not to do themes. Of course if you support the implementation it would make the distribution and "installation" easier.
  12. Regarding my post I think the override new feature is great but as images must match with the particular platforms directories the user has, the feature became a little limited, making users having to rename the images to fit the platform name (even for new themes that would use this overriding feature). I wondering if Launchbox keeps an internal platform id that always is the same, for example that "Neo Geo" has internally assigned "23" and "Nintendo Game Boy" always be "8".... The id could be numeric or not it doesn't matter. If this kind on fix index already exists on the code, Jason/developers could add a condition to override the default images not only with directory name matches but with their id (to give both options) At the end theme developers would call their images with the id and users would not need to make changes inside or outside Bibgox to enjoy the full concept of the theme the developer made. Finally the distribution of themes would be more compacted and "ready to go". If it doesn't exists probably it is not worth to do the job.
  13. Even better now, maybe a little more work to do but it works great and you will not need to change the default images you have. With the new beta update of bigbox new themes can have their own Platform images without changing defaults ones. That provides more customization but also means that if you change the theme and the Fanart doesn't match with it you will not need to change manually every time those images for others. How it works/Steps: 1. Copy from the Lauchbox directory "\Themes\Default\" the folder "Images" to any old Theme folder you want to set an unique platform image set. This "Images" folder will only apears if you have the last beta version of Bigbox installed. Example: Copy the folder "Images" inside "C:\Launchbox\Themes\Default" to "C:\Lanchbox\Themes\CleanBg" 2. Navigate to the "Fanart" directory inside the new folder you have just copy. Example: "C:\Launchbox\Themes\CleanBG\Images\Platforms\Fanart\" 3. Copy all the backgrounds to the "Fanart" directory 4. The "hard" work came now. You need to rename all background images to match your currently Platforms names. Example: Rename "bg-nintendo-game-boy-advance.jpg" to "Nintendo Game Boy Advance.jpg" 5. Profit If you like the same backgrounds for other themes you can directly copy the new Image folder with all the fanart images already renamed to that particular theme.
  14. Hope that's what you are asking. You can set the background opacity to 0% directly at BigBox, go to Option->Views->"last option:Background fade:75%" (guessing the names in english)
  15. That's Great, Hi all, I'm from spain (sorry for my english) and i've just join to LaunchBox a few days ago. As always i expend more time customizing themes and trying all the posibilities the FE offers that playing . I'm only testing what can i do with the bigbox theme, so i were doing the tutoriasl by my side while watching, then i notice on the last tutorial that we can access to some codes Variables, on the tutorial yo use the "PlatformTitle" var. Here is my question. Is there any way trought Visual Studio to know all the variables we can access to? On my concept of the Platform view i want to split the Details View between different parts of the screen, not all together and i wondered is there is something like "PlatformReleaseYear", "PlatformCPU", "PlatformTotalGames", etc... If there's not such thing, Jason, are you planing to publish a list of avaliable vars coded we can bind? P.S. Looking for an horizontal wheel too
×
×
  • Create New...