So basically, I have to do all of the work, I can do that closed source as well.
Printable View
scripts works again with the beta great ! thx for the fast fix freddy
We are on topic.
Lets stop bugging Freddy about open source. He's not going to do it, he's been asked millions of times, just drop it, and make you own Pascal compiler/SCAR clone!
Neither me or kaitnieks made the compiler, it's made by RemObjects Software: http://www.remobjects.com/ps.aspx
No it wasn't mean, it's just the truth. There are a lot of issues with all post 3.15b releases, and thing get worse the higher we go up the version ladder.
No doubt it will stableize in the future, but meanwhile we are stuck with a CTB/DIB-crashing Scar that refuses to run every single script twice.
@ Freddy: 3.23 still generates a lot of DIB-Handle errors with GetTextAtEx. Problem with this is: once it occurs (after one run), I need to restart SCAR.... every time for each time I run a script, which is rather boring if you use SMART and are forced to do colorpicking manual. So I give up.
A bug I get, I think I got it with 3.15 also, but I know I get it with 3.23 because it just happened yesterday is, say I edit a script, and I hit Ctrl+Z to undo stuff, then I hit Ctrl+Shift+Z (might be different for other people, don't know) to redo it, well if it goes too fast (I always just have it go all the way, not sure if this also happens when you undo and redo things slowly) it messes up. Like, it'll combine lines that weren't together and stuff and it'll look like a two year old was typing. It just scrambles stuff sometimes. I'll see if I can do it again and record it to show you if you don't know exactly what I mean.
i honestly don't know what everyone is talking about. Though i don't usually use SCAR for rs, i did so relatively recently (right before SMART broke the last time, i guess) and i had no errors. No problems so to speak of and though i guess that may have been a month or two, I doubt much can have changed, unless...nope cant think of anything.
It is maybe better to close this thread and open a SCAR known issues/bugs forum, and properly post. That is if Freddy agrees.
@WT-Fakawi. Instead of opening closing SCAR, I've found that doing:
Client>Reset Specified Window. And then dragging crosshairs again does the trick for most errors. Try that?
This sucks that our family is going into crisis mode all of a sudden. Guess this problem was piling up time over time that it really struck us. Its sad that both sides in this argument are right and wrong at points. I know saying were family and we should get over it wouldn't help here >.>, but I know we can pull through. I mean look, Call it as you want, Freddy is in charge here, you guys want to make it better, but hes not letting you mess with it.
Is Scar - SRL working for us now? It is, I guess the reason everyone is eager to help is because there afraid of our future. This has become something we don't want to mess up, we all want to save it in a way. Thats of course not to say that Freddy isn't going to fix this, To be honest, I know Freddy can fix Scar. Its just that were stuck on the opposite end trying to make this program into something that just is not in our reach >.> and were feeling pain for that. This is why we want to help, and thus the cycle begins again...
My opinion is just my opinion, I think were just being too attached to something, Change will come in time, Its inevitable, it will happen, for now we have to put trust into those who have the willpower to believe.