As in: press A, press B, release A, release B: in that sequence of key events, you want both A and B to be recognized as typed characters, even though B was pressed before A was released. Rollover refers to the behavior of electronic keyboards that allow multiple keys to be down at the same time. (05-02-2022 09:49 AM)jonmoore Wrote: But what's n-key typing? Is this similar to my request for a proper alpha keyboard? In a nutshell, the UI structure in my apps is not the way iOS apps are really supposed to be structured (Free42 is my first iOS app, I didn't know any better.), and while I have been able to get away with that on the various iPhones and iPod touches, it starts to cause real problems when trying to support the iPad properly.
#PCALC NEGATIVE SIGN KEYBOARD FOR FREE#
I think I'll get those features essentially for free when I turn on iPad targeting in the Xcode project settings, but there are some issues having to do with the Free42/Plus42 views are managed. What the iOS version does with sliding sideways is not the same thing as Slide Over on the iPad, I think, and there's also Split View. Thanks for highlighting this as I probably would have missed it.
#PCALC NEGATIVE SIGN KEYBOARD CODE#
If know of a short code that can do this elegantly please edit this answer.(05-02-2022 09:49 AM)jonmoore Wrote: Slide-over views are a classic iOS UX pattern and perfect for the print view on Plus42. What I advocate is the use of siunitx for fine control over typesetting of numbers.īesides I wanted to have a code that works also for superscripts (for the exponent) (using hard code raisebox produces weird effects on exponents or small fractions). It is just an example to show the difference and I didn't want to clutter the answer with more code. Keep it simple.Īs a bonus the code for TI-84 buttons \documentclass^-, this seems quite extreme. you don't make a difference in handwriting, why should you make it complex (and I dont mean complex numbers :-) in typing.
I don't see any reasons to make that difference in typing. In order to show you the error on the calculator, there is a difference between the 2 characters on a calculator. But if you typeģ + -5 as a minus, than the calculator will jump to the error "-".
So you can type:ģ + -5 and the calculator will not make a problem of it. The minus on the TI-84 as a negative number can be used in the input without brackets. Luatexbase.add_to_callback("mlist_to_hlist", replace_unary_minus, "replace_unary_minus") Return node.mlist_to_hlist(head, displaytype, need_penalties) Node.insert_after(head, v, py(unary_minus))
If n and n.id = 31 and n.fam = 2 and n.char = 0 then If q and q.id = 16 and (q.subtype = 5 or q.subtype = 7 or q.subtype = 8) then return true endįunction replace_unary_minus(head, displaytype, need_penalties) If p.id = 16 and ((p.subtype >= 1 and p.subtype <= 6) or p.subtype = 8) then return true end If not v or v.id \string~= 16 or v.subtype \string~= 4 then return false end Unary_ = py_list(tex.getbox(\number\scriptscriptraisedminus)) Unary_minus.scriptscript = node.new(16, 0) Unary_ = py_list(tex.getbox(\number\scriptraisedminus)) Here is a LuaLaTeX approach that discovers unary minuses automatically (but the \raisebox doesn't work for a reason I don't understand): unary_minus = node.new(15)
0 kommentar(er)
