GUI-O Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • F

      Gui-0 Live Designer V0 .0.16 - Transfer to Device

      Frequently Asked Questions (FAQ)
      • • • Fred Neuman
      3
      0
      Votes
      3
      Posts
      130
      Views

      K

      @Fred-Neuman said in Gui-0 Live Designer V0 .0.16 - Transfer to Device:

      Gui-0 Live Designer V0 .0.16 - Transfer to Device
      The command “transfer to Device’ is quite useful to transfer a design toward android device:
      \Android\data\com.guio.guioapp\files with the PRO version.

      It works fine with Widget that has no customisation (with default value) since the data sent is shorter. Although If I customize a widget with some features, it add some double quotes and backslash to the Widget parameters. In my case it prevents the Transfer to my Device Samsung. Example for Spinnable list Widget:

      |TU UID:tu3 X:50 Y:50\r\n - Transfer to Device works fine

      |TU UID:tu0 X:18 Y:55 FGC:#FF0000 FSZ:5 DAL:"2,3,5,7,9,11,13, "LI:2\r\n"

      Won’t transfer to Device - I suspect \” Li to be the cause

      I would say that the issue occurs with others Widgets, but i did not make a test on everyone
      Regards

      Hi,

      sorry for being quiet for so long.

      I have checked this and the problem seems to be when using parameters that expect internal quotes (e.g., DAL:"2,3...").

      Since the "transfer to device" feature uses the EXTF component (file read / write) of the GUI-O, the problem lies there.
      I will try to fix this issue ASAP.

      Best regards,
      Kl3m3n

    • F

      Cannot send command through Gui-o designer on Tcp/Ip connection

      Frequently Asked Questions (FAQ)
      • • • Fred Neuman
      4
      0
      Votes
      4
      Posts
      147
      Views

      K

      @Fred-Neuman v0.0.16 also includes this fix.

      Best regards.