2018r1

  1. ‹ Older
  2. 4 months ago

    Gavin S

    Jan 12 Pre-Release Testers, Xojo Pro UK
    Edited 4 months ago

    @Joost R And, we have no guarantee that flickering will be zero at the end. And, it's possible that we are going to pay the price with a loss of performance.

    We shall see. I have high hopes for 2018r1 and after years of flickering on Windows, I'm happy to wait until it's ready.

  3. Christoph D

    Jan 12 Pre-Release Testers, Xojo Pro

    An advantage (no flickering) usually also gives a disadvantage (performance). ;-)

  4. Sascha S

    Jan 12 Pre-Release Testers, Xojo Pro Germany/W'haven

    @Christoph Dnbsp;Vocht An advantage (no flickering) usually also gives a disadvantage (performance). ;-)

    Not if the first solution was just a poor one

  5. Louis D

    Jan 12 Pre-Release Testers, Xojo Pro Montreal, QC, Canada
    Edited 4 months ago

    The same happened in previous releases regarding typing speed and was corrected for most use cases in the final releases. Let's give a break to Xojo developers.

    edit: typing error

  6. Jürg O

    Jan 12 Pre-Release Testers, Xojo Pro

    @Julia T One would think that this particular bug fix would warrant a more or less immediate release

    One would think that such a big change in the "core framework" would warrant for a long Alpha/Beta phase... as it is likely to have many side-effects. ;)
    I'm happy to give Xojo and all PreRelease testers enough time to do this, and to get this right.

    Feel free to get access to the PreReleases and try it yourself. If it's already in good shape - fine. More likely you'll notice a couple of things that don't yet work - so they're glad to get your Feedback.

    I just don't remember how one does get access to the PreReleases...?

  7. Sascha S

    Jan 12 Pre-Release Testers, Xojo Pro Germany/W'haven

    @Jürg O I just don't remember how one does get access to the PreReleases...?

    Just ask Xojo Inc. for it ;)

  8. Julia T

    Jan 12 Sandy Hook, Connecticut

    @Jürg O One would think that such a big change in the "core framework" would warrant for a long Alpha/Beta phase... as it is likely to have many side-effects. ;)

    In my enthusiasm for this to be finally fixed I assumed that " Implemented and Verified" meant that it's been tested and is more or less ready, but maybe that's not a valid assumption. While I know that nothing is ever simple, Julian's description of z order as the root cause does make it seem like the fix might be relatively straightforward (and with little or no performance hit). Xojo reviewed the case in July and declared it "implemented" on Dec 6.

  9. Julian S

    Jan 12 Pre-Release Testers, Xojo Pro UK

    I think I put in about 10 tickets the day the alpha was released, some are resolved and the rest are being worked on as I see their Last Modified date alter in feedback even though I can't see what is being said as its Xojo internal chatter.

    I can't talk about the pre-release version in General as I once got chastised for showing the xojo splash screen with some alpha text on it =S

    The longer it takes for 2018r1 to be released the better it will be :)

  10. Louis D

    Jan 12 Pre-Release Testers, Xojo Pro Montreal, QC, Canada

    As they say: what happens in the alpha remains in the alpha. ;)

    On 2018 R1, I think we can safely say something like: I like what I see of it so far. It is worth waiting for it.

  11. Julian S

    Jan 12 Pre-Release Testers, Xojo Pro UK

    hehe, first rule of Xojo club is don't talk about Xojo club ;)

  12. Jürg O

    Jan 12 Pre-Release Testers, Xojo Pro

    @Julia T Julian's description of z order as the root cause does make it seem like the fix might be relatively straightforward

    Well, if you join the "Xojo PreRelease club" , you'll find out more about that. There's a whole lot more to the story than just z-order. And I like it, too :)

  13. Axel S

    is not verified Jan 12 Europe (Germany, Erfurt)

    @Jürg O Well, if you join the "Xojo PreRelease club" , you'll find out more about that.

    The conditions for joining the club unfortunately exclude some users.

    You have filed a Feedback case. If you haven't filed a Feedback case before, but want to apply- go ahead and do so now.

    There is no "howto file a Feedback case without a working Feedback App" :(

  14. Greg O

    Jan 12 Xojo Inc Somewhere near Raleigh, NC

    @Axel S There is no "howto file a Feedback case without a working Feedback App" :(

    It’s called “work with Greg and see if we can figure out why you can’t run Feedback. “

  15. Axel S

    is not verified Jan 12 Europe (Germany, Erfurt)

    starting Feedback in Linux (Ubuntu 64bit)
    it's just a short flash of the window then it's over and the only message i get in Terminal is 'Cancelled'

    it certainly has to do with the HTMLViewer, I quote myself
    (from https://forum.xojo.com/44778-feedback-utility-not-working-on-linux-mint-18-2-64bit-with-xojo# )

    maybe my problem is the htmlviewer in gtk3 that crashes (hard) when using "http://"
    I can show local files only ("file://")

    ldd ./Feedback > /tmp/ldd_Feedback.txt

    linux-vdso.so.1 => (0x00007ffe880ed000)
    XojoGUIFramework64.so => /opt/xojo/feedback/./Feedback Libs/XojoGUIFramework64.so (0x00007f94e4c17000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f94e484d000)
    libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x00007f94e4202000)
    libgdk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x00007f94e3f4d000)
    libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007f94e3d28000)
    libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007f94e39a0000)
    libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007f94e378a000)
    libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007f94e357d000)
    libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007f94e335b000)
    libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007f94e3047000)
    libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007f94e2dfb000)
    libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f94e2b51000)
    libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f94e290e000)
    libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f94e26bb000)
    libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f94e23aa000)
    libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f94e2070000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f94e1d67000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f94e1b63000)
    libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007f94e1961000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f94e1744000)
    libc++.so.1 => /opt/xojo/feedback/./Feedback Libs/libc++.so.1 (0x00007f94e1393000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f94e117d000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f94e6f78000)
    libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007f94e0f79000)
    libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f94e0d73000)
    libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f94e0b69000)
    libXinerama.so.1 => /usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007f94e0966000)
    libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007f94e0756000)
    libXrandr.so.2 => /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007f94e054b000)
    libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007f94e0341000)
    libXcomposite.so.1 => /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007f94e013e000)
    libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007f94dff3b000)
    libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f94dfd29000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f94dfb0f000)
    libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f94df8ed000)
    libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f94df6d2000)
    libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007f94df474000)
    libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007f94df1cc000)
    libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007f94defa7000)
    libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007f94deda3000)
    libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007f94deb99000)
    libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f94de977000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f94de76f000)
    libthai.so.0 => /usr/lib/x86_64-linux-gnu/libthai.so.0 (0x00007f94de566000)
    libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f94de33d000)
    libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f94de135000)
    libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f94ddec5000)
    libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007f94ddc9f000)
    libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f94dda9b000)
    libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f94dd895000)
    libdatrie.so.1 => /usr/lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007f94dd68d000)

  16. Alexis C

    Jan 12 Pre-Release Testers, Xojo Pro Puerto Rico, USA

    I hope this version com with WebListBox col editable like desktop one

  17. Tim P

    Jan 12 Pre-Release Testers, XDC Speakers
    Edited 4 months ago

    @Alexis Cnbsp;Lugo I hope this version com with WebListBox col editable like desktop one

    It would be far more prudent to learn HTML and Javascript and create your own control than to continue waiting.

    I wouldn't think this is on the to-do list for now. According to the XDC Sessions List there is a new Web Framework 2.0 in the works. They announced with the new Xojo framework that they wouldn't be making changes to the old one except for critical fixes. I would think the same applies to the web framework.

  18. Michel B

    Jan 13 Pre-Release Testers RubberViews.com

    It is far from simple to make the WebListbox analogous to the Desktop one. It is much more than a dash of JavaScript.
    For the time being, the best solution seems to be
    GraffitiWebGrid from https://graffitisuite.com/features/web-edition/

  19. Alexis C

    Jan 13 Pre-Release Testers, Xojo Pro Puerto Rico, USA

    i have GraffitiWebGrid and lost my money on it i no same as the one with xojo.

    i talk to customer service like 1 year a go it se to me is goint to be done on 2018 so i renew my lic if this is no done in 2018 then money back.

  20. Louis D

    Jan 13 Pre-Release Testers, Xojo Pro Montreal, QC, Canada

    Perhaps the new web framework may include something like that, but I would not bet my business on it. A new framework is a lot of work. The new framework introduced with IOS support is proof that a new framework is far from the solution to all issues. If it were my business, I would work on the themes and options to make the Graffiti weblistbox resemble as much as possible the weblistbox, if having an editable listbox is of paramouint importance.

    You can also create your own with container controls and text fields (and even other types of controls). I experimented with such a solution for a proof of concept application that I am building. We can get very close to the appearance of the weblistbox and retain full control on which fields (columns) are editable. I suggest using an underlying array, because adding as many rows as there are data rows can become a resource and performance issue when the volume of data is large. I ended up keeping the number of rows constant and simply showing different portions of the underlying array when the user moves the scrollbar. Much care must be taken to index correctly the data, such that the correct array element is updated when data is edited in the self made listbox. But it works!

    This is one thing that I like of Xojo. The tools are there and it is relatively simple (relatively is the key word) to create new complex controls as we need them.

  21. Alexis C

    Jan 13 Pre-Release Testers, Xojo Pro Puerto Rico, USA

    pay for more plug-in with money y pay xojo lic.

or Sign Up to reply!