Hi there Daniel, I have been using LFSLazy since about 2014-2015 Christmas but the day before yesterday and yesterday we came across three problems. The first being the in-game dashboard; our problem (Which I have fixed for myself but don't know how) is that he can't see the dashboard in first person/is staying as the default dashboard, and because I am also using the NTO Rev Bouncer it flickers when I use it.
The second which we found out is "Build 41" Which whenever I/we start LFS up is come's up with this: https://www.lfs.net/attachment/133761/thumb
But when I start up the LFSLazy program it comes up with this:
*EDIT - Also whenever I tab out of LFS with LFSLazy running, my screen turns black and stay's black until I close LFS.
Not really a problem for me to change a color. To be honest I don't really care much about appearance, functionality is more on my mind. I'd like to hear from others as well, is that light gray default color better?
Let me know if you find the cause.
Its like that from begining. Rev bouncer kills your ignition and therefore it has some effect on LFSLazy dashboard. You can modify dashes that you are using, so its not turning off with ignition.
Does the crash happen when you are updating to build 41?
When does it happen exactly? The moment when update window appears or when you click update?
I wouldn't mind getting a crash report.
For now you can manually update by downloading LFSLazy from the first post and replacing it in your LFSLazy folder.
Seems like you are still using build 40, that should be fixed in 41.
Try downloading LFSLazy from the first post and replacing it in your LFSLazy folder as I already said.
Especially important since I've made millions from LFSLazy sales
I'm glad to hear some input. Yeah, that Steam window is simple enough, but I still think I cannot leave out some vital things e.g. current version, newest version. What do you think about showing the size of a new version? Also current progress with the download, progress bar is nice IMO, are the numbers needed e.g. 1553/2893 KB ? Change log is also vital part which I don't think I should leave out now.
Any "complaints" to other windows?
Actually its great to hear some, it made me think how certain parts can be improved.
Actually, when I talk about Steam update window, it's not a static thing. Of course your need to ajust it to your needs !
EDIT : Always think that some people are actually afraid of informations, they just want that the app do it stuff and that's it, so UI have to be thinked to please everyone (more or less, from the "show me the new code un changelog, I want to know everything" to the "do your stuff, I don't care" peoples). END EDIT
I was thinking something like writing the download size (in Mo/MB instead of KB, because it's easier to read) where the "Extracting package..." is.
For informations about versions and changelog, I think and adding a button "Detail" witch deploy the changelog, show the current and new version. Here is a representation of it (don't mind the shitty XP theme and please don't reproduce it lol ) :
For the main window I have an idea but I have to go to work, so we'll talk about it later.
As it is the case with almost any InSim application, LFSLazy also use InSim buttons. Button system in LFS does a great job and yet it's simple enough. However, there are certain limitations while using it, for example, you can place only up to 240 buttons. That may seem like a lot to some, but surely it's not enough from the programmer's side when you want to show a lot of data.
A few months back, I started working on my own button system using LFSLazy overlay (like Radar and Dashboard work). I've put it on hold because of other personal obligations. With the recent design suggestions by nacim, we continued to talk on PM and he reminded me of overlay potential, so I've decided to get my button system near the finish.
The new button system has much more options than standard InSim one, for example:
unlimited number of buttons
complete control over the position on screen to a pixel
background and text color can be selected from a full range of colors and alpha (ARGB) for each button separately
possible to use different fonts
LFS color code handling is implemented as well and it can draw borders around buttons from full ARGB range. Firstly, I wasn't that satisfied with the performance, after some optimisations and testing I actually think it does a great job now. For example, pure LFS at same scene gives me 133 FPS, using my button system I get 126 FPS and using InSim 125 FPS. When buttons aren't that filled with text, it performs much better than InSim's one.
Sure thing, many great things come with this, but what I'm worried about is that there are still some people that have problems running LFSLazy overlay. I'm not sure that I will be able to help them. If they cannot use Radar or Dashboard (run LFSLazy overlay), they won't be able to use new button system. If I decide to move to the new system that will leave them disabled.
About moving to a new system, it can be easily be done using a wrapper function. It will take some time to make all code take the full functionality of a new system. Many great animations can be done, fade in or out on a group of buttons for example, but have in mind once I move to a new system there is no move back. Here is a screen shot of gadgets drawn using the new button system: