Thanks for catching that, Tobias. I’ve corrected the syntax.

Instead \”p1.DrawOval(0,0,…\” I assume it should rather read \”p1.Graphics.DrawOval(0,0,…\”

Thanks Paul!

Code doesn’t seem to format quite right when in comments. I’ve corrected the formatting as best I can.

Unfortunately, my code did not come across well. All those quote chars came prependd with an \”\\\”, which need to be removed again if someone copies my example.. Also, I wrote RuntimeErrror but meant RuntimeException.

Thanks, Thomas. Exception handling is a great way to easily check for any errors during this processing.

That is, of course, unless you opened the pictures folder in the OS X Finder and it created a hidden .DS_Store file in it, which it usually does.

Not even adding a simple check for even that common case is not a good way to teach examples to new users. Any example coming from Xojo should make an effort to teach people proper exercises, because Xojo users are usually those with even less experience than your common Xcode user (who usually do this by trade or at least learned it in school, whereas Xojo claims to make it easy even for newbies).

If you leave every such error checking as an \”exercise\” for the inexperienced user, you\’re not helping them, you\’re rather frustrating them. Just look at the forum, finding many questions related to the simplest cases of nil checking that users don\’t understand.

For those who read this and wonder what I\’m talking about…

1. Usually, when getting the FolderItem from a directory (folder) using \”f.Item(i)\”, that result should be checked for nil – which may indicate that the file is there but not accessible. This is a rare case, but it\’s safer to check for that if you\’re writing code you ever want to run as a built app and even give it away to others.

2. In the above code example by Paul, the easiest way to catch all those possible errors is to add a try/catch block inside the loop, like this:

Try
Dim newPicFile As FolderItem = newFolder.Child(f.Item(i).Name.Replace(“.png”, “.jpg”))
Dim p As Picture = Picture.Open(f.Item(i))
p.Save(newPicFile, Picture.SaveAsJPEG, Picture.QualityHigh)
Catch exc as RuntimeException
‘ ignore any errors
End Try

How you’ll implement it depends on your needs, but the HiDPI webinar has example downloads based on this blog post which you might find helpful.

Thanks

Xavier is so X-Men!!

I’m obligated! So I’ll put all of my special super powers on the task!

Javier

Be sure to refer to the System Requirements (http://developer.xojo.com/system-requirements) and post specific questions and/or errors to the forum (http://forum.xojo.com).

i have a problem ,installing xojo in ubuntu 15.10 pls help me

I think it could be done by splitting the Text value of the TextField into different values. Based on the cursor position you can determine which word is being edited. A popup menu can be launched to show several autocomplete possibilities.
By knowing the offset and length of the edited word you can figure out the what part of the TextField needs to be highlighted.

Additionally it would be cool to keep the initial casing. Right now, when I enter the word Object (with uppercase O), it would be nice to keep the O uppercase. Maybe an additional array of upper/lowercase states would be needed.

But, I must say, this is one of those little diamonds I find in the Blog section 🙂

Lots of jobs will go the way of the DoDo Bird in the medium term with AI, robotics and automation, but it will be a while yet before they can program themselves. So programming can put food on your child\’s table in their own house for years to come, and empower new business ideas too.

Self-study is ongoing with programming so it\’s the right way to get started, and even parents can do it too. What more could you ask?

Edwin, your are right. Multiple words would be very nice and to create a Subclass of TextArea…hope Xavier is still working on it 🙂

What concerns me is not necessarily technical. This is just the lack of warning that bothers me.

–“Don’t trust user input”–

Hi Joseph, I’ve updated the post with a current video of the Xojo iOS QuickStart!

XojoScript code is sandboxed. What risk/vulnerability with this simple example concerns you?

What version of Xojo are you using? I am not seeing such an error on 2016r2 or 2016r1 on either OS X or Windows.

in app event handlers CLOSE calling preferences.save raises the following exception: “there’s more than one item with this name and it’s not clear wich it refers”

thanks