Any idea when the namespaces branch will make it to full version status? Looking at the new Table, I really like it and I really need it. Is there anything in the rest of the controls (current controls that were moved to namespaces) that we should worry about? Are things working correctly, or at le
Sorry,I can't help it. :-)There seems to be a dilemma in regards to consistency of dates:Compare the first parargaph of
http://www.json.org:"JSON (_javascript_ Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and g
Andreas Junghans <[EMAIL PROTECTED]> writes:
> Come on, it's not that hard! You simply have to treat the start and end of a
> date the same way you treat the quotes for strings.
>
> Attached is a patch to your JSON parser that does exactly that.
Yup, after a comment like mine, I deserved this. :-
Hi Derrell,
Am 16.06.2006 um 03:31 schrieb [EMAIL PROTECTED]:
If it's feasible to do, I would like to at least have the ability
to have the
same format going both directions. I'll let you know the results.
I just saw your message directly after I sent mine :-) However, it
seems I had fo
Hi Derrell,
Am 16.06.2006 um 00:59 schrieb [EMAIL PROTECTED]:
> Andreas Junghans <[EMAIL PROTECTED]> writes:
>
>> I would greatly prefer a single, standard format, no matter in which
>> direction a date is sent.
>> ...
>> Since it's so difficult to properly handle timestamps in PHP (and
>> mayb
[EMAIL PROTECTED] writes:
> Andreas Junghans <[EMAIL PROTECTED]> writes:
>
>> I would greatly prefer a single, standard format, no matter in which
>> direction a date is sent. ... Since it's so difficult to properly handle
>> timestamps in PHP (and maybe other backends too), I suggest we standar
Andreas Junghans <[EMAIL PROTECTED]> writes:
> I would greatly prefer a single, standard format, no matter in which
> direction a date is sent.
> ...
> Since it's so difficult to properly handle timestamps in PHP (and maybe
> other backends too), I suggest we standardize on the second syntax: new
Hi Derrell,
Am 15.06.2006 um 04:00 schrieb [EMAIL PROTECTED]:
> What I ended up doing was using the ISO-8601 format for
> transmission *to* the
> server. It's currently encapsulated in a "new Date( string>)" but
> possibly needn't be. There does need to be something that
> identifies it as
Great that it helped you.
You can try luck with the many select functions of QxTextField. Maybe it
is possible to move the cursor with these methods, too.
Sebastian
Thi Nguyen schrieb:
> Hi Sebastion,
>
> Thank you so much for the work around. I used suggestion #1 and it works.
>
> >> you
Hi Sebastion, Thank you so much for the work around. I used suggestion #1 and it works. >> yourTextField.forceValue(null);>>yourTextField.setValue(fixedValue); Another problem is though it works, the cursor get reset to the beginning of the string. How can I set it to end of the new st
10 matches
Mail list logo
