• Daniel Pozmanter

    A fellow named Rene emailed me with a very useful request:  autocomplete in the prompt.

    Problem is, although it was a simple matter to rework the code so that it works in the prompt, hitting enter causes the prompt to get all excited, and act like I was entering a new line of code, instead of just completing a word.


    What I need to do is figure out a way to keep this from happening before I can release the next version of the plugin.

    • Franz Steinhaeusler

      Hello Dan,

      is it possible to restrict the code completion to
      python files? (else I get always unwanted completition
      in txt or c file and unwanted delays).

      def OnAutoComplete(event):
      =>if DrFrame.txtDocument.filetype != DrFrame.txtDocument.PYTHON_FILE:

      with this new constant should do the trick.


    • Daniel Pozmanter

      Thanks.  I should get to this.

      What I REALLY need to do is overhaul the update namespace code.  This is WAY too slow.

      I think I will rewrite the way this plugin gets the info for both calltips and autocompletion.

      I am thinking of adding a feature to allow users to toggle autocompletion and calltips on and off.  (This way you can only have it active when you want it).

    • Franz Steinhaeusler

      Yes, you're right; it is way to slow and this is
      very annoying.

      Hm, in pycrust, it is very fast.

      I like the idea with the toggle mechanism.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks