how can you replace these ?
how do you detect clics in a webcanvas ?
I hope it will be in the next 2020 version …
No way of replacing, no workaround but IDE without functionality…wlcome to the club.
From the blog post I keep trying to get people to read:
There are two reasons that it might not make sense to convert a project at this time. The first would be if this project is both quite large and a short-term solution. If you don’t see it being in use in 5 years, it might make more sense to continue to maintain it in 2019r3. The second reason would be if your project currently relies on some function of Web Framework 1.0 that does not exist in Web Framework 2.0. Primarily this would be mouse events for Label, Canvas, MapViewer and ImageViewer. If your app depends on mouse events for these controls, wait for a future release.
2 Likes
so I will wait. I’m still in 2019r11 by the way, hopping to move to 2020 but still not the right time. it will soon be 2 years paying for updates and using none …
<https://xojo.com/issue/61529>
<https://xojo.com/issue/61528>
I’ve started a new web project for a customer early this year, knowing that web 2 was coming. now I see that any work made in web 1 will give a lot of work to update to web 2. so as a fresh project I will start it in web 2, but I can still give no vague delay to my customer…
and you know what, my really simple web project has mousedown and keypressed events !
2 Likes
STOP paying for things you never use
You get no discounts for doing so
You get no brownie points for doing so
When a new version comes out read the release notes. Try it for free and see if it does what you need. If so THEN buy it.
7 Likes
that is called sponsoring and be proud that you not gave microsoft your money. 
maybe you have a big benefit in future because your money made things possible.
i guess until end of this year there is much to do for web 2.
missing events
also possible that xojo devs have other solution approaches in mind.
1 Like
If you have money to give away and not get anything useful in return I know a few other developers that could use your sponsorship 
there will surely no licence renewal if I don’t have a usable update very soon.
yes it’s kind of sponsoring, I want xojo to make a good product so I pay hopping to get one.
Buy based on what they have available - not what you might get in the future.
that’s a matter of opinion
what is useful and what not
for each person.
if me had finished all my project ideas i would be probably rich today but i had a lack of developers.
Would you pay Mercedes-Benz today for a car ?
I doubt it
You would pay for a car they can sell you today that you can drive home even as long as it has the things you want.
Paying & hoping you one day get a version that has the things you need is not different than that car. The only difference is the amount of money involved.
In that case do the same as you would with the car. Take it for a test drive and IF it has what you want then buy it and be happy. If not keep the money until it does.
That said I’m sure Mercedes would love to have you pay them money in the hopes they build the car you want. But if not I’m sure they appreciate your sponsorship anyway.
2 Likes
When <ou are acting in this market you have to deliver if you get money. This (xojo) is not an open source project, it is a commercial Software what you have to pay for to be able to build. What is going on now is another problem: xojo is not doing what they said. The Major Version instead of end of 2019 as public beta is September 2020 as public beta cause it is not even reaady with the features they wanted to have.
If you are making cash with a software you should be able to do what you are promising. I am not speaking about Android. Cause that is a Project. But I am speaking about Software what they wanted to release in 2019 and released near the end of 2020 and where not giving a release what was really working. The errors in the IDE are still there and never a reaction is coming up wich is showing that there will be a change.
When and if someone is selling something he has to accept that his customers rely on that what he is telling what his product is and will be in near future.
we are all focusing on saving money but i also see the people behind a product,
they need a good income and a company have many other expenses.
its not possible to say the xojo product is finished and then let them all goto home (quitting).
if you buy a cheap asia comparable car than potentially at the expense of staff (low wage).
the price relationship is very different at each country.
for me it must fit the price / utilize ratio and sure a positive bank balance.
about “Mercedes-Benz” in past i think it was money in and quality out from people that have enough $ or more.
I know this VERY well
I was one for a decade
Software is almost veer finished as the OS changes , apis changes, etc
But, any single release should be “fit for purpose”
And then you obtain a license and use that version more or less as is for as long as you want
That’s the agreement we have with Xojo
I dont pay them for what they make tomorrow or a year from now the same as I dont pay Mercedes or anyone else for what they may or may not do tomorrow
sure.
we all make our own value judgements about whats an appropriate price to pay for what I need
but to pay for something you arent getting ?
if someone stuck at older version because of some projects or for whatever reasons its unpleasant.
about missing events i think this will be solved after more debate soon.
this 2020 release was long overdue so i am happy that it appear early.
people on windows machines are all almost stuck on r2017 !!!
I’ve been using 2019r3.1 on ONE client project
Although thats not on my real machine but a VM
Its … OK
I’ve been using Xojo on Windows almost exclusively for years and using the latest version for development practically as soon as released. I can’t imagine being stuck back at the 2017 version. I’ve been using 2019 R3.2 since it was released. Most everything I do these days is internal Web apps. 2020 R1 so far is the 1st version in years I have significant disappointment over. Rebuilding existing apps is a nonstarter due to things like styles and the mousedown/keypressed events issues. Anything I might try in 2020 R1 will have to be experimental. I’ve been waiting for Web 2.0 for over 2 years since it was first announced in Denver but this 1st release is not ready for me to use for production applications.
1 Like
Very risky. Sometimes you upgrade something and discover something breaking. After 2016R3 people had all sorts of problems in screen and printer due to the complete rewrite of the graphics system. Later HTMLViewer started leaking and accumulating zombie processes… I’ll never be an early adopter. Won’t write API2 until stable, for example.
1 Like
Well, not ready for you nor for anybody aiming to do anything more deeper than a hello world.
I’m sure it will be awesome in the (hopefully near) future, but wow.
3 Likes