MMF report the extensions not converted when you save the application as standalone java app, or applet...
Printable View
MMF report the extensions not converted when you save the application as standalone java app, or applet...
yeh but if you start your program and it only tells you when you save it... thats kinda a lot of time and planning wasted
Well we can develop a easy to look at chart for people to review on whats supported by Vitalize, Java and HWA when everything gets done.
Then during that planning stage :) (just a :) because 95% of the creations skip this) the programmer can review it and plan for it.
and thats given me an idea for a site or expansion to the extension list, support for each extension under each OS, 95 - vista, linux java, mac java, applet java, vitalize, etc. :)
cool idea NK!
Could we have a filter checkbox in the "add new object" window to make it only show java objects?
Yes I was thinking about it. Depending on the current state of the build file property, it could only show this or that extension.
But then people may change builds to insert a certain object then switch back if you get my drift...
Yeah. So we have to do a constant application check at every loop of the editor.
Be reasonable. The solution I offer is sensible. And also a message box when you save.
If people change build and insert objects that are not in the build then too bad for them...
I know its common sense not to do it but you will always get the new users who try it and then come on here and ask why its not working and how to fix it.. But you could do a couple of things to stop it.
My suggestions would be either to disable the build type drop down box after its been selected or an extension for a specific type is put in the frame? Or, like with lots of IDE's, you have to select the type of program you want to build first.