Welcome to Koda bug tracker!

At the moment you can post bugreports or suggestions anonymously. But registered users have some benefits: attaching files, commenting, voting, tracking tasks e.t.c.

Due some asshole started spamming tracker, now (at least for some time) it’s not allowed to create anonymous tasks. Sorry for unconvenience.

In edit fields you can use DokuWiki syntax for formatting.


FS#306 - Generate Code button | Save to file

Attached to Project: Koda
Opened by Chris Haslam (c.haslam) - Thursday, 23 June 2011, 17:19 GMT+3
Type Bug Report
Category Application
Status Unconfirmed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


  1. I created a form in the Design Area but did not save it.
  2. I clicked the Generate icon.
  3. At the Code window, “Save to file” showed. I clicked on it.
  4. Koda said “Your current form is not saved. In order to use the Update function, you must save the form before saving the script”.

But I wasn’t using the Update function, so I suggest that “In order to use the Update function” be dropped from this messagebox.

BTW Yesterday I met a message that contained “it’s”. There is a growing tendency in English usage to use “it’s” rather than “its”. Correct usage is:

  • “it’s” is the abbreviated form of “it is”, just as “wasn’t” is an abbreviated form of “was not”. The “‘” shows that one or more characters are missing.
  • “its” is an exception to the general rule that “‘s” indicates possession, as in “Koda’s design”, which is exactly equivalent to “the design of Koda”
  • “its design” is good English.

There are cases in computer-eze where I do use “‘s” to indicate a plural because it seems to be the only way to be clear. An example: “there are five #include’s in my script”. :-)

This task depends upon

Comment by Admin (Lazycat) - Friday, 24 June 2011, 15:22 GMT+3

Seriously, I don't like the design of whole "save to file" thing in this dialog... But while it is as is, why you think it should be dropped? You can save form without name. But clearly can't use Update function. Maybe "In order you want to use the Update..." will be more clear?

About it's/its - got it, hope I'll not forget about in future :-)

Comment by Chris Haslam (c.haslam) - Saturday, 25 June 2011, 08:43 GMT+3

My lesson regarding it's is one that many native English-speakers need to learn!

To answer your question, here is a long version of what the message box might say:

This form has not been saved to a file.
Because the Update function identifies the code to be updated by searching for a form filename in the script, a form must be saved before the script can be updated.
Save the script?

This is a very long caption for a message box!

Here is a shorter caption:

Your form has not been saved. Should you wish to use the Update function later, you need to save the form before saving the script. Save the script?

I think the longer version belongs elsewhere, e.g. in the doc.

I still think that identifying the script at start-up is the wrong time to do it. I realize that the hint in the Form List will not show the filespec of the script until after an Update has been done. But that's OK. I am thinking about the logic for identifying the script when the user chooses Update.

The Update function is proving very useful in writing the styles dialogs.