On running an application I was working on in 1.5 in 2.0 I get a message when I try to open it that it needs:
scrollbar.mfx
dsound.mfx
browser.mfx
browser2.mfx
I expected to see .cox files listed.
Suggestions???
Printable View
On running an application I was working on in 1.5 in 2.0 I get a message when I try to open it that it needs:
scrollbar.mfx
dsound.mfx
browser.mfx
browser2.mfx
I expected to see .cox files listed.
Suggestions???
On running an application I was working on in 1.5 in 2.0 I get a message when I try to open it that it needs:
scrollbar.mfx
dsound.mfx
browser.mfx
browser2.mfx
I expected to see .cox files listed.
Suggestions???
As long as you have those extensions copied into the "mmf1" folder (which is in the extensions folder), just click retry and it'll load fine. At least that's what it did for me.
As long as you have those extensions copied into the "mmf1" folder (which is in the extensions folder), just click retry and it'll load fine. At least that's what it did for me.
MMF2 can't use MMF1.X extensions (unless they're converted_.
because of that, if you put your MMF1.x extensions in the MMF1 folder it will load the old MMF file but won't let you run it until you get rid of all MMF1.X extesions in the game/program
MMF2 can't use MMF1.X extensions (unless they're converted_.
because of that, if you put your MMF1.x extensions in the MMF1 folder it will load the old MMF file but won't let you run it until you get rid of all MMF1.X extesions in the game/program
Well this sucks. My application is dead with MMF2.
Clickteam need to take better control of the COX extensions. I have felt this for a long time.
MMF 2 should be able to load MMF 1.5 extension converted or not. Didn't anyone in the alpha or beta test groups bring up this issue. This causes a real problem.
Well this sucks. My application is dead with MMF2.
Clickteam need to take better control of the COX extensions. I have felt this for a long time.
MMF 2 should be able to load MMF 1.5 extension converted or not. Didn't anyone in the alpha or beta test groups bring up this issue. This causes a real problem.
good point. they should have backward compatibility,
the .gam files still work fine, so why not the .cox?
good point. they should have backward compatibility,
the .gam files still work fine, so why not the .cox?
Clickteam do take control of their own extensions and any in the bonus packs. However, 3rd party legacy extensions belong to their creators - and if they lose/don't want to share their code, then the extensions cannot be converted to MMF2.
Clickteam do take control of their own extensions and any in the bonus packs. However, 3rd party legacy extensions belong to their creators - and if they lose/don't want to share their code, then the extensions cannot be converted to MMF2.
Its a disapointment but then I would mmf2 to run a lot better in runtime and have more power instead of being 100% backwards compatable.
Its a disapointment but then I would mmf2 to run a lot better in runtime and have more power instead of being 100% backwards compatable.
We can't force independent developers to update their extensions.
Its an open system we do not require people to do things to make an extension.
You can just make it.
This is why a lot of people will only use extensions that come with the product or that are in the bonus packs.
Sad but true and not it is something we have said over and over the last couple months -- A lot of extensions won't be converted or will be converted later.
Clickteam can't convert what we don't have the source for.
We can't force independent developers to update their extensions.
Its an open system we do not require people to do things to make an extension.
You can just make it.
This is why a lot of people will only use extensions that come with the product or that are in the bonus packs.
Sad but true and not it is something we have said over and over the last couple months -- A lot of extensions won't be converted or will be converted later.
Clickteam can't convert what we don't have the source for.
I can understand, the redundant code becomes too laggy for the existing engine, okay that makes sense. Just i wish Isometric Movement came already with MMF2. Sad because i really wanted to try multiple layers of Isometric mayhem.
I can understand, the redundant code becomes too laggy for the existing engine, okay that makes sense. Just i wish Isometric Movement came already with MMF2. Sad because i really wanted to try multiple layers of Isometric mayhem.
if an extension can't be converted it will never be clickteam's falut.
all the reasons are connected to the creator:
-the creator quit clicking
-the creator wouldn't like to convert it
-the creator lost the source
if an extension can't be converted it will never be clickteam's falut.
all the reasons are connected to the creator:
-the creator quit clicking
-the creator wouldn't like to convert it
-the creator lost the source
For information about the extensions mentioned above:
scrollbar.mfx -> Izzy is no longer around, but Vortex2 is developing a new scrollbar object that will be released soon.
dsound.mfx -> as far as I know Tigs has lost the source code, so this extension won't be ported to MMF2. Maybe you can replace some of the functions by the new sound functions of MMF2.
browser and browser2.mfx -> I think 3EE has lost the source code of these extensions too. If you launch programs associated with files (e.g. for viewing PDF or HTML files), you can use the Open URL action of the Vitalize! Plugin object (it does that in stand-alone applications).
Also, for info all the BP extensions plus others (especially some from 3EE like the String Parser object) will be released in a pack soon.
Ans I'm sure that other important extensions will be replaced by something else soon.
Yves.
For information about the extensions mentioned above:
scrollbar.mfx -> Izzy is no longer around, but Vortex2 is developing a new scrollbar object that will be released soon.
dsound.mfx -> as far as I know Tigs has lost the source code, so this extension won't be ported to MMF2. Maybe you can replace some of the functions by the new sound functions of MMF2.
browser and browser2.mfx -> I think 3EE has lost the source code of these extensions too. If you launch programs associated with files (e.g. for viewing PDF or HTML files), you can use the Open URL action of the Vitalize! Plugin object (it does that in stand-alone applications).
Also, for info all the BP extensions plus others (especially some from 3EE like the String Parser object) will be released in a pack soon.
Ans I'm sure that other important extensions will be replaced by something else soon.
Yves.
[]Also, for info all the BP extensions plus others (especially some from 3EE like the String Parser object) will be released in a pack soon.[/]
That's very good to hear <img src="/center/images/graemlins/laugh.gif" alt="" />
[]Also, for info all the BP extensions plus others (especially some from 3EE like the String Parser object) will be released in a pack soon.[/]
That's very good to hear <img src="/center/images/graemlins/laugh.gif" alt="" />
<We can't force independent developers to update their <extensions.
<Its an open system we do not require people to do things to <make an extension.
<You can just make it."
I disagree. Does not Clickteam require the extension to be reviewed by Clickteam before listing??? What if someone wrote an extension to steal credit card or financial information???? Open source, in general, means the source code must be made available.
All Clickteam needs to do is to set a set of standards for extensions to meet in order to run with MMF2. The software development kit should include a compiler.
Extensions created with "Clickteams" sdk that do not work with MMF2 does not make the extension or extension developer look bad. It makes Clickteam and MMF2 look bad.
<We can't force independent developers to update their <extensions.
<Its an open system we do not require people to do things to <make an extension.
<You can just make it."
I disagree. Does not Clickteam require the extension to be reviewed by Clickteam before listing??? What if someone wrote an extension to steal credit card or financial information???? Open source, in general, means the source code must be made available.
All Clickteam needs to do is to set a set of standards for extensions to meet in order to run with MMF2. The software development kit should include a compiler.
Extensions created with "Clickteams" sdk that do not work with MMF2 does not make the extension or extension developer look bad. It makes Clickteam and MMF2 look bad.
the extension SDK is called an SDK for a reason. <img src="/center/images/graemlins/laugh.gif" alt="" />
anyone can potentially create an extention to use in MMF2. Would Valve look bad if a custom made map didn't work properly in Half Life 2?
I prefer the SDK idea over the "reviewed extension" idea because it allows complete freedom in developing extensions.
the extension SDK is called an SDK for a reason. <img src="/center/images/graemlins/laugh.gif" alt="" />
anyone can potentially create an extention to use in MMF2. Would Valve look bad if a custom made map didn't work properly in Half Life 2?
I prefer the SDK idea over the "reviewed extension" idea because it allows complete freedom in developing extensions.
Yep, reviewed extension idea would not work with the number of staff we have.
The big thing is that the SDK allows a 3rd party/business to make the extensions they want, which they may/may not want to share.
Of course i would say that extension development has got alot better over the last two years, and there is a fantastic group of dedicated extension developers that have put their objects into the bonus packs, which means we can at least provide/update bugs in them if need be.
Of course it is a shame we cannot get hold of some of the 3rd party developers, but im sure some will appear and update their extensions.
Yep, reviewed extension idea would not work with the number of staff we have.
The big thing is that the SDK allows a 3rd party/business to make the extensions they want, which they may/may not want to share.
Of course i would say that extension development has got alot better over the last two years, and there is a fantastic group of dedicated extension developers that have put their objects into the bonus packs, which means we can at least provide/update bugs in them if need be.
Of course it is a shame we cannot get hold of some of the 3rd party developers, but im sure some will appear and update their extensions.
I'm sure hackers do too. No controls at all. Free to damage a users computer with uncontrolled extensions.
Users also suffer by not having standards in how the extension is installed from one download to another. In one case, a nice install program is included with an uninstall available, documentation included, etc... In another, no documentatiion is included. No common way to get help with the extension. Code gets lost, user application will not work, users work lost. Who looks bad and losses revenue??? "Clickteam". Who get bad press, "Clickteam". Not the extension developer.
Better extension standards are needed!!!
I'm sure hackers do too. No controls at all. Free to damage a users computer with uncontrolled extensions.
Users also suffer by not having standards in how the extension is installed from one download to another. In one case, a nice install program is included with an uninstall available, documentation included, etc... In another, no documentatiion is included. No common way to get help with the extension. Code gets lost, user application will not work, users work lost. Who looks bad and losses revenue??? "Clickteam". Who get bad press, "Clickteam". Not the extension developer.
Better extension standards are needed!!!
Well if your a hacker you could actually make a virus/dodgy program with many programs, C++, Java, VB, Dos batch file etc etc. But there is always a fine line between development systems being able to allow people what to make or restricting them. If you restrict too much, then you might not have much of a development tool :D
So its always good to take care Whatever you download, be it a program made with MMF or any other development system, or an extension etc.
Well if your a hacker you could actually make a virus/dodgy program with many programs, C++, Java, VB, Dos batch file etc etc. But there is always a fine line between development systems being able to allow people what to make or restricting them. If you restrict too much, then you might not have much of a development tool :D
So its always good to take care Whatever you download, be it a program made with MMF or any other development system, or an extension etc.
You can always do as many professional users do - only use the Clickteam and Bonus pack extensions. Or if that restricts you too heavily, don't use an extension until it has been thoroughly tested by others for six months. Or - keep a spare old PC as a sandpit for anything new that takes your fancy.
Some really amazing extensions have been created in the past by 14 year olds with genius level IQs. It would be sad to stifle such creativity, when others are happy to shoulder the testing risk for you.
You can always do as many professional users do - only use the Clickteam and Bonus pack extensions. Or if that restricts you too heavily, don't use an extension until it has been thoroughly tested by others for six months. Or - keep a spare old PC as a sandpit for anything new that takes your fancy.
Some really amazing extensions have been created in the past by 14 year olds with genius level IQs. It would be sad to stifle such creativity, when others are happy to shoulder the testing risk for you.
You can also use open source extensions and compile them yourself. Yes, there are a few.
You can also use open source extensions and compile them yourself. Yes, there are a few.
Clickteam has no problem setting "standards" for vitialized extensions. They have to be reviewed and vitalized, at least that is what I understand from the past forum discussions since Clickteam will "not allow" certain extensions to used in vitalize MMF applications unless they meet certain "STANDARDS" and are "APPROVED".
There is no debate here about freedom of development. They need to meet standards or no go period.
Standards are needed to protect Clickteam and users both.
Extension standards for source code, documentation, installation, Vitialize usage, and listing on the Clickteam website is needed to bring order to the chaos to protect Clickteam and users time and effort in using Clickteam products and website.
Example:
Yves stated:
************************************************** ******
scrollbar.mfx -> Izzy is "no longer around", but Vortex2 is developing a new scrollbar object that will be released soon.
dsound.mfx -> as far as I know Tigs has "lost the source code", so this extension won't be ported to MMF2. Maybe you can replace some of the functions by the new sound functions of MMF2.
browser and browser2.mfx -> I think "3EE has lost the source code" of these extensions too.
************************************************** ***
If one standard was that the developer would need to submit a copy of source code for storage at clickteam, this could be encrypted for security and only the developer and clickteam would know the key then lost source code could be protected. A simple online contract would protect the developer and Clickteam.
This would protect the USER from lost work and effort.
Help the developer and protect is their time and effort.
No more lost code, time, effort etc...
Protect Clickteam's reputation.
Clickteam has no problem setting "standards" for vitialized extensions. They have to be reviewed and vitalized, at least that is what I understand from the past forum discussions since Clickteam will "not allow" certain extensions to used in vitalize MMF applications unless they meet certain "STANDARDS" and are "APPROVED".
There is no debate here about freedom of development. They need to meet standards or no go period.
Standards are needed to protect Clickteam and users both.
Extension standards for source code, documentation, installation, Vitialize usage, and listing on the Clickteam website is needed to bring order to the chaos to protect Clickteam and users time and effort in using Clickteam products and website.
Example:
Yves stated:
************************************************** ******
scrollbar.mfx -> Izzy is "no longer around", but Vortex2 is developing a new scrollbar object that will be released soon.
dsound.mfx -> as far as I know Tigs has "lost the source code", so this extension won't be ported to MMF2. Maybe you can replace some of the functions by the new sound functions of MMF2.
browser and browser2.mfx -> I think "3EE has lost the source code" of these extensions too.
************************************************** ***
If one standard was that the developer would need to submit a copy of source code for storage at clickteam, this could be encrypted for security and only the developer and clickteam would know the key then lost source code could be protected. A simple online contract would protect the developer and Clickteam.
This would protect the USER from lost work and effort.
Help the developer and protect is their time and effort.
No more lost code, time, effort etc...
Protect Clickteam's reputation.