If you export a set of states with an event hander as the initial state, on re-importing into a new project the initial state is transfered to the first media file, not the original event handler.
See attached screen shots.
What BrightAuthor version are you using? Go to Help - about BrightAuthor to tell.
Version 3.8.0.27, direct from the software downloads page. it would have upgraded an earlier Beta.
can you send us your project? I tried with one event handler, and with 3 but didn't fail like yours. So, must be something else in combination with the handlers that's causing the home state to ship. I was also using 3.8.0.27
Exported project attached with an exported state included.
Unable to duplicate.
I go to File - Import User Events.
Select UserDefinedEvents.xml.
Go to File - Open Presentation.
Select AV208 Kaka.bpf.
Event Handler is displayed as a home state. See attached image.
Please see original post, not trying to import 'User Events' - this relates to export and import states.
Within interactive play list - highlight states - right click - 'Export State'
New presentation - interactive play list - right click - 'Import State'
All the required 'User Events' are already loaded within BA - No need for us to re-import them.
This happens on 3 separate computers with different OS builds.
This works as designed.
To workaround the problem, you first need to add Event Handler to an empty interactive playlist, so that Event Handler automatically becomes an initial state.
If you add Event Handler to a playlist that already contains other states, and then manually apply home state to Event Handler, you will see the behavior that you've described.
The above kind of defeats the purpose, at least in my eyes.
We will stop using this feature as it is just a recipe for things to go wrong if you neglect to change one presentation out of a hand full.
We just assumed we would be able to make a presentation export it, import it into a blank presentation and get a 1:1 copy - Speeding up work-flows.
Thank you for clarifying it will not work this way nor was it designed to work this way. Not really sure what advantage this feature adds to the system.
Shaun,
I think there is some confusion here. If you are trying to use the same presentation over and over, just use the "save as" feature. If you are trying to create a library of states that you want to reuse in different project types then use the export/import states feature.
Is the not import as the home state for a event handler the issue in the context of a whole presentation export/import or is it something else that needs a closer look?
Thanks.
Yes, you could use the 'save as' function and we probably will now set up a series of templates that way
We were trying to set up a series of templates for future use that you could drop 'read-only' in without having to open the original files.
I understand when importing a set of states into an existing structure that the imported states merge with the originals and conform to that structure.
But when importing a state into a blank pretension it should be the same as it was when you exported it, not shift the initial state to another element - in this case to the first video file.
If that is the way it is supposed to be then that's fine, it just looked like a fault as it changed the structure unnecessarily.
If the event handlers are replaced with black jpegs the initial state does not change on re-import.
Can't find what you're looking for?
Contact support
