33 replies to this topic

[Rob van der Does]

Not sure if there's any patch at all; in ViX it's an option in the system menu.

[littlesat]

When they made it.... then there should be a patch.... Because their basics is simply OpenPli,,,

When they have an option in the system menu... it is wierd... and also a patch...???

Our virtual keyboard does SMS buttons and virtual keyboard at once....

But what is the exact issue here you claim ViX solved?

Edited by littlesat, 15 October 2012 - 19:10.

[Rob van der Does]

See screenie:

Attached Files

•  RC Text.jpg   68.97KB   35 downloads

Edited by SatKiekerd, 15 October 2012 - 19:09.

[pieterg]

this has been discussed many times, there is no nice solution for this, because vu, in their apparent wisdom, decided to combine an ascii input device with a numerical input device (while these types of devices need specific handling, so they should not be combined).

The only thing you can work around that, is with an ugly hack.
And I personally refuse to introduce ugly hacks, especially when they are required because some manufacturor forgot to switch on their brain before implementing something.

[Rob van der Does]

this has been discussed many times, there is no nice solution for this, because vu, in their apparent wisdom, decided to combine an ascii input device with a numerical input device (while these types of devices need specific handling, so they should not be combined).

The only thing you can work around that, is with an ugly hack.
And I personally refuse to introduce ugly hacks, especially when they are required because some manufacturor forgot to switch on their brain before implementing something.

OK, understandable. The wish(dom) of manufacturers prevails over users being able to use PLi.

[littlesat]

When VU made it correctly following the normal rules.... the ugly hack is not required... that is why.............

[pieterg]

The wish(dom) of manufacturers prevails over users being able to use PLi.

Rather, the lack thereof leads to this.

[Rob van der Does]

The wish(dom) of manufacturers prevails over users being able to use PLi.

Rather, the lack thereof leads to this.

That's what I mean: users are the victim of this.

[pieterg]

seriously, I've spent more time in this thread already than it would take VU+ to fix this issue; it's really that simple.
I've said all I need to say about this, please complain to VU+, not to us.

[Rob van der Does]

I know VU doesn't do a good job here. I also know VU+ has been asked several times to cope with this. But all this knowledge doesn't bring us any further.
And users are still the victim of this, while a work-around is possible (as ViX has done; and ViX also supports 17 different boxes so this was not a pleasure either).

Edited by SatKiekerd, 15 October 2012 - 21:00.

[pieterg]

just bug them as much as you're bugging us.

We care about the quality of our code, so don't expect any hacks from us.

[Rob van der Does]

just bug them as much as you're bugging us.

????
It's users we're talking about!

Edited by SatKiekerd, 15 October 2012 - 21:20.

[littlesat]

I think it is very clear.... we draw a borderline not to made special box patches especially when a manufacturer could made a very easy and structural fix.... so blame to VU.... "if vu then" patches because VU refuse to fix their issues are not done....

"while a work-around is possible"

So you request an unrequired hack because VU refuses to make good code?

Edited by littlesat, 15 October 2012 - 21:24.

[Rob van der Does]

I do blame VU for that, that's not the point. If you knew how much effort I spend on letting them know about issues like that. And not only me: I know there are more clients who complained about many issues.
But as I said: given the fact that they apparently don't do this, or even understand what it's about, it's a pity to see users being the victim of this. Especially knowing that, although not desirable and even far from ideal, it is possible to make box-specific solutions (OK: work-arounds) for this, as ViX shows.

But of course: it's your choice to make the fundamental decision in favour of a 'clean' build (environment) and not in favour of the PLi-users who happen to have an Ultimo and are the victim of this standpoint.

No use in any arguing: you made your point perfectly clear.