|
I left a scathing review of a restaurant's "call ahead" policy. I called ahead and when I got there I wasn't on the seating list - I was on the call ahead list and when they moved me to the seating list it was to the bottom of the list. Needless to say I left and let them page my cell phone multiple times before they gave up - costing them an open table for about 15 minutes. (I was already eating at a nearby restaurant when the first "your seat is ready" text came in.)
I left this on Google and the response was a "We're sorry your meal wasn't to your liking."
|
|
|
|
|
Rockstar support does make it seem as though they want to go through this maze of options, and none I can find ever seems to be relevant, so you're left leaving messages in areas that really don't have anything to do with what you're trying to say.
Whether they ever have a human read any of these, I'll never know. I gave up trying to reporting various bugs.
|
|
|
|
|
Sell the duplicate car at LS Autos. Should be worth a couple of dollars
modified 6-Sep-22 21:01pm.
|
|
|
|
|
It's worth $0.
If you win a car on the wheel, it has no value - so when you try to sell it, it reflects that. You will get back some value for any mods you've done to it, but ... only half. So if you win a car, upgrade it for $100,000 and then sell it, you'll get $50,000!
I'll just leave it to rot in a garage somewhere, and replace it with a better car later on when I need the space.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Message Closed
modified 25-Jun-21 6:45am.
|
|
|
|
|
Haven't you been told to put a sock in it about this before? You post only vacuous political musings, so I'm flagging this one.
|
|
|
|
|
Seconded, I don't mind a semi-political post once in a while, but Brexit seems to be the only thing Bram ever posts about and every time he gets a warning for it.
This is really just bait for a flame war.
|
|
|
|
|
Well, No,
This is not a bait for a Flame War. This was intended as a comedy remark.
Brexit however, has not gone away, it has "Not Been Done", despite the promises by Boris. In the end, he did not get Brexit Done, he left the NI part of the UK out of it. It is thankfully from my point of view still within the EU in many important aspects.
The bigger question is, what is deemed "Religious" or "Political". Religion or Politics, or both are part of peoples experience of life. Does that merely mean "Controversial". Is LGBT political?
Where is the Definition!
Is it out of bounds here to connect with people in Hongkong. because of laws there. If so, can they not protest on this forum about curtailment of democracy? I think there should be a wider policy debate here about how things are classified on the world stage.
Please consider this concept carefully
The lounge suggest free talk, and a place where one is free to talk about any issues, whatsoever. It is also a Physical Safe Place. No one knows each others front door, nor email address.
What is wrong with that.
Bram.
Bram van Kampen
|
|
|
|
|
Be aware of the message at the top of the page regarding political postings:
Quote: Trolling, (political, climate, religious or whatever) will result in your account being removed.
You are walking a fine line here, and I suspect you may already have stepped over it.
As Chris has said, there are many other sites where you can discuss such things - this is not one of them.
I'd suggest deleting your post before someone more trigger happy than I decides it is political trolling and starts the process ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I've been spinning my wheels on a simple design issue I can't decide on for the life of me.
I've spent a quarter of the time on this actually writing code - which works, and does everything it needs to - and the rest of that time I've spent on basically one method, and what to return from it.
All to switch screen modes, and all because different screen modes *must be* different actual types.
So you have to return something from a screen mode change operation that you can draw to.
What do I with the old draw target from the previous mode???? This isn't even something I can really ask someone about.
I hate problems like this. They leave me feeling paralyzed and frustrated because I can't just code my way out of it. I can't put myself in the shoes of a person using my code in this instance to a degree that satisfies me. So I can't answer the question.
I've got $150 worth of hardware that was donated to me on the premise that I would write driver code for it, and I'm stuck on this one stupid issue and at this point it is ruining my day.
Yes, I've already taken a break from it. That's why it is taking so long. The question isn't difficult. It's just difficult to decide.
*headdesk*
Anyway, I'm just venting, and also typing this in hopes that putting it out there might lead to me making some headway, as happens occasionally.
Real programmers use butterflies
|
|
|
|
|
Good luck!
I was going to say take a break.. but you already did... :/
Can you continue somehow and ignore that question for now? The best answer might make itself apparent if you manage to skip the problem for a while...
The details are a bit vague.. but if, say, a drawing directx surface became invalid, any further operation will fail with surface invalid or something.. how about that?
|
|
|
|
|
That is one of the options - to fail on subsequent drawing operations.
The other - trickier but doable option is to allow both to continue working, but at the expense of more memory usage (since its holding both frame buffers), and the fact that your whole screen will change when you start to draw to the original target again.
I don't want this to be too difficult for people. That's one of the reason I kind of don't like the failing options. The problem with failing is that in this environment I cannot use exceptions. If people don't check return values, the fails are all silent.
But maybe in this case that's for the best. After writing this out to you I'm leaning toward that. 
Real programmers use butterflies
|
|
|
|
|
perhaps you should have a method like ValidState IsValid(surfacePtr) so one could check the surface is valid or not and what happened to it?!
|
|
|
|
|
I have something like that already on my targets.
Real programmers use butterflies
|
|
|
|
|
All good then, I'd say! 
|
|
|
|
|
Let the developer decide.
You are writing an api, right?
Choose a default. Allow for the opposite value.
Complete the easiest path.
By then, reality should be more clear. If not, implement the other path, and repeat the thought process.
Finally, how is it handled in other OSes? Older systems? Maybe they were right?
Good luck!
|
|
|
|
|
First one is impossible. The code either works one way or it works the other.
The second one was basically my approach though both paths were non-trivial.
Older OS's and older systems were developed by people that either have never heard of generic programming, or avoided using it, so they've never encountered this issue.
Real programmers use butterflies
|
|
|
|
|
Ask me about the application I began in 2009 and still haven't committed to a decision about a design choice I thought I had made.
Back in the 80s (? I think it was in Turbo Pascal at that time) I had also stalled for a year while working on a game -- I needed to decide how to score a roll of dice. But I eventually finished that one and later updated it to C# and WinForms.
|
|
|
|
|
Something you mentioned earlier comes back to mind. Maybe changing your point of view is what's needed.
Switch over to writing a use-case for this API. What's the most useful behavior for what's being returned? If only one 'thing' can be active, and the returned item is no longer the active 'thing', then what about making the returned object read-only? You can return information from it that either doesn't require the active state, or is a copy of the last value held while the 'thing' was in the active state.
Software Zen: delete this;
|
|
|
|
|
The thing is if anything, write only, because it's a screen mode. You can draw to it to draw to a screen. (some screens support reading, but all screens support writing or they wouldn't be screens! )
Basically you instantiate a device, but the device itself has several screen modes. because of the way this code works, they must different actual types.
Hence the design complication.
Real programmers use butterflies
|
|
|
|
|
Whenever I've been in this state, pounding my head on the desk trying to decide something, it's always been the case I was looking at the problem incorrectly.
I'll admit I've used a brute-force solution fairly often of making the simplest decision and implementing it, knowing that it wasn't adequate and would fail. Iterating through this again and again, while looking wasteful, was a way of eroding the mental block. The act of implementing an idea, making it concrete, puts the brakes on the fruitless "nope, nope, nope, nope" cycles. Getting down to the details of each inadequate solution helped me learn about the actual shape and edges of the problem.
This also lets you throw something at the problem other than your peace (piece?) of mind, which is useful in my environment. Good luck.
Software Zen: delete this;
|
|
|
|
|
Absolutely. I've been telling myself, just code it, and then deal with it, knowing that if I choose poorly, I'll have to rewrite 90% of the driver code because of how it operates. The design decision has ramifications that impact the entire driver's codebase.
It's just tough to get that motivation to continue going feeling like I'll probably have to do it over again. Or at least I think that's part of it.
I'll work through it eventually. I feel a little obligated to make it a priority based on me accepting goods in exchange for my coding, even if it was informal. Just a little pressure though, not a lot.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: I can't put myself in the shoes of a person using my code
As far a I'm concerned, you're already ahead of the game by just considering another person using your code. I see far too many implementations where "oh, someone else might use this code besides me" clearly was never considered. Particularly the way API endpoints are coded. Definitely a WTF, as I see endpoints that are unusable except for the very narrow use case of a specific front-end implementation.
|
|
|
|
|
I always try to design my APIs like I'm going to be forced to use them. 
Real programmers use butterflies
|
|
|
|
|
Without code to go on, this is very speculative. Even code might not help, because of the time that would be needed to study it, trying to infer the design rationale before providing what might have a shot at being useful unsolicited advice.
But why should any of that be a barrier? 
1. How about returning void? The user must know they're switching modes, so they should adjust accordingly.
2. If switching modes can fail, even because of bad arguments, then a bool would be better.
3. If the previous mode can no longer be used, how about returning the new one? Can't it actually be returned?
4. There's also a "draw target". How about returning that?
5. I assume there's a "handle" to which clients write, and that it's polymorphic. So can the new one be returned?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
