Yaniv Bouhadana

I installed UI tools on my LabView 2012 and made use of the Dialog(Blackened).vi in several places during development.  

 

When I compiled my code, I found that the text message for the dialog box had disappeared.  There are some dots on a line that may be the tops of some ascender strokes.  I was under time pressure, so I went back to standard dialog boxes.  I have attached a screen capture to demonstrate the problem.

 

Is there some setting in the Build procedure that would affect only the message?  The blackened background is preferable because the instrumentation displays tend to be cluttered.

 

If you look at the title bar, you can also see that the text message intended for the main dialog box display seems to have been concatenated to the Window Title.  It does not do this on the uncompiled version.

 

The second attachment shows the implementation code which produced the results shown in attachment one after being compiled.

Same Problem for me.

is there a solution fore that ? (b.t.w - that was the bug i was try to fix by reinstalling from the previous post..)

"Main Package Name: UI Tools v1.3.0.70

Package Name with Error: UI Tools v1.3.0.70

Error Message: VIPM could not install the package lava_lib_ui_tools-1.3.0.70 .

Error Code: 8

Error Source: Open/Create/Replace File in ZLIB Read Compressed File__ogtk.vi->VIPM ZLIB Extract File (Optimized).vi->828EB4D32CB95072DF2958D72809E51E->CEF9914F587EE4F76B49993D93059AB9->OGPM Class.lvlib:38AC86238973053DFAD7A7BA9B82677D->OGPM Class.lvlib:D6F18AC72B231EBACC17ED485EA9EBEC->F04184443FB48FC5A48358EB76F6C3D1->VIPM Main Window.vi<APPEND>

C:Program Files (x86)National InstrumentsLabVIEW 2012vi.libLAVAUI ToolsDialogDialogDialog_Blacken__lava_lib_ui_tools.vi

==============="

 

Same error for all previous versions .

Other package installations works fine.

Is there a manual way to install this package?

 

 ok, Fixed (Updating for those who will met this error at the future)

The problem was that from some reason there was still some files left without a way to delete them from previous installations. restart the computer , delete them manual fixed the problem..

Never mind - I've found this - it rellated to the notifications - I decrease it to the minimum and meanwhile it looks OK - I'll use the software for a few days and report.

Thanks!!

Can you be more specific? Where can I find that switch?

Hi - it looks like a BUG but maybe someone has an idea to around this problem:

This bug was observed on a compiled (built) program which written by Labivew.

When I'm trying to write to a binary file or to create a folder which the path is pointing a windows network drive (network drive mapped by windows i.e : X:\*.*) and I'm logging as every user on this computer which is not "Administrator" , even this user acount as administrator and even launch the executable porgram as an administrator (right click --> run as administrator) when it try to write to the file - it return me an error 7.

The strange thing is that when I logging in the computer as real Administrator (and not as a user with Adminitrator privileges) its working good 80-90% of the times and suddenly get this error .

This problem was shown since the operating computer was transfered into Windows 7 (64 bit) after a long and quiet period under Windos XP.

Did anyone has an idea how to around this anoying bug?

I'll try it, but I'm afraid that the action of choosing a working directory itself, makes the directory to be locked. I'll try it when I'll have time and report as well.. Thanks again for the reference.

OK - I tried both solutions - the Unlocker is ok but its not a solution for a program which i develope to someone else use..

the other solution is nice - I implemented it and the only disadvantage of this solution is that for unlocking one folder you need to lock other and in this case i choose c:\windows - but it means that each time you use a common dialog file box in you program - the deafaut location will be c:\windows...

Thanks again!

LabVIEW Folder Unlocker.vi

Hello!

I used the "Copy file" for copying an image file from a directory and everything runs OK, exept one problem - after closing the vi (and even LabVIEW) the "Thumbs.db" file which inside the folder stays "locked" - no rename ,move or deletion of this folder by windows is allowed!

I know it make no sense but still this file stay locked!

It released again when I copy another file from other directory and then the previous "Thumbs.db" file released.

Did someone met this problem?