[texworks] SCRIPTS: TW.getItem() returning everything lower case?
Paul A Norman
paul.a.norman at gmail.com
Wed Dec 8 22:48:10 CET 2010
>Could you test with a list of strings that contains no (entirely)
The problem is that fickly, but most often, Uppercase letters are
treated/converted to lower-case
In the graphic in the last email,
The results of progressively going through the array are shown.
The array that I went carefully through with the item box one by one was
And the corresponding results of each progressive use of the item box were ..
tiny scriptsize footnotesize small normalsize large large
large huge huge
I have kept the previous compilations of TeXworks, and have tried 0.3
rev 606 and this problem is **not** found there at all.
It does happen in 0.3 ver 649
It does happen in 0.3 ver 684 and so up...
On 9 December 2010 08:23, Stefan Löffler <st.loeffler at gmail.com> wrote:
> On 2010-12-08 00:36, Paul A Norman wrote:
>>> The only
>>> thing that has changed (at least in my Windows builds, compared to
>>> before) is the version of Qt.
>> What version of Qt is being used at present please - 4.7 - as in help about?
> Yes, Qt 4.7.0.
>> Its fickle - sometimes it happens (mostly), sometimes it doesn't, in
>> successive calls to the script - only occurrence of this that I am yet
>> aware of in anything that I am using on this computer at present.
>> Here is an image showing what repeated running of the script shown
>> does, as described in the comment line. The results were being
>> inserted in the Scirpt's file in Tw as it was used.
>> The message box in the image should show: Huge
> Could you test with a list of strings that contains no (entirely)
> lower-case entries? So we can determine if this is actually a problem of
> case, or of selecting the wrong item ("huge" instead of "Huge")?
> As you already saw in the code, the getItem function is basically a
> direct wrapper around the native Qt function QInputDialog::getItem. So
> unless something weird happens in passing data to/from scripting, this
> seems very much like a Qt bug (if any) to me.
More information about the texworks