Xojo webinar how to#
Xojo webinar full#
Xojo webinar code#
Xojo webinar windows#

VB6 is an ancient language by modern standards. While the two development tools use a BASIC language that’s about as close as they get. There is no easy solution to get your VB6 application to work in Xojo. And again, because VB6 doesn’t do some things well, like control subclassing, you might actually be better off rewriting the user interface from scratch in Xojo anyway. But given the huge diversity of 3rd party controls for VB6 you will have to work at converting them to standard Xojo controls. It’s much easier for a human to look at the VB6 code, figure out the Xojo equivalent and use the Xojo-way of doing things.Īt best, the VB Migration Assistant will convert your UI for you.

Xojo webinar code#

Sure, there are rules you could employ to convert code but in my experience the converters create more work for you in the long run. It’s very hard to convert the intent of the original programmer. Not converting code is actually a good thing because no conversion tool is perfect. It isn’t a perfect tool and does not convert any code for you. The first thing many people do is look at the VB Migration Assistant from Xojo. The problem is that Xojo isn’t VB6 and most of the things that take huge workarounds in VB6 are almost laughably simple in Xojo. The IDE’s look a lot alike and the languages at first glance are pretty similar. Don’t convert your app to Xojo, rewrite it in Xojo. In it worked this way.” I’ve heard this complaint so often that I ignore it. Why? The complaints are varied but they usually say things like “ doesn’t work right. New Xojo developers are often sorely disappointed with Xojo when first coming to the language.

Xojo webinar full#

ReportPF will now extract Styles from the report definition file.īKS Shorts with the Report Designer is $300 and you get the full source code.

In PAF_ if there is no DefaultStyle we create one.Reconfigured Demo window to break between Report Designer stuff and older code-only stuff.

Xojo webinar how to#

Added a new example of how to print directly to printer without having to use the viewer.The Styles Editor now allows you to delete multiple Styles at a time.Fixed an issue where the Default Style wasn’t getting passed to the generated report.As a Text Item or Field Item are put on a report it will automatically use the “Default Style”.Rearranged UI on ccPAF_Filter (Filter Data) to make it a bit more obvious.Example of use is to have line numbers on your report without having to do it in SQL. This lets you get how many times this band has been shown. Added SC_GetCount in the Band XojoScript editor.The second, is an example of how to print directly to a printer without having to go through the viewer. The first is using the SC_GetCount Band Script to set row numbers. We added a couple of new examples based on user feedback. Add this to any Band Script to modify a TextItem. One of the new items is the ability to show a Row Number on any band using the new SC_GetCount XojoScript. I will be the showing off Shorts at the next Xojo webinar on February 2nd at at 1:00 PM (GMT-5:00) Eastern Time (US and Canada). A number of bug fixes, changes, and additions were added. We released version 1.5.3 of BKS Shorts today. What say you my Xojo developers? Do you like to turn Implicit Instance off or do you even care? Simply put, Implicit Instance is evil and you should avoid using it – especially in larger applications. It is my not-so-humble opinion, that leaving ImplicitInstance = true is bad for you as a Xojo programmer. Either way, I don’t think the burden is too high. To solve this you can either iterate through the existing windows/pages to find the one you’re looking to reuse or simply close it as you open your new one. For short lived apps this usually isn’t a problem. Depending upon your application this may cause long term memory issues especially as the app gets a collection of pages that are no longer used.

Xojo webinar windows#

The drawback, if you can call it that, to having Implicit Instance = false is that as you call new windows or web pages you haven’t done anything to the old ones. For i as integer = 0 to session.PageCount- 1ĭim w as WebPage = Session.PageAtIndex(i)