Closed heldercorreia closed 9 years ago
I would rather have submitted this issue as enhancement, but I can't figure out where
I had to specify that
Reported by voxiac
on 2007-01-31 15:39:51
Hi voxiac,
Thanks for the idea.
As for enhancement, just chane Type-Defect in the label to Type-Enhancement (which
I'm doing right now)
Reported by ariya.hidayat
on 2007-02-03 22:23:00
I agree, variable names should be case sensitive. Accepting the sugestion, thank you.
Reported by helder.pereira.correia
on 2007-05-12 01:14:03
Accepted
Fixed in trunk, will be available in 0.8
Reported by helder.pereira.correia
on 2007-05-13 01:49:50
Fixed
Just noticed only one of the variables is stored in the settings and loaded back from
history. I'll fix this later, marking as Started.
Reported by helder.pereira.correia
on 2007-05-13 02:01:10
Started
In trunk, it is now possible to define variables "x" and "X", for instance. It is
also possible to define variables "PI", "Pi", "ANS", Ans" and so on. Only "pi" and
"ans" are reserved now. The only remaining issue happens when saving the settings:
if
variables "a" and "A" are defined, only one of them is going to be saved. For
portability reasons, keys cannot be case sensitive since Windows registry is not. So
we would have to take another path on this. I'll leave it like this for now, since
it
allows to use case sensitive variables in a session, and that was the issue. Marking
as "Fixed" and creating a new issue regarding the saving to settings problem.
Reported by helder.pereira.correia
on 2007-05-13 21:49:38
Fixed
Originally reported on Google Code with ID 23
Reported by
voxiac
on 2007-01-31 15:36:23