|
Boooo! Hope that scared you.
Get me coffee and no one gets hurt!
|
|
|
|
|
If you think about it, the internet isn't the only place where people act out because they feel anonymous.
The roads are another place. People treat each other terribly when they are enclosed inside their automobiles.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
True! True!
Get me coffee and no one gets hurt!
|
|
|
|
|
You are very right about that. Good point.
And some of those people who are acting out while driving are obviously also using their phones at the same time to post trolling messages.
Double-dipping-trolls!!!
|
|
|
|
|
|
To get fed. You just fed a troll. Please don't do that.
|
|
|
|
|
PIEBALDconsult wrote: To get fed. You just fed a troll.
I know. You are definitely right. I've ignored these so many times. Just this one time it got to me.
I think it got to me because I was really trying to have a simple conversation about an interesting thing I put a lot of work into.
Thanks for the input.
|
|
|
|
|
raddevus wrote: Why?
Because they get rep points for doing so.
|
|
|
|
|
PompeyThree wrote: Because they get rep points for doing so.
Well then, it all makes sense to me now.
Thanks. I understand there's really no explanation for such behavior. I appreciate everyone's input though.
|
|
|
|
|
I'm pretty sure I know the answer to this but...
I'm developing a 64-bit app that interfaces with Access databases, which works fine with the 64-bit ACE drivers. However, due to some inexplicable co-mingling, you can't have 32-bit and 64-bit Access drivers existing on the system without 'tricking' Windows. This also works fine, until Windows update 'fixes' your trickery, forcing your 32-bit Office installation to repair itself and break your 64-bit drivers.
Some solutions are obvious, but stupid (switch to SQL, turn off Windows Update, force users to use 64-bit Office...) and I'd like to get Microsoft's official recommendation.
They're going to make me pay for that aren't they?
|
|
|
|
|
Kyudos wrote: you can't have 32-bit and 64-bit Access drivers existing on the system without 'tricking' Windows
I haven't found that to be true. But maybe because our servers don't have Office installed? Do you have proper servers? Without Office?
|
|
|
|
|
It's a consumer app - it'll be on people's machines with their whatever-version of Office. If they happen to have 64-bit Office (unlikely) it'll all work OK, but if they have our 64-bit plugin, and 32-bit Office (more likely) its a potential problem.
|
|
|
|
|
Then it sounds like it's up to the customer to be sure it runs. Not your problem.
|
|
|
|
|
I wish! It'd be our app that fails, which means they ring us...
|
|
|
|
|
Maybe it does not work, but why do you not release a 32 bit version of your app for people running 32 bit office with 32 bit drivers?
Within you lies the power for good - Use it!
|
|
|
|
|
It's a plugin - if they have a 64-bit version of the host app, they need a 64-bit version of our product. Of course, we will have a 32-bit version too, but forcing the user to acquire a different 'bit-version' of the host app isn't ideal. Inevitably they will tend to ignore the requirement, and then complain about our app 'not working'.
It would all have been academic if Microsoft hadn't made their drivers mutually exclusive...
|
|
|
|
|
What if you determine the bitity on install and then make sure the correct plugin version is used?
|
|
|
|
|
There is no problem matching bitity of host and plugin - the problem arises when that bitity is not matched by the installed version of Office. Not many people use 64-bit Office, so people using 64-bit host are likely to have 32-bit Office.
|
|
|
|
|
Shouldn't you be able to find out which version of Office is installed, too?
|
|
|
|
|
Yes - but that doesn't really help. The best I could do would be to refuse to install or give some kind of warning if the bitness of Office doesn't match the bitness of the host app - it doesn't solve the underlying problem.
|
|
|
|
|
I often refer to coding as "going underwater" because when you are concentrating on some feature or algorithm or whatever it's as if you become totally submerged by the challenge. You can't even hear other people talking.
Anyways, I recently had this experience while writing my book, Launch Your Android App (releases at Amazon.com on April 1, 2016 (and no, it's not an April fools joke).
An API Can Suck You Underwater
There's a feature in Android which supposedly allows you to share text (import text into your app which the user has selected in another app like the browser).
It's easy to implement. Famous last words!
StackOverflow: I Wish I Could Also Post It Here In A Valid Location
I posted the problem with tons of images to StackOverflow and no one has had any valid response to it.
Android: Sharing Data and Receiving text from 3rd party app. Why doesn't my app receive new text? - Stack Overflow[^]
This isn't an article but I'd like CPers to see it. I appreciate any input anyone has.
Is there a valid place to post it here on CP?
Fascinating When Finding Bugs In Professional APIs
Does anyone else find it fascinating (aka frustrating) to find serious bugs in professional APIs from Google and the rest?
Painful Resolution
I spent days on this and finally created a great workaround. I have the scars to tell about it.
|
|
|
|
|
you should write this as an article here
(and as for trolls, FVCK EM - they feed off genuine/original work because they have nothing of their own to offer, so the only thing they can do is try to create misery - dont let them get to you)
|
|
|
|
|
Thanks I appreciate your encouragement.
Would this work as an article since it is a workaround solution to an odd problem with Android Intents?
|
|
|
|
|
Mycroft explained it well
You could post it as a tip or even a blog if you didnt have enough material for an article - I just think you have a lot of knowledge that's better out than in and may help someone
... as for the anally retentive ones, a tube of 'rhoid cream could fix them
|
|
|
|
|
Thanks for the encouragement. I really appreciate it.
I will try get it written up as a tip/article soon.
|
|
|
|