Invisible objects made visible revert to their invisible state after saving and opening

I am working in LiveCycle Designer ES2 creating a decision tree that is highlighted in red as you click the Yes and No checkboxes in the document. I duplicated the arrows and made the copies red and then invisible. When the checkbox is checked, the red arrows become visible, when unchecked, invisible. The problem I have encountered is that because the default state of the red arrows is invisible, they do not stay visible if you fill out the form, save it, then open it again. When the saved form is opened, all the correct checkboxes are checked, but all the red has gone back to being invsible. I am creating and saving the pdfs as dynamic XML forms and using them in Acrobat X. It was all done with the action builder (yes, I know, stop using action builder, but I had to teach myself LiveCycle last week to get this far and havn't made it to scripting).
I read through a post with a similar question but it involved a master drop down list not checkboxes, and I did not see how I could apply the solution in that post to my checkbox issue.
Any thoughts on how to get the red lines to stay visible when saved and reopened?

Hi,
check your form properties.
You need to activate the option to preserve script changes.
http://forums.adobe.com/message/3835967#3835967

Similar Messages

  • Why won't Photoshop revert to earlier history state after image resize when scripted?

    I've written an Applescript to automate watermarking and resizing images for my company. Everything generally works fine — the script saves the initial history state to a variable, resizes the image, adds the appropriate watermark, saves off a jpeg, then reverts to the initial history state for another resize and watermark loop.
    The problem is when I try not to use a watermark and only resize by setting the variable `wmColor` to `"None"` or `"None for all"`. It seems that after resizing and saving off a jpeg, Photoshop doesn't like it when I try to revert to the initial history state. This is super annoying, since clearly a resize should count as a history step, and I don't want to rewrite the script to implement multiple open/close operations on the original file. Does anyone know what might be going on? This is the line that's generating the problem (it's in both the doBig and doSmall methods, and throws an error every time I ask it just to do an image resize and change current history state):
                        set current history state of current document to initialState
    and here's the whole script:
    property type_list : {"JPEG", "TIFF", "PNGf", "8BPS", "BMPf", "GIFf", "PDF ", "PICT"}
    property extension_list : {"jpg", "jpeg", "tif", "tiff", "png", "psd", "bmp", "gif", "jp2", "pdf", "pict", "pct", "sgi", "tga"}
    property typeIDs_list : {"public.jpeg", "public.tiff", "public.png", "com.adobe.photoshop-image", "com.microsoft.bmp", "com.compuserve.gif", "public.jpeg-2000", "com.adobe.pdf", "com.apple.pict", "com.sgi.sgi-image", "com.truevision.tga-image"}
    global myFolder
    global wmYN
    global wmColor
    global nameUse
    global rootName
    global nameCount
    property myFolder : ""
    -- This droplet processes files dropped onto the applet
    on open these_items
      -- FILTER THE DRAGGED-ON ITEMS BY CHECKING THEIR PROPERTIES AGAINST THE LISTS ABOVE
              set wmColor to null
              set nameCount to 0
              set nameUse to null
              if myFolder is not "" then
                        set myFolder to choose folder with prompt "Choose where to put your finished images" default location myFolder -- where you're going to store the jpgs
              else
                        set myFolder to choose folder with prompt "Choose where to put your finished images" default location (path to desktop)
              end if
              repeat with i from 1 to the count of these_items
                        set totalFiles to count of these_items
                        set this_item to item i of these_items
                        set the item_info to info for this_item without size
                        if folder of the item_info is true then
      process_folder(this_item)
                        else
                                  try
                                            set this_extension to the name extension of item_info
                                  on error
                                            set this_extension to ""
                                  end try
                                  try
                                            set this_filetype to the file type of item_info
                                  on error
                                            set this_filetype to ""
                                  end try
                                  try
                                            set this_typeID to the type identifier of item_info
                                  on error
                                            set this_typeID to ""
                                  end try
                                  if (folder of the item_info is false) and (alias of the item_info is false) and ((this_filetype is in the type_list) or (this_extension is in the extension_list) or (this_typeID is in typeIDs_list)) then
      -- THE ITEM IS AN IMAGE FILE AND CAN BE PROCESSED
      process_item(this_item)
                                  end if
                        end if
              end repeat
    end open
    -- this sub-routine processes folders
    on process_folder(this_folder)
              set these_items to list folder this_folder without invisibles
              repeat with i from 1 to the count of these_items
                        set this_item to alias ((this_folder as Unicode text) & (item i of these_items))
                        set the item_info to info for this_item without size
                        if folder of the item_info is true then
      process_folder(this_item)
                        else
                                  try
                                            set this_extension to the name extension of item_info
                                  on error
                                            set this_extension to ""
                                  end try
                                  try
                                            set this_filetype to the file type of item_info
                                  on error
                                            set this_filetype to ""
                                  end try
                                  try
                                            set this_typeID to the type identifier of item_info
                                  on error
                                            set this_typeID to ""
                                  end try
                                  if (folder of the item_info is false) and (alias of the item_info is false) and ((this_filetype is in the type_list) or (this_extension is in the extension_list) or (this_typeID is in typeIDs_list)) then
      -- THE ITEM IS AN IMAGE FILE AND CAN BE PROCESSED
      process_item(this_item)
                                  end if
                        end if
              end repeat
    end process_folder
    -- this sub-routine processes files
    on process_item(this_item)
              set this_image to this_item as text
              tell application id "com.adobe.photoshop"
                        set saveUnits to ruler units of settings
                        set display dialogs to never
      open file this_image
                        if wmColor is not in {"None for all", "White for all", "Black for all"} then
                                  set wmColor to choose from list {"None", "None for all", "Black", "Black for all", "White", "White for all"} with prompt "What color should the watermark be?" default items "White for all" without multiple selections allowed and empty selection allowed
                        end if
                        if wmColor is false then
                                  error number -128
                        end if
                        if nameUse is not "Just increment this for all" then
                                  set nameBox to display dialog "What should I call these things?" default answer ("image") with title "Choose the name stem for your images" buttons {"Cancel", "Just increment this for all", "OK"} default button "Just increment this for all"
                                  set nameUse to button returned of nameBox -- this will determine whether or not to increment stem names
                                  set rootName to text returned of nameBox -- this will be the root part of all of your file names
                                  set currentName to rootName
                        else
                                  set nameCount to nameCount + 1
                                  set currentName to rootName & (nameCount as text)
                        end if
                        set thisDocument to current document
                        set initialState to current history state of thisDocument
                        set ruler units of settings to pixel units
              end tell
      DoSmall(thisDocument, currentName, initialState)
      DoBig(thisDocument, currentName, initialState)
              tell application id "com.adobe.photoshop"
                        close thisDocument without saving
                        set ruler units of settings to saveUnits
              end tell
    end process_item
    to DoSmall(thisDocument, currentName, initialState)
              tell application id "com.adobe.photoshop"
                        set initWidth to width of thisDocument
                        if initWidth < 640 then
      resize image thisDocument width 640 resample method bicubic smoother
                        else if initWidth > 640 then
      resize image thisDocument width 640 resample method bicubic sharper
                        end if
                        set myHeight to height of thisDocument
                        set myWidth to width of thisDocument
                        if wmColor is in {"White", "White for all"} then
                                  set wmFile to (path to resource "water_250_white.png" in bundle path to me) as text
                        else if wmColor is in {"Black", "Black for all"} then
                                  set wmFile to (path to resource "water_250_black.png" in bundle path to me) as text
                        end if
                        if wmColor is not in {"None", "None for all"} then
      open file wmFile
                                  set wmDocument to current document
                                  set wmHeight to height of wmDocument
                                  set wmWidth to width of wmDocument
      duplicate current layer of wmDocument to thisDocument
                                  close wmDocument without saving
      translate current layer of thisDocument delta x (myWidth - wmWidth - 10) delta y (myHeight - wmHeight - 10)
                                  set opacity of current layer of thisDocument to 20
                        end if
                        set myPath to (myFolder as text) & (currentName) & "_640"
                        set myOptions to {class:JPEG save options, embed color profile:false, quality:12}
      save thisDocument as JPEG in file myPath with options myOptions appending lowercase extension
                        set current history state of current document to initialState
              end tell
    end DoSmall
    to DoBig(thisDocument, currentName, initialState)
              tell application id "com.adobe.photoshop"
                        set initWidth to width of thisDocument
                        if initWidth < 1020 then
      resize image thisDocument width 1020 resample method bicubic smoother
                        else if initWidth > 1020 then
      resize image thisDocument width 1020 resample method bicubic sharper
                        end if
                        set myHeight to height of thisDocument
                        set myWidth to width of thisDocument
                        if wmColor is in {"White", "White for all"} then
                                  set wmFile to (path to resource "water_400_white.png" in bundle path to me) as text
                        else if wmColor is in {"Black", "Black for all"} then
                                  set wmFile to (path to resource "water_400_black.png" in bundle path to me) as text
                        end if
                        if wmColor is not in {"None", "None for all"} then
      open file wmFile
                                  set wmDocument to current document
                                  set wmHeight to height of wmDocument
                                  set wmWidth to width of wmDocument
      duplicate current layer of wmDocument to thisDocument
                                  close wmDocument without saving
      translate current layer of thisDocument delta x (myWidth - wmWidth - 16) delta y (myHeight - wmHeight - 16)
                                  set opacity of current layer of thisDocument to 20
                        end if
                        set myPath to (myFolder as text) & (currentName) & "_1020"
                        set myOptions to {class:JPEG save options, embed color profile:false, quality:12}
      save thisDocument as JPEG in file myPath with options myOptions appending lowercase extension
                        set current history state of current document to initialState
              end tell
    end DoBig

    As many others here I use JavaScript so I can’t really help you with your problem.
    But I’d like to point to »the lazy person’s out« – with many operations that result in creating a new file on disk I simply duplicate the image (and flatten in the same step) to minimize any chance of damaging the original file if the Script should not perform as expected.

  • Hidden Objects made visible, hidden again upon saving?

    Hello,
    I've created a form where I have a master drop down list which causes other "hidden" drop downs to become visible depending upon the selection from the master.
    I have the master drop down, and four "hidden" drop downs. Depending on which selection is made in the first drop down list, one of the secondary drop downs then becomes visible. This all works just fine in the pdf form, until I try to save. As soon as I fill out the form, and save, everything that had become visible is now hidden again!
    I have been trying to play with the action builder and figure out why, but with no success. Does anyone have any idea what the problem is?
    Thanks!

    1) Add another action to your master drop down. Add two conditions: 'is initialized' and 'text selected' with the value you want selected. Then add the same result as you did with your first action.
    2) Stop using action builder
    Kyle

  • Front Panel objects do not stay in place after saving, closing, and reopening the VI.

    I have been working with a couple of versions of a main VI. The original VI was given to me so that I could add additional functionalities to it. I had been designing the front panel of the latest version of the VI on a Dell laptop running Windows 7 and LabView 2011 SP1 using a monitor with a resolution of 1920x1080. My booleans, numerics, and plots on the front panel had always stayed in place after saving, closing, and reopening the VI. Once in the field, I connected my laptop to a cRIO9073 and used my laptop screen with a resolution of 1366x768 to operate the VI. I made some changes to the VI, saved it, and reopened it. This time I noticed that the front panel objects had become overlapped, resized, and generally rearranged. I tried fixing the objects but I noticed that they reverted back to the incorrect positions after saving and reopening the VI. I was successful in keeping the objects in position a couple of times, but when I would open the VI at a later time, the objects were again rearranged. This is happening on both my monitor and laptop screen. The original version of the VI, however, does not behave this way and I have opened it on both my monitor and laptop screen. In this version, the front panel objects always stay in place. Both VI's have the same window size properties. Could I have corrupted the latest version of my VI somehow? Below are screenshots of the front panels of both VI's.
    Attachments:
    Blender Controller Original.PNG ‏140 KB
    Blender Controller.PNG ‏203 KB

    Hi Miguel,
    It is possible to programmatically set or change the position of front panel objects. (for example: http://digital.ni.com/public.nsf/allkb/4D0DA06B431​95B3F862572F3000AF2D3?OpenDocument) However, if you haven’t intentionally done that, it seems unlikely that it is the problem.
    Have you tried copying the entire block diagram in to a new VI to see if the problem persists? While it is unlikely, you are right that it is possible for VIs to become corrupted. I’ve never heard of a situation like this except in the situation where the settings Tom had you check have been changed. Here is some information about those settings:
    http://digital.ni.com/public.nsf/allkb/7567EF257B9​CFDF986256F630073228F?OpenDocument
    Since there was no rearrangement when you copied the front panel to a new VI, you might try copying the block diagram a little bit at a time to see if there is some particular part of it that creates the problem somehow.
    K. Johnson

  • Save and Open whole objects

    Hi,
    Do you know any good tutorials about saving and opening whole objects with the jFileChooser? Your direct advice on how to do it would be very appreciated too.
    Regards,
    Pingen

    Pingen wrote:
    Hi,
    Do you know any good tutorials about saving and opening whole objects with the jFileChooser? Break it down... I think what you want to do is serialize/deserialize an object to/from a file selected by the user through a JFileChooser. Correct?
    If so, one (the serialization) has nothing to do with the other (how to get the user specified File).

  • Generating pdfs with invisible sections made visible through code

    I have a survey with several question that are either visible or hidden based on the user's selection from a Yes/No radio button group.  The user can then either submit the survey by e-mail or print the survey.  If the user prints the survey before submission, all of the invisible portions that the user's input has rendered visible are included in the printed copy; however, when the pdf is generated to be attached to the e-mail submission or saved using the Save As option, the elements that were made visible by code are not included in the pdf.  The following is the code being used in the Yes radio button:
    Comp4WhenImplementText.presence = "invisible";
    Comp4WhenImplement.presence = "invisible";
    Comp4MajorFactorText.presence = "invisible";
    Comp4WhenImplement.Comp4When03 = 0;
    Comp4WhenImplement.Comp4WhenNever = 0;
    if (Comp4No.selectedIndex != -1 ||
      Page3.Comp1.Comp1No.selectedIndex != -1 ||
      Page4.Comp2.Comp2No.selectedIndex != -1)
    CorrectiveAction.presence = "visible";
    else
    CorrectiveAction.presence = "invisible";
    The code in the No radio button is as follows:
    Comp4WhenImplementText.presence = "visible"
    Comp4When.presence = "visible"
    CorrectiveAction.presence = "visible"
    The code in the e-mail submit button:
                   form1.#subform[12].Button2::click - (JavaScript, client)
                   if (CorrectiveAction.presence == "visible")
                      if ((CorrectiveAction.rawValue == null) || (CorrectiveAction.rawValue == ""))
                   else
                   Button1.execEvent("click");
                   else
                   Button1.execEvent("click");
    Button1 is invisible and layered under the visible e-mail submit button.  It actually submits the pdf by e-mail.  The visible button performs a test and displays a message to the user if the user's survey answers fail.  I have also tried "hidden" in all of the areas that are listed as "invisible".
    What should be added or changed so that the invisible elements of the survey that are rendered visible by code can be seen in the pdf of the survey.  Any assistance would be greatly appreciated.

    There is a setting that indicates to save the changes amde via code to the form when saved. In Designer goto the File/Form Properties/Defaults and ensure that the Radiobutton named Automatically under the Preserve Scripting changes to form when saved is set on.
    Paul

  • Recently, iTunes upgraded.  My 7th generation iPod is now not recognized and I cannot sync.  The troubleshooting talks  about being visible in Windows (iPod is invisible)  No other options and nothing about windows 8

    Recently, iTunes upgraded.  My 7th generation iPod is now not recognized and I cannot sync.  The troubleshooting talks  about being visible in Windows (iPod is invisible)  No other options and nothing about windows 8

    I have had similar issues with mine, happens mainly if I transfer songs and then decide to disconnect my iPod to listen to them with my IEMs (I use Interenet Explorer in my case and it is not neccessarely up when this happens, so I seriously doubt it is an issue conencted to the web browser). I have no patience for this so my trick is I try to eject it from iTunes, if that does not work, then I bring Windows explorer up, right mouse click on the iPod mounted drive and select Eject. It gives me the same warning but there is a third button selection called Continue. When I choose that it just disconnets the drive anyway and the iPod is finally disconnected. It seems to work each and every time I do it so this solution is fine for me. Would be intersting to see what the real root cause of this is because I started getting this problem with the newer iTunes 11.

  • "Object has visibility layer override" .. how do i stop this?

    using CS3...I understand what makes this come up but dont understand how to make things update...
    Here is one example where this comes up. I have a bunch of business cards with each being its own file, each with a 2nd layer to it that is just the cut area border around it. When I print each card, i want the cut border to show for the customer. When i go to actually print, i will put them all on the same sheet and print at one time. I do this by dragging the ID files into the document that will have all the cards. Of course any changes made to the individual files will automatically (sometimes manually) update on the sheet with all the cards. The only problem I run into is if after I add these cards to the sheet and they still have those borders on it, I then have to go into the individual files and turn off the layers that have that border but this will never update in the linked file on the document using it. Instead with layers, I get this yellow and red eyeball that seems to say "Object has visibility layer override". The borders will still show on the document its linked to but the individual file, the borders are not there.
    How do I get the files using the linked ID files to read just as the individual files are without showing those layers? The only way around this I can find is to remove each card, turn off the layers in the individual files, and put the cards back on...which doesnt always do the trick, but still. Thanks!

    lark,
    Select the link on the page, then go to the layer visibility options dialog. There's a filed there to keep or update the layer visibility when updating the link. Perhaps you need to change that.
    Peter

  • Context object not visible in the Expression Editor

    Hi ,
        I have created a context object and assigned it to the sender interface ( outbound interface) but i couldn't see the created object in the Expression editor.
    Can anyone tell me why it is like this? It shows only the technical context objects .
    with Regards
    VasS

    Hi Vasagam,
    Please try out the following and see if it works:
    - Did you set the "Adapter-Specific Message Properties" in the Sender File Communication Channel.You have to select this check box and also select the "File Name" check box(this will be visible once the initially mentioned check box is selected)
    - Is the interface to which the context object is assigned an outbound Interface(Sender Interface) in receiver determination? Only then the context object will be visible.
    Regards,
    abhy

  • Add Transition to Grid control when it is made Visible.

    Hi. I have a collapsed Grid and when I tap a HyperLinkButton I want the Grid to start getting visible from the closest point from the Button or any other transition effect similar to this. To simplify my question, how do I add a transition effect to a
    Grid when it is made visible?

    Hi Clint William Theron,
    For adding the transition to the Grid control in Windows Phone, first please try to check the following articles:
    https://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh452703.aspx .
    If you want to create a custom transition for the Grid control, please try to use the
    Storyboard class to help you implement it, for more information please try to refer to:
    https://msdn.microsoft.com/en-us/library/windows/apps/jj206955(v=vs.105).aspx .
    Best Regards,
    Amy Peng
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Web Object not visible in published project

    I'd like to use the new web object interaction widget in Captivate 7 to embed a website into a project. Everything works fine as long as I  only preview the project in my web browser. But when I publish it and go to the slide where the web object is supposed to be, there's only a blank space. Why?
    I've published the project in SWF-Format with  eLearning-output set to "AdobeConnect". I tried to switch the option "Scalable HTML content" on and off as I heared that some people are having problems using this in connection with widgets, but no matter whether it's turned on or of, the web object doesn't show up. There must be something very
    trivial that I have overlooked since I'm using the web object in the standard way it is meant to be used.
    Thanks in advance for any help.
    Andreas

    Thanks for your advice, but it still doesn't work. I have created a new project for my tests with only the web object in it to make sure no other objects etc. are influencing the output. I  published the project and tried to run it on different browsers/operating systems and directly from my hard drive vs. Adobe Connect. The results:
    Using my Mac and opening the project with the HTM.-file from my hard drive after I have added the published files folder  to the trusted locations for Flash (without this setting, it doesn't work), the web object only appears in Safari, but not in Chrome and Firefox. Using AdobeConnect, it's the same: only Safari.
    Using a Windows laptop (again opening the project with the HTM.-file from my hard drive after I have added the published files folder  to the trusted locations for Flash), it works with Internet Explorer and Firefox, but not with Chrome. Using AdobeConnect, no browser works. I only get this message:
    I can't use the web object when it only loads under very special circumstances. Moreover, I found out, that checking the "Scale HTML content" checkbox in the publish window  results in a totally misplaced web widget in those browsers that support the web object. It then looks like this:
    I use this option regularly, so this is really a problem for me.
    I hope you can tell, what I can do to get the web object running. I simply can't believe that this  is the standard behaviour and that everybody else is experiencing the same problems. There must be something I can do to get it running.
    I hope you can help.
    Best Regards
    Andreas

  • Error message when I insert a div tag: Couldn't commit the changes made in Live View. Refresh the Live View and try editing again.

    According to a web and support forum search, myself and another person, Chloe in the Dreamweaver Club forum, have ever reported this. Trying to follow along a Lynda.com tutorial, and the instructor isn't getting this error. Can't imagine why it's happening. I'd be very grateful for any help. I'm also getting an error dialog message:
    DIALOG BOX:
    While executing onClick in InsertFGDiv.htm, the following JavaScript error(s) occurred:
    At line 687 of file "Macintosh HD:Applications:Adobe Dreamweaver CC 2014.1:Configuration:Commands:InsertFGElement.js": The object is not currently contained in a document.
    This appears at the top of the screen:
    Couldn't commit the changes made in Live View. Refresh the Live View and try editing again.  [Refresh doesn't do anything.]

    Try the suggestions here -
    Index to Dreamweaver FAQ
    The solution for Javascript errors is likely the one.

  • How does Adobe make their camera  profiles for ACR and Lightroom?

    I'm not interested in the proprietary algorithms , but I am curious as to the photographic mechanics and hardware tools used by  Adobe to make the various camera profiles as they differ markedly from the ones I make using the DNG Profile Editor.
    My methodology is to set an X-Rite 24 patch Color Checker target, light it evenly with electromic flash (with 0.1 stops from center to corners as mesured with a Sekonic L-758r Meter) and make a series of exposures bracketed in third of a stop increments around the meter reading in case the camera sensitivity differs from the meter's.
    I then process the raw files and convert them to the DNG format, select the best exposure and run it through the DNG Profile editor. My results differ from Adobe's generic profiles for that camera enough that that I don't thin kthe difference can be credited to the difference between a generic profile a specific camera.
    How do the different tools work in the DNG converter? Starting with the Options for "Base Tone Curve"? Is there a document a moderately color geeky person can understand that explains this?
    I thin kthe DNG Profile editor is a great and under usedtool. I wish more people knew about it.
    Thank you for your time and consideration.

    Someone who only eats sausage may not want to know how it's made.  Someone who creates things with food, a chef, a cook, or otherwise is thinking about a career in the food industry, might have a interest in such things.  Someone who is thinking of making sausage will want to know all the details.  Someone who is concerned with the public safety might want to know how sasauge is made.
    It would be nice for a sausage maker to give some hints about the process as compared to what each of us can do with the DNG Profile Editor and to the original poster's question, why are our profiles different from Adobe's?
    It is my experience that when I create a profile with the DNG Profile Editor, and then compute the color error for each of the 24 color patches of a CC24, using a program like Imatest, some colors are quite a bit off and some are very close, and the colors that are off, are not the same ones that are off when I compute the color error using one of the Adobe Standard or Camera Standard profiles.
    Is Adobe using more detailed and sophisticated color targets with hundreds of different colors, or if not, do the tools provide more feedback and allow more manual manipulation of the profile and so the differences are due to their judgement about which colors to make "right" and which ones to let have more error associated with them, that can be manipulated by hand instead of merely letting the DNG Profile Editor apparently distribute the error amongst the various colors with some sort of even-handed calculation.
    For example it is easy to imagine that someone tweaking a profile by hand with a live readout of the error of each of the colors plus an overall composite error, might put more emphasis on skin tones being right if they have a background in people photography, or more emphasis on bright colors being right if their experience is in textiles and the current trend in the US is bright colors--and a different emphasis when the trend is muted colors so there is cultrual bias and life-experience coloring a "standard" profile.
    In other words, how much of the difference between Adobe and our profiles are due to Adobe having different or better science, and how much of it is due to Adobe have different or better "artists" who decide what colors to make correct compared to others.

  • Objects (mostly text boxes, etc.) change slightly after uploading

    Hello!
    I am a novice Muse user, and love how easy it is to use - but I've noticed what I think may be a glitch with the rendering of text boxes once they're uploaded. When I am in design mode, all of my items are one size and perfectly aligned, but when I preview or upload, some items resize and and end up "off".  I've uploaded screencaps of my site in Muse and on the Web to show what I mean. See how the second content box on the live version is slightly longer than the other three? According to design mode, all four of those boxes are exactly the same width and height, but they render differently when uploaded or previewed. 
    I'm wondering if this is due to responsive resizing when a scrollbar is added in preview/web mode? And if so, how can I fix it? I've already tried adjusting the text in that box. I haven't made the others larger to match it because when I'm in design mode it all looks fine, and I'd have to do trial and error fixing for something that seems like it should be simpler.
    Any info is appreciated!
    Kellie

    I may have discovered a work-around for this fatal bug. Make sure that the area-type object is the top most object in the layer order, or if you are working with multiple type objects, that each type object is in its own separate layer. It seems this bug is most prevalent when the selected objects are in the same layer, and the area-type that is selected is below other selected objects.
    I was able to simplify the process of re-creating this bug down to one text box and a rectangle. First, create an area-type object and put some text in it.. Second, create a rectangle. Then, while the rectangle is still selected, use the shift key and direct-selection tool to select the left edge of the area type object. Finally, with both selections active, start moving them and watch the type disappear!
    I noticed that if I change the layering order of the type-object, to where it is above the rectangle, then moving the selections, the bug goes away. Also, I found that if I needed to move the selected edges of several area-type objects at once, I could do so, as long as each type-object was in its own layer.
    For the amount of time that I have spent on this bug, Adobe should give me the next version of Illustrator for free. Heck, Adobe should give everyone that has to use CS, a free upgrade.

  • New LabHSM Toolkit - Agile development of complex event-driven maintainable LabVIEW applications with active objects / actors based on a universal Hierarchical State Machine / statechart template.

    Dear Fellow LabVIEW programmers:
    Most of the systems you deal with are reactive. It means that their
    primary function is constant interaction with their environment by
    sending and receiving events. But most likely, they can have something
    happening inside them too, even when they are not processing messages
    received from outside. So, such systems have to continuosly react to
    external and internal stimuli. Right? Moreover, most likely, they
    consist of subsystems that are reactive too and, in turn, can have
    their own "life", to an extent independent from other parts (with
    which they still communicate, of course). Reactive (event-driven)
    systems are more naturally modeled with active objects. So, why then
    should we try to model and code them with GOOP and its passive
    ("dead"!) objects?
    "Flat" State Machines have been known for decades to have severe
    limitations. It's been more than 20 years since Dr. Harel invented
    Hierarchical State Machines (statecharts) to fight those limitations.
    Then why does NI still tout the same old good Moore FSM as the
    ultimate tool for event-driven programming in LabVIEW in its $995
    State Diagram KIt?
    The LabHSM toolkit we are happy to present, makes it possible to
    easily create and then maintain complex event-driven applications in
    LabVIEW as a collection of HSM-driven active object VIs using a higher
    level of abstraction and agile software development methodologies.
    These active object VIs are created based on a universal Hierarchical
    State Machine ( HSM or statechart ) template. So. all your code looks
    similar regardless of its functionality!
    We all love just jump to code, right? However, to be good boys, we
    need to do design first. Then implement it in code. If the logic is
    modified we need to redo the design first and then redo the code. When
    using LabHSM where behavior information is abstracted into a separate
    HSM data file editable with a supplied editor, there is no need for
    coding separate from design any more. The modified behavior becomes
    code automatically as soon as the HSM file is saved. Design is code!
    The implementation basically follows Dr. Samek's Quantum Programming
    paradigm. (see http://www.quantum-leaps.com). However, as already
    mentioned, LabHSM stores the behavior information in a file separate
    from the code itself. It also adds state dependent priorities to
    events, a separate queue for public events/messages, and, of course,
    some LabVIEW specific code like capturing front panel user events and
    putting them into the private Events queue. Communication and
    instantiation functions are also rather specific for LabVIEW.
    It is available for UNLIMITED PERIOD trial. Please visit
    http://www.labhsm.com for details and download. The site also contains
    references which you may want to check to learn more about
    hierarchical state machines and active object computing.
    Since this is our debut we will appreciate any comments and
    suggestions. Our contact information is available on our site, of
    course.
    Have a G'day!

    Symtx is currently hiring the following position. Please contact me if interested.
    Amy Cable
    Symtx, HR
    [email protected]
    Symtx, the leading supplier of functional test equipment, hires the brightest & most talented engineering professionals to design & manufacture complex custom electronic systems for advanced technology leaders in the defense, aerospace, communications, medical, transportation & semiconductor industries. Symtx’ challenging & dynamic work environment seeks to fill openings with highly qualified electronic engineering design professionals.The ideal candidate will be responsible for defining the requirements, software design and code development, and integration of test control software for custom functional test systems. Candidate should be familiar with data acquisition concepts, instrument control, complex test, measurement and calibration algorithm development and definition and implementation of control interfaces to hardware. Prefer familiarity with instrument control via GPIB, VXI, MXI, RS-232 desirable. Requires BS/MSEE and 3 -7+ yrs of experience in one or several of the following test applications in a Windows NT/2000/XP environment using Labwindows CVI, TestStand, Labview, Visual Basic, C++ and knowledge of RF systems is a plus. Job responsibilities will include software design, development, integration, team leadership, and interfacing with customers( includes PDR’s & CDR’s).

Maybe you are looking for