Jump to content

pyscripter

Members
  • Content Count

    974
  • Joined

  • Last visited

  • Days Won

    61

Posts posted by pyscripter


  1. 11 minutes ago, Anders Melander said:

    Ohwaitamoment!

    I think DevExpress use a custom property editor to get the events listed. I'll investigate.

    It works with Components if you call SetSubComponent or set csSubComponent.  Then Events are displayed.     e.g,

     

    image.png.abeab2ba62815cc15f4cf7730727d7bd.png

     

    So you can change TTestSub to inherit from TComponent.


  2. 1 hour ago, dummzeuch said:

    This passes the raw bytes received to the callback. Maybe it is possible to convert them to a string first? Or maybe call every time a line feed is received? Also, maybe the callbacks are enough so collecting the whole output is no longer necessary.

    This is roughly what I had in mind.

     

    Suggestions:

    • Have one event with an Enumerated parameter TExecOutput = (eoStdout, eoStdErr)
    • Pass to the callback only the newly added bytes in a TBytes.  They can be easily converted to strings using the ISshClient encoding.
    • Keep the output as is.  The user has a choice of not providing a callback.  The overhead is small.

     


  3. ISshExec.Exec was substantially revised and now works in non-blocking mode.

    • Are you using the latest source?
    • Are you using the latest linssh2 binaries?


    You can execute ISshExec in a thread.  Note that then it can be cancelled from the main thread using ISshExec.Cancel.

     

    Also you memory leak in TSshExec.Exec · Issue #18 · pyscripter/Ssh-Pascal has been fixed.  Can you confirm that?

     


  4. In the latest commits, I have added the ability to handle pointer fields and properties.  They are converted to python integers.

     

    So you could store for example an integer to the TTreeNode.Data.

    You could also store pointers to python objects using ctypes.   

    See for example the following:

    from ctypes import py_object, pointer, addressof, cast, POINTER
    
    # Create a py_object
    original = "Hello"
    py_obj = py_object(original)
    
    # Get its address
    addr = addressof(py_obj)  # e.g., 0x7f8b5c403020
    
    # Recover the py_object
    py_ptr = cast(addr, POINTER(py_object))
    recovered_py_obj = py_ptr.contents
    recovered = recovered_py_obj.value
    
    print(recovered)  # "Hello"
    print(original is recovered)  # True (same object)

    addr is an int type (python integer) that can be stored in Delphi pointer property. 


    • TTreeNode.Data is a Pointer property and WrapDelphi does not support raw pointer properties.
    • The only pointer property supported is PPyObject.   So if your wrapped class had a property declared as PPyObject it would work.  This also explains the error message.
    •  To be able to use the Data property you would need to modify the TTreeNode wrapper and do some custom wrapping of the TreeNode.Data property.   Alternatively you could save whatever info you need to store in a python data structure (possibly dict for easy access).
    • Thanks 1

  5. @Alex7691Good work.  It is useful to have a drop-in fast generics replacement.

     

    A couple of questions:

    • Is there an impact on code size?
    • I see a lot of code included that it is not directly related to generics.  (e.g. TSyncSpinlock, TSyncLocker, TaggedPointer, TCustomObject. TLiteCustomObject  etc.).  Are they actually essential for the rapid collections?   

  6. 28 minutes ago, bravesofts said:

    Microsoft’s WinUI 3, the latest iteration of its modern Windows UI framework

    Not quite.   See for instance Ohh...WinUI3 is really dead! - When can we expect the announcement? · microsoft/microsoft-ui-xaml · Discussion #9417

     

    The Microsoft strategy for GUI App development is utterly messed up:

    • WinForms
    • WPF
    • Xamarin Forms
    • UWP
    • WinUI3
    • MAUI

    And there is no longer a GUI designer.  You have to develop XAML in a text editor.  Discussion: WinUI 3.0 XAML Designer · Issue #5917 · microsoft/microsoft-ui-xaml

    • Like 7
    • Thanks 1

  7. 9 minutes ago, ToddFrankson said:

      (right hand side during install)

    This is the 64 bit IDE.   My problem was that the Win64 platform was not available.   After trying many things, I had to do a full uninstall/install to get the platform available again.


  8. 41 minutes ago, softtouch said:

    val contains 'testing' again, even it does not exist in python2.py.

    Of course it does.

     

    What you are doing is like running the following python script:

    exec("a = 1; print(a)")
    exec("b = 1; print(a)")
    

    a is created in the first statement and still exists when the second statement is executed.

     

    but if you do

    exec("a = 1; print(a)", {}, {})
    exec("b = 1; print(a)", {}, {})
    

    then the second statement raises an error.

     

    ExecFile has the following signature:

     

        procedure  ExecFile(const FileName: string; locals: PPyObject = nil; globals: PPyObject = nil); 

     

    If you provide no arguments for locals and globals, the code is executed in the namespace of the __main__ module.    If you do not want this to happen then you should provide empty dictionaries as arguments for the locals and globals parameters (or just the locals).  But then MainModule.VALUE will raise an error.

     

    Example code (not tested):

    var Py := GetPythonEngine;
    var NewDict := NewPythonDict;
    Py.ExecFile('python1.py', ExtractPythonObjectFrom(NewDict));
    var val := NewDict.GetItem("VALUE");
    
    NewDict := NewPythonDict;
    Py.ExecFile('python2.py', ExtractPythonObject(NewDict));
    val := NewDict.GetItem("VALUE");  // will raise an error since VALUE does not exist
    VarClear(NewDict);

     


  9. Indeed.   Python variables are reference counted.   As long as you keep a reference the python object it refers to is kept alive.

    When you have a statement like:

     

    var s:Variant :=MainModule.MYVALUE 

     

    s is a custom variant that stores the python reference.   The variable will be dereferenced, when s goes out of scope or you explicitly clear s (VarClear(s)).

     


  10. The following will not compile (error: class property accessor can be a class field or a static class method) :

     

      TTest = class
      private
        class function GetName: string; virtual; abstract;
      public
        class property Name: string read GetName;
      end;

     

    whilst the following does:

     

      TTest = class
      private
        class function GetName: string; virtual; abstract;
      public
        property Name: string read GetName;
      end;

     

    My question is that since you can have virtual class methods, why not properties that behave accordingly? 

     

    In SmallTalk, the first object oriented language, you have a distinction between:

    • instance variables (aka properties)
    • class variables (aka class properties - one per class including subclasses)
    • class instance variables  (one per class, subclasses can change the value)
×