I forgot to mention that you can code in Basic.
[attachthumb=#]
I did a search for Delphi.
To see it could also code in Basic.
I am sure I saw something somewhere.
Quote from: ThomasGrant on Jul 22, 10:20 PM 2010
I forgot to mention that you can code in Basic.
Sweeeeeeet!
BASIC is the one for me :thumbsup:
Quote from: VLS on Jul 22, 11:30 PM 2010
Sweeeeeeet!
BASIC is the one for me :thumbsup:
Great.
I recommend speaking to MMM admin.
And see if you can get a copy of RSS Pro.
It is a fairly good design tool.
Not sure how you can code Basic into Delphi.
But I am sure there was a link somewhere on the subject.
I think there is an option in the menu or something.
Don't know.
I looked in both version of Delphi I have.
And forgot where it was.
That is if it was there in the first place.
I mean if RSS Pro can code for you in Basic.
Then I see no reason why Delphi can't.
Just not sure how?
But I am sure you will find out.
I use "Just BASIC", here's the free down-load page for instructions and compiler, link:://:.justbasic.com/ (link:://:.justbasic.com/) .
Sorry Bayes... last time I checked, it's for Windows only.
Thomas,
Basic's decision-making nature is ideal for gaming programs; unlike Pascal, which focuses on set-manipulations, and in a more-formal manner. (Fortran's somewhere in the middle?)
To me Delphi/Pascal has always been a "tweener".
If you want to go soft: go BASIC.
If you want to go hardcore: go C/C++
...again: to me :)
By the way, amazing how things evolve in time. Back in the day it was:
- If you want hardcore go Binary.
- If you want soft, go Assembler.
Then:
- If you want hardcore go Assembler.
- If you want soft, go C.
If this continues... in the future it will be:
- If you want hard, use the keyboard to write a sentence telling the computer what to do.
- If you want soft, just grab the mic and talk it!
:)
Quote from: GARNabby on Jul 30, 10:39 AM 2010
Sorry Bayes... last time I checked, it's for Windows only.
Ha!
No worries, I've been using the same language for years. It ain't perfect, but programmers tend to get attached to languages, which isn't necessarily a good thing.
@ Victor,
Do you use any methodology for DESIGNING your programs, or do you just intuitively bash out the code and debug later?
Quoteintuitively bash out the code and debug later?
I think most programmers work like this, it's almost psuedo like which helps while the thought processing is in motion then change it later into code then debug.
I cut my teeth in php/mysql then when I got into roulette I did the same for a 'tool' but you had to enter the numbers from a drop down select box, now I use Autoit as it has allowed me to make my bots plug n play, open game, open tool click go, sit back and watch. Getting the numbers was the hard part as Autoit does not have any OCR in it.
A tool template is the grounds for the tool, then I just use an include file where I do all my fiddling, different methods etc, the main tool just gathers the numbers and puts them into an array for later manipulation.
Looking forward to see Thomas's creation
Quote from: Bayes on Jul 30, 11:04 AM 2010
@ Victor,
[...]do you just intuitively bash out the code and debug later?
Yes, that's correct.
Quote from: superman on Jul 30, 11:33 AM 2010
Getting the numbers was the hard part as Autoit does not have any OCR in it.
S.
Did you manage to find any suitable OCR to plug into your programs or did you have to develop your own? Just curious.
Quote from: superman on Jul 30, 11:33 AM 2010
I think most programmers work like this, it's almost pseudo like which helps while the thought processing is in motion then change it later into code then debug.
I used to work like this, and still do for short/simple programs, but after a while I found the whole business of bug-hunting to be incredibly frustrating and time-consuming, so I looked around for a more systematic way of designing the program before coding it, and found Jackson Structured Programming (link:://en.wikipedia.org/wiki/Jackson_Structured_Programming).
Using this has virtually eliminated the need for debugging, it's rare now that I need to spend any time on it at all. Plus, it almost completely removes the need for inspiration; programming is now a more or less mechanical process (but there is still room for creativity). It's a very visual technique which means you can see the "shape" of your code and easily make modifications. If you had to draw all the diagrams by hand it would be tedious, but there's an excellent free editor which makes it a snap to create them, add and remove elements etc. It even generates code in C and Pascal directly from the diagram (see link at the foot of the wiki page).
I know that a lot of programmers actually
enjoy debugging, it gives them a kick when they eventually find that elusive bug, but I can easily do without any of it!
Personally, I like ease of use.
KIS Keep it simple.
Back, way back when...
At one point I owned an Amiga.
A what?
Or you did?
Is the response I get.
Back then it was the bees knees.
One of the programs that I like to use was called CanDo
It was the precursor to Delphi.
Well sort of.
You could do so much with it.
Again, easy to use.
Delphi and pascal are not that hard to learn.
With RSS Pro. Designing and getting things working is very easy.
Well, sort of.
As there are no definitive guides to RSS Pro apart from mine.
There is a wealth of stuff on Delphi.
QuoteDid you manage to find any suitable OCR
Nope, I ended up getting the coords of the rectangle the numbers display in
$startx = 727
$starty = 56
$x = 53 ; 0 - 53 = 54 pixels width of rect
$y = 8 ; 0 - 8 = 9 pixels hight of rect
Then run a while loop inside a while loop incrementing the row and column count as required counting which pixel was red/black/green, this then returns me a bar code type result for a switch statement which I push into the top of an array, on pushing I also add ALL the things attached to the number, red, high, even, dozen3 etc
This method is limited but worked for what I wanted, it only works on Playtech as the numbers are perfectly built without any bleading.
@ Bayes, I didn't actually finish my post, I forgot to add, after doing it in real rough pseudo style I always then run through it again with higher concentration, I was just reffering to how the script begins its life, very rough, proper code, run then debug, there's always something that you missed or isn't doing what you expected, all fun though.