|
Yeah.
GTA physics. Not quite real-world yet.
|
|
|
|
|
I'm not familiar with the ramp buggy. is it online?
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Oh my, you're more evil than I thought. 
One thing that always amuses me takes place on Grove street (the dead end with street gangs).
Every once in a while, there'll be a purple Mananna or Tornado parked at the end of it, with a driver and passenger sitting in (just about to drive away as you show up), and people on foot walking on the sidewalk on the other side of it.
If the car's there, I'll plow into it on the driver side as fast as I can go, which will push the car into the pedestrians...so they get upset at that driver and start shooting at him.
Or try to get them shooting at me (with no star) then I call the cops on them, stand back and watch the ensuing chaos.
Other members of my crew like to antagonize the mugger.
|
|
|
|
|
OriginalGriff wrote: just don't do it in a populated online session as you will wreck the game for everybody else and that isn't fair!
That's exactly the problem with GTA Online, and R* has never done much given the impression of doing much to prevent mods like that - unless a mod is affecting them financially (like removing incentives for the noobs to buy so-called Shark Cards).
That's why nowadays I'm mostly playing in crew sessions. There's always an a-hole who will teleport right next to you, in god mode, as you're trying to sell stuff in an attempt to make a few miserable bucks, and kill you/destroy your merchandise with no way for you to retaliate.
|
|
|
|
|
If it is any consolation to you, at the moment I'm driving on sidewalks too in small mountaineous villages near the Mosel river. The roads are very narrow and winding, and this is better than causing a collision with an oncoming vehicle. So far I have managed not to hit any pedestrians 
|
|
|
|
|
RickZeeland wrote: at the moment I'm driving on sidewalks
Then please stop typing messages while you are driving, it could be considered dangerous. 
|
|
|
|
|
Went the through the whole thread and no one called you any names, however You seemed pretty triggered by some of the comments.
You chose to bring it back up 7 months later, holding a grudge maybe?
You are the one gaslighting people. What a toxic sense of humor.
Maybe you're just a troll and nothing more.
Reported you for being one, if more people will agree we'll not see you around.
|
|
|
|
|
Those movie advertisements they show in theaters before the main feature, why are they called "trailers?"
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
I would be more curious how popular that specific question is on google.
I couldn't find an answer to my question. I did find the Wikipedia page for the OP question. Wikipedia was launched in 2001 and the page for that question was added in 2005.
And then I thought about looking up the oldest page
Wikipedia:Wikipedia's oldest articles - Wikipedia[^]
Kind of interesting not because of the pages but rather the history of why they really have no idea what the original page was.
|
|
|
|
|
So I am not the only one asking about that Now that there are two of us, I took the time to see if Wikipedia could help me, and found this:
Due to trailers initially being shown after, or "trailing", the feature film, the term "trailer" was used to describe the promotion; despite it coming before, or "previewing", the film it was promoting. This practice was found to be somewhat ineffective, often ignored by audiences who left immediately after the film.
So, historically, they were trailing the main feature. Thanks for making me look it up
Religious freedom is the freedom to say that two plus two make five.
|
|
|
|
|
Thanks for doing the legwork on that 
I suspected as much.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Well, at least until someone comes up with a dumb name for them, like "prequel".
Preler?
modified 43 mins ago.
|
|
|
|
|
Nowadays they're also called teasers, isn't it?
|
|
|
|
|
|
They're meant to tease you.
And there's a tease in every trailer court.
Hence trailer, because they called call them ho's.
If you can't find time to do it right the first time, how are you going to find time to do it again?
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
this_guy_tho.jpg[^]
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
 Maybe it’s one of those Impossible dogs (that got Joey Chestnut disqualified from the main event)
TTFN - Kent
|
|
|
|
|
 when i first looked i thought it said vegan. could have been a vegan burger.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
It does say vegan. I was joking about it saying Megan.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Perhaps the tat on the other arm says "never"? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Stadium hot dog?
Yeah, I'd be willing to bet there ain't much meat in those.
|
|
|
|
|
I'm creating a data bank of MCQ (Multi Choice Questions) and their answers so that an app can be built around it. Regarding the actual storage format, I have two ideas:
- An array of objects with keys (
q for question, a for choice-a, etc.). - An array of arrays.
The first one is obviously more readable. Here is a brief sample of what I have so far:
{
"data": [
{
"q": "What kind of language is Python?",
"a": "Compiled",
"b": "Interpreted",
"c": "Parsed",
"d": "Elaborated",
"r": "b"
},
{
"q": "Who invented Python?",
"a": "Rasmus Lerdorf",
"b": "Guido Van Rossum",
"c": "Bill Gates",
"d": "Linus Torvalds",
"r": "b"
}
]
}
The app will read the q key to print the question, then present the four options (a, b, c and d). And the last key (r) will store the right answer. This is very much readable when viewed as a JSON file also. However, what I am thinking is that once the data-bank grows in size into hundreds/thousands of QA, a lot of space will be wasted by those keys (q,a,b,etc.) isn't it? In this case, an array like this is more efficient from storage perspective:
{
"data": [
[
"What kind of language is Python?",
"Compiled",
"Interpreted",
"Parsed",
"Elaborated",
1
],
[
"Who invented Python?",
"Rasmus Lerdorf",
"Guido Van Rossum",
"Bill Gates",
"Linus Torvalds",
1
]
]
}
In this case, each array will have 6 items viz. the question, four choices and finally the index of the correct choice (1==Interpreted, etc.).
Which of these two formats is better? Feel free to suggest any third format which is even better than these two.
|
|
|
|
|
I like the 1st better.
The 2nd, for me anyway, would be harder to keep track of square brackets.
If you can't find time to do it right the first time, how are you going to find time to do it again?
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
|
First, the question should probably be asked in "Design&Architecture[^]" forum.
Second, my preference would be for something like:
{
"data": [
{ "q": "question",
"a": ["answer1", "answer2",...],
"ok": 1
},
...
]
}
---
Edit: My suggestion allows you to have a variable number of answers to each question. Not sure if it's important or not for your application.
Mircea
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
