#45 OLEObject - allow determining how conversions take place

v3.1.2
closed
None
5
2012-08-14
2005-02-23
No

In the present implementation the conversion of byte
arrays to Object REXX is carried out such, that an
Object Rexx array is created and each byte's decimal
value is assigned to the appropriate slot.

Getting picture data from Windows as byte arrays can
encompass a million or more bytes, causing Object REXX
to use many resources (especially time, where one needs
to wait for many seconds, sometimes even a minute or
more!).

Instead I would prefer to get byte arrays as regular
Rexx strings. That should be less resource binding and
much quicker.

It also may make sense to allow determining how
conversions from Rexx to Windows should take place,
i.e. the order of Windows datatypes which Rexx
datatypes should be converted to (e.g. Boolean, Byte,
...).

Discussion

  • Mark Miesfeld

    Mark Miesfeld - 2007-02-13

    Logged In: YES
    user_id=191588
    Originator: NO

    Rony,

    If you would attach a simple example of what you are talking about, I'll take a look at this request. I don't off the top of my head, know anything that returns picture data, so I don't know where to start with this.

     
  • Rick McGuire

    Rick McGuire - 2007-04-05

    Logged In: YES
    user_id=1125291
    Originator: NO

    Mark, I think this might have been addressed by your OLEVariant changes. Close this out if so.

     


Anonymous

Cancel  Add attachments





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

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks