Vehicle Maintenence Plugin

**Sonicxtacy02** · 08-09-2009, 05:44 PM

#1 when you went back to the history screen what command did you use... using BACK or EXIT or CLOSE will not reload the history screen with its data... you have to set your back button to run RRVM_HISTORY. Is the data still in the .csv file ?

#2 I did the price calculations rather early on and they could probably use a bit of a recheck

I didnt enable the debug class yet... it was in my plans for tomorrow. I wont be around much tonight to work with it anyway.... i'm shopping for some new home theater stuff (tax free weekend!)

Originally Posted by JohnWPB

Ok, I am not to the point of putting a bug report together yet, as I still ahve to get all buttons in place and skinned. What do I need to do to turn on debugging, and how do you want me to get it to you? I will be on YahooIM this evening.....

A couple things I noticed. I had an alert that an oil change was due when I updated the odometer. I clicked the button to reset the item ("RRVM_RESETMAINTENANCE"). When I did this, it reset to 3000 miles and 90 days, but now in the history screen everything is empty, no matter how it is filtered. I had a few fill up's, and a water pump repair in there for testing. I restarted RR, and still it is all empty now. When I go back to the fuel screen, the fill up's are still listed there.

On another strange note, when I press the button to go to the maintenance screen("RRVM_MAINTENANCE"), it adds money to the total cost per mile variable ("RRVM_TOTALCOSTPERMILE"), around 1/10 if a cent or so every time it is pressed.

**JohnWPB** · 08-10-2009, 12:02 AM

I am using the commands to load the screens on the top right buttons in the screen capture above to switch screens. There are no ESC, CLOSE, BACK ect commands.

When I open the CSV, it looks like the "Reset Item" just cleared the price of the item:

MAINTENANCE 8/9/2009 Oil Change 65000
REPAIR 5/22/2009 Water Pump 62365 129.95
FUEL 8/9/2009 62800 2.52 14.6
FUEL 8/9/2009 62500 2.47 14.2

I put the price back in on the line, fired up rr and now the history is showing.

Looks like an error trap is needed to look for empty fields, as well as why it only cleared out the price using the reset_item command.

**JohnWPB** · 08-10-2009, 05:04 AM

Ok, its just about all skinned.. all except for the msg boxes, as I am hoping some changes can be made

There are a LOT of screens and reading just to enter fuel added, which will probably be the most common thing entered, as well as the most often.

It's quite a lengthy process:

Click Add Fuel button
Msgbox saying "Please take a moment to enter information needed to record fuel fill up's and calculate mileage. Click next to enter the odometer reading at the current refuel"

Click Next
Enter the odometer on the NumOSK
Press Enter (After data entered)
MsgBox saying "Click next to enter the price per gallon of fuel"
Click Next
Entered fuel on the NumOSK
Press Enter (After data entered)
MsgBox saying "Enter the gallons of fuel used at the fill up"
Click Next
Press Enter (After data entered)
MsgBox asking "Thank you, would you like to view the fuel data now"
Click Yes

Just to enter in fuel is 7 OK's and Enters plus the data entered.

I would like to see a much simpler, and faster way to do it, by simply moving all the message box info to the top of the NUMOSK as a label. This should be really easy to change in the code, as you are just removing the msgbox's, and then only updating the "info required" label instead.

Click add fuel button
NumOSK opens and at the top states "Enter current odometer" Press Enter (After data entered)
NumOSK changes to say "Enter Price per gallon" Press Enter (After data entered)
NumOSK changes to "Enter the gallons used" Press Enter (After data entered)

Then just default going to the fuel data screen after the last item is entered.

This makes it much simpler, and only requires 3 click plus the data.

Have you checked into why the numosk is so slow to respond? I have to pause between clicking each number, or it misses one. I have entered in the wrong odometer quite a few times during testing, due to the lag.

If you want, I can zip up the skins and images I have done, so you can check them over, and see that everything is as you intended it to be. I can make it a "Complete skin" with a main menu so you do not have to overwrite any files on your end.

**Sonicxtacy02** · 08-10-2009, 11:41 AM

i planned on removing some of the message boxes when you suggested the numosk label... and i will check on the reset procedure as well.. that was the very last thing i added so it doesnt surprise me that it would go wrong. Unfortunately i wont be able work on this for the next few days at all because i just got 10 stitches ont he back of my right hand

. Shattered glass sucks @$$.

**JohnWPB** · 08-10-2009, 12:35 PM

Originally Posted by Sonicxtacy02

Unfortunately i wont be able work on this for the next few days at all because i just got 10 stitches on the back of my right hand

. Shattered glass sucks @$$.

Wow, you must have said something to really upset Dawn!

Seriously, 10 stitches.. What happened?

No Problem, I have plenty of other things I can be working on here to get this skin ready for the next release..... which is how I found out the Movie times has stopped working. Prob was just a matter of time before they changed the webiste you are scraped from.

**carputer1** · 08-10-2009, 01:17 PM

sorry to hear Sonic's , maybe john can hook you up with 1 of his speech - text programs lol.... looks like i had a better escape than you did , comming home today , some idiot just pulled out on me i had to lock up and the truck did a 360 in the middle of the road, i managed to catch up with him , a scary the living daylights out of him , his excuse was he wanted to get out before the push bike i was overtaking . oh well shaken up but all good lol....

**Sonicxtacy02** · 08-11-2009, 11:22 AM

ok i've got reset bug all figured out.. i actually completely forgot to add the cost to the history array!

I'm in the process of converting over then msgbox/osk stuff... and i'm really considering further streamlining the information entry process by having one OSK for all entry. What i mean by this is RRVM_OSK.skin will be the only skin for all entries, and the osk will remain open with only the label changing to indicate what data need be entered. Doing it this way will improve the feel of data entry i think. It will also allow skinners to simply copy there existing osk.skin file and only change the ENTER button to "RRVM_ENTER". the RRVM_ENTER command will save the osk text to a variable for the plugin to use. Sound like a plan?

**Sonicxtacy02** · 08-11-2009, 11:27 AM

Originally Posted by JohnWPB

Wow, you must have said something to really upset Dawn!

Seriously, 10 stitches.. What happened?

No Problem, I have plenty of other things I can be working on here to get this skin ready for the next release..... which is how I found out the Movie times has stopped working. Prob was just a matter of time before they changed the webiste you are scraped from.

i have an old door in my basement that i'm assuming expanded in the heat to the point i couldnt open it. I kicked the door open and in the process shattered one of the panes of glass. as i was pulling shards out of the window frame i pulled my hand too far back and got sliced by the glass. As they say .. ***** happens! lol

the movietimes thing really ****es me off honestly. i guess the data sourcing people are losing money in the economy and as a result are keeping a close eye on who's pulling there data. I'm still looking for a solution there but it seems like EVERY movie scraper program is down now.

**carputer1** · 08-11-2009, 12:51 PM

FYI sonic . in the osk and rrvm_numosk ,i have added the RRVM_OSKTITLE label you suggested a few posts back so you should see that working straight away .

**Sonicxtacy02** · 08-11-2009, 02:26 PM

i've got ahead and made the changes to the data entry. There is now ONLY RRVM_OSK.skin (no more numosk). The RRVM_OSK.skin can be identical to the standard osk.skin that comes with every skin with the exception of two things.

1. The standard K line with the "ENTER" key should be changed to button code "RRVM_ENTER"
2. There should be a label on the osk named RRVM_OSKTITLE

Here's an example... thanks carputer1!

doing it this way makes the entry process faster. There's no more key lag john.