Cannot browse directory structure in EXE

[Monkeymerlot]

Can you elaborate on what this bug is?

[ciozi137]

@Monkeymerlot:

[Monkeymerlot]

I dont think the problem is with list folder but rather how the structure laid out. Here is an exe I made with list folder that just reads stuff from my desktop. I had to modify the incoming path though. and here is the block diagram before building:

[ciozi137]

The issue is if you try to browse inside the exe Basically there is a VI at Main.exe\AFM\etc, but List folder can't browse inside the exe

[ciozi137]

Maybe I am not stripping the path sufficiently: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019NFfSAM&l=en-US

[ciozi137]

Nope that didn't fix. Here's 6 minute video.

https://drive.google.com/file/d/1vp_MMwOWamzLyCpVq68ZFK_hmi8md1NE/view?usp=drivesdk

[ciozi137]

https://forums.ni.com/t5/LabVIEW/Getting-vi-directory-list-from-LabVIEW-executable-internally/td-p/3601722?profile.language=en

"The best option so far, is as I mentioned to run a pre-build VI that looks at the relative paths to the project, writes that to a file, and then when the EXE runs, use this information and hope that the relative path from source to project, is the same from VI to EXE."

[ciozi137]

@Monkeymerlot is there really a need to have the program “search” for the available drivers? I think that the ring control can be pre-populated with all of the AFMs that the lithography program supports. Actually choosing which afm can be automated somehow, e.g. looking at the computer name it is running on or just reading from the configuration file on the computer.

[Monkeymerlot]

I like the configuration file idea. This would also provide us (developers) a way to develop everything as well as choosing an individual AFM for a computer in the lab. The computer name is probably not a good idea because that ties this software directly to specific computers unless I am misunderstanding what you mean by that. I do agree though that there is really no reason for us to have a ring there. I cannot fathom people having more than one AFM hooked up to the same computer, and I think that people are capable of changing a config file if needed.

[ciozi137]

I was just imagining a way for the program (exe) to automatically configure itself for the type of afm attached to the computer. A configuration file in the appropriate place (c\programdata) would be fine because it only needs to be configured once. Updating the exe does not overwrite the config file

On Sat, Jun 27, 2020 at 8:56 PM Joseph notifications@github.com wrote:

I like the configuration file idea. This would also provide us (developers) a way to develop everything as well as choosing an individual AFM for a computer in the lab. The computer name is probably not a good idea because that ties this software directly to specific computers unless I am misunderstanding what you mean by that. I do agree though that there is really no reason for us to have a ring there. I cannot fathom people having more than one AFM hooked up to the same computer, and I think that people are capable of changing a config file if needed.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/levylabpitt/AFM-Lithography/issues/10#issuecomment-650659502, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGLMUZCGAILP2OW755MXE5LRY2IJ7ANCNFSM4OA3ENDA .

[Monkeymerlot]

Just thought of this: what about using the file extension for the background image to set the afm type. Eg nid --> Nanosurf, ibw --> Asylum. There is some issues eith this like multiple Nanosurf AFMs with different active x references all use nid files, but it is just a thought.