H
Henning
Schmidt said:
I have the same experience, they used it for a month, then went back to
kb/mouse. Their expensive touchscreens are only "normal" monitors today.
I have the same experience, they used it for a month, then went back to
kb/mouse. Their expensive touchscreens are only "normal" monitors today.
S
Schmidt
Am 14.01.2012 00:24, schrieb Henning:
Glad you confirmed that...
But it's logical IMO - first thing is, you usually
*sit* on a Desktop - and there's no convenient way, to
hold one of these larger 21-24" Touchscreens "on your lap"
One has to be standing, to use the touch-interface.
So first there's the "ergonomics" which are at play
here. And then there's of course a whole bunch of
more or less irrational reasoning, as for example:
"I hate those thumbprints on my screen, do I really
have to clean them myself any other day?"
not the least among them. ;-)
about 100Euro more expensive than their normal counterparts.
I used this model here (the touch worked well enough,
it even came with a small TouchPen-device in the bottom-
right corner):
http://www.alternate.de/html/product/Iiyama/ProLite_T2250MTS-B1/144613/?
Olaf
Glad you confirmed that...
But it's logical IMO - first thing is, you usually
*sit* on a Desktop - and there's no convenient way, to
hold one of these larger 21-24" Touchscreens "on your lap"
One has to be standing, to use the touch-interface.
So first there's the "ergonomics" which are at play
here. And then there's of course a whole bunch of
more or less irrational reasoning, as for example:
"I hate those thumbprints on my screen, do I really
have to clean them myself any other day?"
not the least among them. ;-)
Yep, same here - although there are devices which are only
about 100Euro more expensive than their normal counterparts.
I used this model here (the touch worked well enough,
it even came with a small TouchPen-device in the bottom-
right corner):
http://www.alternate.de/html/product/Iiyama/ProLite_T2250MTS-B1/144613/?
Olaf
G
GS
Just want to interject that VB will persist to exist as the language of
choice for macros in MS Office. Since MS has reworked VBA to work in
x64 (VBA7), I don't expect VB to disappear in my working lifetime.
While it may be arguable that VBA is not Classic VB in various ways, it
remains that the underlying core to the VBA language IS Classic VB!<g>
MS tried to take away VBA capability it Mac versions of MS Office and
got a horrific reaming for doing so. -Well.., at least enough of a
reaming that they put it back in pretty quick!
I'm thinking there is not a dedicated special runtime for VBA, and so
unless I'm wrong MS will continue to ship that runtime with MS Office
if they take it out of Windows!<IMO>
choice for macros in MS Office. Since MS has reworked VBA to work in
x64 (VBA7), I don't expect VB to disappear in my working lifetime.
While it may be arguable that VBA is not Classic VB in various ways, it
remains that the underlying core to the VBA language IS Classic VB!<g>
MS tried to take away VBA capability it Mac versions of MS Office and
got a horrific reaming for doing so. -Well.., at least enough of a
reaming that they put it back in pretty quick!
I'm thinking there is not a dedicated special runtime for VBA, and so
unless I'm wrong MS will continue to ship that runtime with MS Office
if they take it out of Windows!<IMO>
M
Mayayana
| You can not access Win32 functions directly in a metro app. For all
| practicle purposes, it is dead to the a developer targeting the metro
| interface. Period. To think that WinRT does not make use of Win32 at
| this point would be naive at best.
|
Exactly. It's another wrapper in API's clothing.
I don't want to write Metro trinkets. I doubt
that you really want to either. And it's *very*
unlikely that anyone's going to make money
doing that.
It'll be interesting to see how it pans out. Metro
is completely unrealistic for PCs. Nokia/Win phones
are getting great reviews, but no one is buying them.
Tablets never made much sense in the first place,
so it's hard to know how that will work out. No
matter how you look at it, people are not going to
be writing docs and spreadsheets on a swipe screen.
Microsoft tried to move developers out of the system
with .Net. They're doing it further with Metro. The plan
sounds a lot like trying to cash in on the Apple model:
Tight control. Developers have to be approved. MS gets
a 30% cut of software sales. That might happen, but it's
not going to happen on a PC. And that's the only kind
of software I'm interested in writing or using.
I'm actually very curious. On the surface, at least,
Microsoft seems to be turning away from corporate and
toward the entertainment market. So corporate PCs with
Win8 will be set to Desktop while non-business PCs will
be tuned to Metro, where people will spend their time
updating their Facebook page on their swipe screen?
That vision is so untenable in so many ways that I'm
quite curious to see how it all shakes out.
It seems clear that VB will be usable for Desktop
software as long as people can actually control their
own Windows PCs. And .Net will continue to be relevant
on corporate intranets, if nowhere else. If Metro survives
at all it will be in an entirely different arena.
| practicle purposes, it is dead to the a developer targeting the metro
| interface. Period. To think that WinRT does not make use of Win32 at
| this point would be naive at best.
|
Exactly. It's another wrapper in API's clothing.
I don't want to write Metro trinkets. I doubt
that you really want to either. And it's *very*
unlikely that anyone's going to make money
doing that.
It'll be interesting to see how it pans out. Metro
is completely unrealistic for PCs. Nokia/Win phones
are getting great reviews, but no one is buying them.
Tablets never made much sense in the first place,
so it's hard to know how that will work out. No
matter how you look at it, people are not going to
be writing docs and spreadsheets on a swipe screen.
Microsoft tried to move developers out of the system
with .Net. They're doing it further with Metro. The plan
sounds a lot like trying to cash in on the Apple model:
Tight control. Developers have to be approved. MS gets
a 30% cut of software sales. That might happen, but it's
not going to happen on a PC. And that's the only kind
of software I'm interested in writing or using.
I'm actually very curious. On the surface, at least,
Microsoft seems to be turning away from corporate and
toward the entertainment market. So corporate PCs with
Win8 will be set to Desktop while non-business PCs will
be tuned to Metro, where people will spend their time
updating their Facebook page on their swipe screen?
That vision is so untenable in so many ways that I'm
quite curious to see how it all shakes out.
It seems clear that VB will be usable for Desktop
software as long as people can actually control their
own Windows PCs. And .Net will continue to be relevant
on corporate intranets, if nowhere else. If Metro survives
at all it will be in an entirely different arena.
G
GS
GS explained :
Turns out, I've discovered, that the runtime for VBA IS a separate
runtime and includes several DLLs for the VBE as well. Interesting...
Turns out, I've discovered, that the runtime for VBA IS a separate
runtime and includes several DLLs for the VBE as well. Interesting...
T
Tom Shelton
GS pretended :
Not where I work - we use VS tools for office. VBA is banned.
Not where I work - we use VS tools for office. VBA is banned.
G
GS
Tom Shelton formulated on Saturday :
Yeah, I'm a big fan of using COMAddins over VBA. Though, I suppose the
..Net tools aren't really COM in the same way anymore. C++ is my choice
tool now but I'll use C# if .Net is really necessary. The nice thing
about C++ is that it still lets me use my 3rd party ActiveX components
that also work with VB6/VBA projects.<g>
Yeah, I'm a big fan of using COMAddins over VBA. Though, I suppose the
..Net tools aren't really COM in the same way anymore. C++ is my choice
tool now but I'll use C# if .Net is really necessary. The nice thing
about C++ is that it still lets me use my 3rd party ActiveX components
that also work with VB6/VBA projects.<g>
T
Tom Shelton
GS used his keyboard to write :
And you can use them in .NET as well... COM IS part of .NET.
And you can use them in .NET as well... COM IS part of .NET.
G
GS
Tom Shelton explained on 1/15/2012 :
Not according to the manufacturer. They recommend upgrading to their
..net versions. Has something to do with Windows Forms. If you can point
me to some info regarding using ActiveX components (in my case .OCXs)
I'd appreciate that very much.
Not according to the manufacturer
..net versions. Has something to do with Windows Forms. If you can point
me to some info regarding using ActiveX components (in my case .OCXs)
I'd appreciate that very much.
T
Tom Shelton
GS explained :
I've used AX components before... Simply add them to your toolbox - on
the COM tab, and drag and drop them on the form. So, either the
manufacturer have done something really stupid (can't think what,
because I haven't found one that didn't work - though, you might need
to change your compile target to x86) or they are lying.
I've used AX components before... Simply add them to your toolbox - on
the COM tab, and drag and drop them on the form. So, either the
manufacturer
because I haven't found one that didn't work - though, you might need
to change your compile target to x86) or they are lying.
G
GS
Tom Shelton submitted this idea :
I'm thinking they just want to sell more product. I'll certainly try
your suggestion in C#. Big thanks...
I'm thinking they just want to sell more product. I'll certainly try
your suggestion in C#. Big thanks...
T
Tom Shelton
GS formulated on Sunday :
Well, my guess is that they will work - but, I probably shouldn't have
been so terse in my response. There is always a possiblity that a
particular that something might go wrong in a new environment
Well, my guess is that they will work - but, I probably shouldn't have
been so terse in my response. There is always a possiblity that a
particular that something might go wrong in a new environment
T
Tom Shelton
Tom Shelton has brought this to us :
Wow... mangled that I was trying to say there is always a
possiblility of failure in a new envrionment - but, I must have been
thinking two sentences at a time....
GS formulated on Sunday :
Well, my guess is that they will work - but, I probably shouldn't
have been so terse in my response. There is always a possiblity that
a particular that something might go wrong in a new environment
Wow... mangled that
I was trying to say there is always apossiblility of failure in a new envrionment - but, I must have been
thinking two sentences at a time....
G
GS
Ok, I tried this and it's definitely a no-go. Not saying it's still not
doable, but rather a quick check didn't work for each of 3 components.
Looks like the C# environment doesn't like them, though. I'll try C++
when I get time...
doable, but rather a quick check didn't work for each of 3 components.
Looks like the C# environment doesn't like them, though. I'll try C++
when I get time...
T
Tony Toews
I very much like my Kobo Vox 7" tablet. But then all I really do on
it is read eBooks and browse the web. I don't do much else with it.
I certainly don't type more than a sentence on it while in Facebook.
Agreed. Although maybe with an external keyboard I can see some folks
using it to do some light work.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/