So in other words, anything might've been the cause here and the fact the move to different drive solved the issue may very well be completely irrelevantA clean on as I have been planning to do that for some time.
So in other words, anything might've been the cause here and the fact the move to different drive solved the issue may very well be completely irrelevantA clean on as I have been planning to do that for some time.
Yes. Recursive (searching subfolders as well as the specified folder) should be optional and for completeness and future proofing the file extension regular expression could be customisable (but not essential) Other than that spot on.So, at this point, you need file search function with regular expression(searching "*.nut" recursively and return array of file list). Am I correct?
OK. That's simpler specification than first. I'm going to add it.Yes. Recursive (searching subfolders as well as the specified folder) should be optional and for completeness and future proofing the file extension regular expression could be customisable (but not essential) Other than that spot on.
I'm not sure it's in my code or squirrel itself. But, at least, there was one bug in my code, so try this.Hi @kenken
I had some very strange issues with the import command last night. I was left scratching my head until the small hours of the morning when I worked out the pattern of the problem.
I am hoping you have an idea as to the cause. I had to make a video to explain the issue as it is so strange.
Thanks
What's exactly the top number means? How did you judge loading is succeeded or failed? I saw your video but I can't find any code for judging in foreach loop.No improvement on the issue @kenken. Thanks for trying.
::widgets["brakeInfo"] <-
{
x = 280,
y = -80,
order = ["x","y"]
}
First, does debugview show no error message?Each widget adds an entry to a "widgets" table. If the widget nut file loads then the first thing line of code is something like the following:
Code:::widgets["brakeInfo"] <- { x = 280, y = -80, order = ["x","y"] }
All I am doing is return the ::widgets.len() to see how many widgets loaded.
Unrelated to the import problems:
The GUI is coming along now. I have it dynamically loading widgets from a folder and loading/saving a config file. If there is no config file then the defaults specified in each widget are used. Any missing / invalid, unwanted settings in the config file are replaced with the defaults specified in the widget using a error checking routine.
- Is there a way of making a wrapping text field? I am using "text" but if what I write exceeds the width of the window it does not wrap.
- Can the buttons / combo boxes have an alignment argument added (AlignLeft, AlignRight, AlignMiddle)
I am onto the GUI now and I wanted a help page with version number and other useful info. Hence the wrapping text box request.
Thanks once again!
Not sure what you mean by "debugview". Is this the little empty box that appears sometimes on the left when the code is invalid? If so that does not show up at all and even when it does (for unrelated issues) it is always empty.First, does debugview show no error message?
No problem. Is it possible to get the size of (width / height) of a button or combobox using calcTextSize? That would allow me to alignment using a dummy and a calculated size.The original imgui has no alignment option for each parts. At this point, you have to align each parts manually(with dummy and sameLine function).
Understood. I will try to group my gui feature requests into batches but I don't think I will need many more. Hard to know until I actually try and do something and realise I need a feature addedI suggest that you take a some time to pick up which gui parts you need. For me, one request for several parts is better rather than multiple requests for one parts at each time when you need it.
Didn't you use debugview for debugging code? It's very hard to debug.Not sure what you mean by "debugview". Is this the little empty box that appears sometimes on the left when the code is invalid? If so that does not show up at all and even when it does (for unrelated issues) it is always empty.
.