https://bugs.kde.org/show_bug.cgi?id=492100
--- Comment #5 from Edward Kigwana <ekigw...@gmail.com> --- (In reply to Gabriel Barrantes from comment #4) > (In reply to Edward Kigwana from comment #3) > > This has been working my nerves for a bit now. I imagine this simply needs > > an input state tracker. > > E.g. > > > > When one enters DEC 16 the tracker stores DEC. > > When one changes base to HEX, the input is updated by converting DEC 16 to > > HEX 10 and the state tracker then gets changed to HEX. > > > > At the moment the action above converts DEC 16 to HEX 16 which does not make > > any sense since DEC 16 != HEX 16. HEX 9 to OCT waits for a request for > > results before complaining about a syntax error. > > > > It seems we need an input regex for each mode as well so that invalid input > > is also not possible. > > is not that simple because inputs can be many things now, not a single > number that can be easily converted. > To convert 10+20+30 for example all the numbers will need to be found and > then converted and replaced in the string. Not even Qalculate is doing it... I agree it is not simple and only discussed the simple case as an illustrative case. If the input is restricted to one base then it is a matter of using a regex to capture the values and tokens. For the case of the current input it should then be straight forward to do the conversion and leave history alone especially since the history results indicate base. -- You are receiving this mail because: You are watching all bug changes.
