i have a plot with a lot of textboxes (about 1000, count still growing). and if i try to change the name of an ID it need 1 minute until i can work on.

i think the check if the ID is free need this time. but can’t this done in background?

3 answers

Hi Yasofies,

It is hard to believe that changing the ID needs so long time, althought the plot has so many textboxes.

I wonder if there is any error happens during that process, which cause additional time to change the ID. Could you send us your plot file ( That will help us to locate and fix the problem ASAP. If the plot is confidential, may be you can send the log file for us to check. Thanks in advanced.

If we confirm the problem is just related to performance, we will try to optimize it, or try to put it in the background and avoid blocking the process.

  1. I will try to create a new Plot with the same Problem.

    The reason for the textboxes is that i need a DB. i try to simulate a browser game. there for i need a table with buidingcost for each building and buildinglevel.

    mail will be out soon.
  2. Perhaps i can do the same with the element "Table" this would save a lot of IDs.

Hi Yasofies,

Thanks for sending us the sample plot file. I just checked it and I found that renaming the textbox on first and last page takes the same time (about 20 seconds, which is long).

In order to change the id of an element, ForeUI needs to update its references in all expressions, that is a time consuming task. After debugging, I confirmed that more than 90% of time is used to update the expression defined in elements’ behavior. I reviewed the algorism and I think there is not so much room to optimize it, at least under the current architecture.

We have seem many big plots, some of them even have 100+ pages. But we haven’t met a plot that has so many actions defined before. In your sample plot file, there are about 800 textboxes, and each of them has two event handlers (which contains 5 parsable expressions). That means ForeUI will check 4000 expressions and update the references inside. That will be extremly time consuming.

if the 1000+ text boxes are really needed in your prototype, try not to define actions in each of them, or at least make the actions simple (consider making good use of Custom Events). ForeUI is not designed to simulate solution with complex logic, it is still a UI oriented prototyping tool.


right. i meaned before creating the second and the third page. i needed on the first page only 2 seconds.

the definition of action is a MUST cause this is the way i can point on elements. i ask every every element have you ID XY if yes, tell me ….

but i found a way to replace the text boxes with table. i have no idea why i haven’t tride that before.

(hope you can understand my english)

  1. Yes using table should be a better approach :-)

This question is now closed