Region.type() conflict with builtin type() function --- workaround

[anatoly techtonik]

*** workaround

the builtin type function can be called using __builtin__.type().
(You would also need to import __builtin__)

... and you could use isinstance()

----------------------------------------------------------------

I've just realized that Region.type() is imported in global scope and shadows builtin type() function, which makes debugging harder.

[RaiMan (raimund-hocke)]

Yes, that is really an API design mistake.

I would suggest to deprecate type() and implement a new typing feature that eliminates the keyboard layout and special character problems of type().

[anatoly techtonik (techtonik)]

Region.input() ?

[RaiMan (raimund-hocke)]

nice try ;-)

already in use as input dialog feature :-(

what about keyStroke() or keyPress() or typeKeys() .....

[anatoly techtonik (techtonik)]

Something with 'key' in its name assumes that the argument is some key identifier, something like scan code that is obviously different from text or char. Perhaps it is better to decide on the arguments first. It may happen that the action will be called enterText() or keySequence() depending on the arguments.

[RaiMan (raimund-hocke)]

good idea --- fully agreed.

[Tsung-Hsiang Chang (vgod)]

btw, the builtin type function can be called using __builtin__.type().
(You would also need to import __builtin__)

[RaiMan (raimund-hocke)]

thanks for the reminder ;-)

I had some "feeling", that you mentioned a workaround already.

I only took the chance to talk about the need to revise and develop the type/paste stuff as such ;-)

[anatoly techtonik (techtonik)]

I used another workaround for type check - through isinstance()

[anatoly techtonik (techtonik)]

BTW, the "paste" stuff seems a lot like a solution.

paste("text') - creates some kind of buffer with 'text' inside and then pastes it into control.

[RaiMan (raimund-hocke)]

paste simply simulates a ctrl-v internally. the buffer is the clipboard, which gets corrupted this way.
 ... and after the first time you use paste(), Env.getClipboard no longer works.

so, still some things to improve ;-)